Connect Segment from GrowSurf

Open Campaign Editor > 4. Options > Integrations, choose Segment, and connect the integration. If Segment is already installed on every referral surface, the write key is optional and you can still enable the integration. GrowSurf recommends saving the key anyway so referral pages without a preinstalled Segment snippet are still covered.

Keep the GrowSurf referral event set enabled

• growsurf_signup for new participants who join and receive a share link.
• growsurf_share when a participant uses GrowSurf's social or copy-link share actions.
• growsurf_invite when a participant sends email invites from GrowSurf.
• growsurf_referral when a referred visitor signs up through a referral link.
• growsurf_referral_trigger when a referred participant completes the qualifying action and you use growsurf.triggerReferral().

Start with the full event set enabled, then turn off any events you truly do not need after you confirm the source is clean.

Cover both places where referral activity happens

GrowSurf's own docs call out two URLs that teams often miss: the referral portal and the referred-friend landing page or signup page. Segment needs to be allowed on both surfaces, otherwise your source will show only part of the referral journey.

Validate events in Segment's Source Debugger

Run a real participant test, then check Segment's Source Debugger for the GrowSurf events. Twilio Segment documents the debugger as a sampled, capped validation tool, so treat it as the fastest way to confirm delivery, not as your permanent event archive.

Only fan out to other destinations after the source is correct

Once Segment is receiving the right GrowSurf events, forward them to your product analytics tools, customer data tools, alerting destinations, or warehouse. That keeps every downstream report tied back to the same verified referral source instead of debugging multiple tools at once.