Connect Segment in GrowSurf first

In Campaign Editor > 4. Options > Integrations, connect Segment and add the write key when GrowSurf needs to load Segment itself. If Segment is already installed on every referral surface, the key is optional, but the integration still needs to be enabled so GrowSurf can emit the referral events.

Confirm the GrowSurf event family in Segment

Before you think about tables or warehouse models, confirm Segment is receiving growsurf_signup, growsurf_share, growsurf_invite, growsurf_referral, and growsurf_referral_trigger where relevant. Segment's Source Debugger is the fastest first check, even though Twilio documents it as sampled and capped.

Add the warehouse destination with the right expectations

Connect your warehouse destination inside Segment and let Segment handle the load process. Twilio's warehouse docs describe these syncs as bulk loads that run on a regular cadence, so do not treat the warehouse as an instant event stream or an alerting system.

Validate warehouse sync health beyond the debugger

Once the source is clean, check the warehouse destination's sync history, schema, and loaded tables. The debugger tells you whether events reached Segment; your warehouse destination tells you whether the batch load completed and the data landed where your team expects it.

Join referral data with the rest of your business data

After the tables are healthy, join the GrowSurf referral events to your product usage, CRM, or billing data in SQL. That is where this pattern pays off: you can analyze referral-sourced users, qualified referrals, and revenue outcomes in the same warehouse model your team already trusts.