Andrea Caravello

Marketing
Cello

All•
Blog•
Apr 21, 2026 •
13 min read

Cello + Segment Integration: Track Referrals (2026)

TL;DR

The Cello + Segment integration is a server-side connection that routes every referral event into your CDP via Segment's HTTP API source. No custom ETL required
Every invite sent, signup completed, and conversion confirmed enters Segment as a structured track() call, enabling full-funnel attribution without manual data exports.
Segment Destinations forward Cello referral data to HubSpot, Salesforce, Customer.io, and 550+ tools
PLG teams use Cello referral events to build high-intent Audiences in Segment and trigger automated activation sequences on day one.

For Growth Engineers and Heads of Growth at PLG SaaS companies, Segment is the operational hub for customer data. Every product event, user trait, and conversion signal flows through it, yet for most teams, referral program data sits in a separate tool, disconnected from the rest of the pipeline. That gap produces attribution blind spots and forces manual data reconciliation between your referral platform and your CRM, email, and analytics tools.

The Cello + Segment integration closes that gap. By connecting Cello's referral platform to Segment via REST API, every referral event lands in your CDP alongside the rest of your product data. No custom ETL, no brittle exports. Referred customers are 18% less likely to churn than those acquired through other channels (Schmitt, Skiera & Van den Bulte, Journal of Marketing). For a full overview of Cello's integration ecosystem, see our guide to SaaS native integrations.

What Is the Cello + Segment Integration and How Does It Work?

The Cello + Segment integration is a server-side connection that uses Cello's REST API to send referral events into Segment via Segment's HTTP API source. When a user sends a referral invite, a referred contact signs up, or a conversion is confirmed, Cello fires the event to your backend, which forwards it to Segment as a structured track() call. No native connector is required, the integration runs on Cello's standard REST API and Segment's standard HTTP API, both of which any Growth Engineer configures in under a day.

💡 Answer Nugget: The Cello + Segment integration works by routing Cello referral events through Segment’s HTTP API source via a server-side REST API call. Each referral event: invite, signup, or conversion, arrives in Segment as a track() call with a consistent event schema, making it immediately available for Audience building, Destination routing, and funnel analysis.

Cello's integration architecture has three layers:

REST API: the primary method for sending referral event data to Segment. Authenticated with an accessToken generated from your accessKeyId and secretAccessKey at Cello's portal.
Web and Mobile SDKs: capture referral identifiers (the ucc referral code) on the client side, ensuring the referring user is correctly attributed before the server-side event fires.
Webhooks: Cello fires webhooks for payment-related events (Stripe and Chargebee natively supported), which can also be forwarded to Segment's HTTP API for reward-triggered events.

Why PLG SaaS Teams Connect Their Referral Program to Segment

PLG SaaS teams use Segment as the single source of truth for user behaviour. Connecting a referral program to that source of truth means referral activity, who referred whom, when, and whether the referral converted, is visible in every downstream tool without a separate data sync.

💡 Answer Nugget: PLG SaaS teams connect their referral program to Segment because referral events are product events. A user who referred three colleagues and converted them into paying customers is a fundamentally different user than one who did not — and that difference should be visible in your CRM, email tool, and product analytics without manual intervention.

The commercial case is well-established. VEED, a PLG SaaS company using Cello's referral platform, reduced customer acquisition cost by 90.4% and achieved a 14.5% sign-up rate from referred users. Those numbers are only measurable, and reproducible, when referral data flows through the same analytics infrastructure as every other acquisition channel.

Three specific problems Segment solves for Cello customers:

Attribution fragmentation: Referred users show as 'direct' in GA4 and your CRM until referral event data is routed through a shared identity layer. Segment's identify() call resolves this by attaching the referring user's userId to the referred user's profile at signup.
Manual CRM sync: Without a CDP in the middle, referral program data requires a direct integration with every downstream tool. Segment replaces N individual integrations with one.
Advocate visibility gaps: Without Segment Audiences, identifying your top referral advocates requires a manual query against your referral platform. With the integration live, a Segment Audience of 'users with 3+ referral conversions in the last 90 days' updates automatically.

What You Can Do With Referral Data in Segment (Top 5 Use Cases)

Connecting Cello to Segment unlocks five high-value data flows that PLG SaaS teams cannot achieve with a standalone referral tool.

Use Case	How Cello Sends the Data	What You Do in Segment
Track new referral signups	REST API event → Segment HTTP API as `track()` call	Filter on event name to build conversion funnels and Audiences
Enrich referrer user profiles	Referrer `userId` + traits forwarded via API	Run `identify()` to update user profile with referral activity history
Trigger reward notifications	Reward-issued event via backend webhook listener	Route to Customer.io or Iterable Destination to fire reward fulfilment email
Sync referral data to CRM	Track events forwarded through Segment pipeline	Connect HubSpot or Salesforce Destination; map event properties to CRM contact fields
Build referral cohorts for analysis	All referral Track events carry `referral_*` properties	Create Segment Audience: users with ≥1 `referral_converted` event, segment by plan or acquisition date

How to Connect Cello to Segment: Step-by-Step Setup Guide

Setup requires access to your Segment workspace, your Cello API credentials, and a server-side environment (Node.js, Python, or any backend that can make POST requests).

💡 Answer Nugget: Connecting Cello to Segment takes four core steps: create an HTTP API source in Segment to get a Write Key, retrieve your Cello API credentials from the portal, configure your backend to forward Cello referral events as Segment track() calls, and verify events in the Segment Debugger before connecting Destinations.

Step 1: Create an HTTP API Source in Segment

In your Segment workspace, navigate to Connections > Sources > Add Source and select HTTP API. Name the source clearly (e.g., 'Cello Referral Events'). Copy the Write Key from Source Settings. Your backend uses this to authenticate POST requests to Segment's API. The Write Key must be base64-encoded and passed as a Basic Auth header.

Step 2: Retrieve Your Cello API Credentials

Log into Cello's portal and generate your accessKeyId and secretAccessKey. Use these to request a short-lived accessToken via POST to Cello's authentication endpoint. Cello provides a production API, and sandbox for pre-launch testing.

Step 3: Configure Your Backend to Forward Cello Events to Segment

Create a handler that listens for Cello referral events: invite sent, signup confirmed, conversion recorded, and reward issued (Verify exact event names). For each event, POST to Segment's API with the Write Key in the Authorization header, the referrer's userId, the event name, and a properties object containing referral metadata (referral code, referred user ID, reward type, conversion value).

When a referred user completes signup, fire a Segment identify() call alongside the track() call. Include the referred user's userId, email, and traits: referral_source: 'cello' and referred_by_user_id: '[referrer_userId]'. This attaches referral context to the user's profile in Segment, available in every Destination (HubSpot, Salesforce, Customer.io) without additional configuration.

Step 5: Verify Events in the Segment Source Debugger

Open the Source Debugger tab in Segment. Trigger a test event using Cello's sandbox. Confirm the event arrives with the correct event name, userId, and properties. Ensure schema consistency across all referral event types before connecting Destinations. Inconsistent schemas cause downstream mapping failures.

Step 6: Connect Segment Destinations to Activate the Data

Navigate to Connections > Destinations and add the tools in your stack: HubSpot, Salesforce, Customer.io, Amplitude, or any of Segment's 550+ available Destinations. Map referral track() events to the appropriate trigger or field in each Destination. No additional API credentials needed once the source is live.

How to Track Referral Events in Segment (Identify, Track, and Group Calls)

Segment uses three core call types: identify(), track(), and group(). Each serves a distinct purpose when integrating referral program data from Cello, and using all three correctly gives your team a complete referral data model in Segment.

💡 Answer Nugget: The three Segment call types map directly to referral program data: track() records what the user did (sent an invite, converted a referral), identify() attaches referral context to the user’s permanent profile, and group() associates a B2B referred user with their company account for sales team visibility. All three are sent via the same HTTP API source endpoint.

User Profile Enrichment

Fire an identify() call when a referred user signs up. Include these traits:

referral_source: 'cello': flags the user as referral-acquired
referred_by_user_id: '[userId of referrer]': creates a queryable link between the two users
referral_code_used: '[ucc code]': the Cello unique referral code that drove the signup

Event Recording

Event Name	Trigger	Key Properties
`Referral Invite Sent`	User shares referral link	`referrer_user_id`, `channel`, `referral_code`
`Referral Signup Completed`	Referred user creates account	`referred_user_id`, `referrer_user_id`, `referral_code`
`Referral Converted`	Referred user converts to paid	`referred_user_id`, `referrer_user_id`, `plan_name`, `conversion_value`
`Referral Reward Issued`	Reward triggered for referrer	`referrer_user_id`, `reward_type`, `reward_value`, `reward_currency`

Account-Level Attribution (B2B SaaS)

In B2B SaaS, referred users join a company account, not just an individual plan. Fire a group() call with the referred user's userId and their groupId (company/account ID) when they complete signup. This makes the referral visible at the account level in Salesforce and HubSpot. Critical for sales teams evaluating pipeline quality by acquisition channel.

How to Use Segment Audiences to Identify and Activate Your Top Referral Advocates

Segment Audiences transform your Cello referral event stream into actionable user segments that trigger automated workflows. No SQL queries, no manual list exports.

💡 Answer Nugget: A Segment Audience built from Cello referral events is a dynamic, auto-updating list of users who meet a referral activity threshold. Growth teams use these Audiences to identify high-value advocates in real time and route them to targeted activation sequences in Customer.io, HubSpot, or Intercom without manual intervention.

Audience 1: Top Referral Advocates

Criteria: Users with Referral Converted event count ≥ 3 in the last 90 days.

Action: Route to a high-touch nurture sequence via your email platform. These users are your most effective growth lever and warrant a personalised reward or upgrade offer.

Audience 2: Invited-But-Not-Converted Advocates

Criteria: Users with Referral Invite Sent event count ≥ 1 AND Referral Converted event count = 0 in the last 30 days.

Action: Trigger a re-engagement push notification or in-app prompt reminding them of their pending invite. Conversion rates on reminded referrers are consistently higher than on first-touch invites.

Audience 3: New Referred Users — Onboarding Cohort

Criteria: Users with referred_by_user_id trait set AND account created in the last 14 days.

Action: Route to a dedicated onboarding sequence in Customer.io or Intercom that acknowledges the referral context and accelerates activation.

How to Route Cello Referral Data to Your CRM and Email Tools via Segment Destinations

Once Cello referral events are live in Segment, they flow automatically to every connected Destination. No additional API setup per tool.

💡 Answer Nugget: Segment Destinations route Cello referral events to every tool in your stack from a single configuration point. A referral_converted event sent once to Segment simultaneously updates a HubSpot contact record, creates a Salesforce activity, and triggers a Customer.io reward email — with no duplicate integration work required per destination.

Salesforce

Map the Referral Converted event to a Salesforce Activity or custom field on the Contact record. For teams with the Cello + Salesforce direct integration already live, Segment adds a complementary event layer for behavioural data on top of the CRM sync.

HubSpot

Map Referral Invite Sent and Referral Converted events to HubSpot Contact properties and Workflow triggers. A referred user who converts triggers a HubSpot workflow that updates lifecycle stage and notifies the assigned sales rep.

Customer.io, Iterable, and Klaviyo

Route the Referral Reward Issued event to your email platform to fire a reward fulfilment confirmation. Route Referral Invite Sent to trigger a follow-up prompt if the invite goes unopened for 72 hours.

Amplitude, Mixpanel, and Heap

Route all four Cello referral event types to your product analytics tool to create referral acquisition funnels alongside your standard product funnels. The fastest way to calculate comparative retention, activation, and LTV profiles of referred vs. non-referred users.

Referral Attribution: Measuring Full-Funnel Impact From Segment Data

Full-funnel referral attribution requires connecting three data points that typically live in separate tools: the referral invite (Cello), the signup event (your product), and the conversion to revenue (your billing system). Segment is the layer that joins all three.

💡 Answer Nugget: Full-funnel referral attribution in Segment works by joining three event types — Referral Invite Sent, Referral Signup Completed, and Referral Converted — using the shared referral_code property as a consistent key. This produces a single, queryable funnel from invite to revenue that no standalone referral tool or CRM can generate alone.

Invite → Signup conversion rate: Divide Referral Signup Completed count by Referral Invite Sent count, segmented by channel property. Identifies which share channel (email/in-app link/social) produces the highest invite acceptance rate.
Signup → Conversion rate: Divide Referral Converted count by Referral Signup Completed count. A high rate confirms you are attracting product-qualified referred users, not low-intent signups.
CAC comparison: Join Cello referral events with your billing event stream (Stripe webhook → Segment) to calculate referral-acquired CAC against paid channel CAC. VEED achieved a 90.4% CAC reduction and a 19.7% freemium-to-paid conversion rate using Cello. Metrics that are only measurable with a shared data layer.
Referral LTV cohort: Build a Segment Audience of all users with referred_by_user_id trait set. Compare 6-month and 12-month LTV against non-referral acquisition cohorts in Amplitude or Mixpanel.

Talk to an expert

Frequently Asked Questions

Does Cello have a native Segment integration?

Cello does not have a pre-built one-click Segment connector. The integration is built using Cello's REST API and Segment's HTTP API source — a standard server-side setup that a Growth Engineer configures in under a day. Cello provides production and sandbox API environments, and Segment's HTTP API source accepts any structured event payload via POST request.

What referral events does Cello send to Segment?

Cello sends four categories of referral events: invite sent (user shares referral link), signup completed (referred user creates account), conversion confirmed (referred user converts to paid), and reward issued (reward triggered for referrer). Each event is sent as a Segment track() call with a consistent properties schema.

Can I use Segment to trigger referral invite emails automatically?

Yes. Once Cello referral events are in Segment, route the Referral Signup Completed event to Customer.io, Iterable, Klaviyo, or any email Destination in your Segment workspace. This triggers a referral-specific welcome email for referred users or a conversion milestone email for the referrer — managed from your existing email platform, with no separate workflow inside Cello.

Can I send Cello referral data to HubSpot or Salesforce via Segment?

Yes. Add HubSpot or Salesforce as a Destination in Segment's Connections interface and map referral event properties to the relevant CRM fields. The Referral Converted event maps to a HubSpot lifecycle stage update or a Salesforce Activity, making referral-acquired pipeline visible to your sales team without a separate integration.

How long does it take to set up the Cello + Segment integration?

The Cello + Segment integration takes one engineering day end-to-end: ~2 hours to create the Segment HTTP API source and retrieve Cello API credentials, ~3-4 hours to build the server-side event forwarding handler, ~1-2 hours to test events in the Segment Debugger and connect the first Destination. Teams with an existing server-side Cello API integration typically complete the Segment extension in under 4 hours.

Do I need engineering resources to connect Cello to Segment?

Yes — the Cello + Segment integration requires server-side implementation. A Growth Engineer or backend developer configures the connection by writing a backend handler that forwards Cello API events to Segment's HTTP API endpoint. Setup is typically completed in one engineering day. Cello's sandbox environment and Segment's Source Debugger both provide testing capabilities before going live.

Best Referral Software: HubSpot & Stripe Integration (2026)