← View All Guides
Customer.io logo
Integration Guide

How to Trigger Customer.io Journeys from GrowSurf Referral Data

Use GrowSurf-synced Customer.io attributes to build data-driven segments and start referral journeys without a separate event bridge.

Want the full setup walkthrough?

Use these docs for exact setup steps, supported fields, and troubleshooting.

GrowSurf's native Customer.io integration updates people records with referral attributes every time a participant is added or referred. That gives you current referral context inside Customer.io without wiring a second event pipeline.

Use this guide when you want Customer.io journeys to react to referral status, referral counts, or milestone progress. The fields that matter most for this workflow are {{customer.grsf_referral_status}}, {{customer.grsf_total_referral_count}}, {{customer.grsf_next_milestone}}, and {{customer.grsf_share_url}}.

Integration Steps

Connect Customer.io in GrowSurf first

Customer.io integration settings in the GrowSurf campaign editor
Connect Customer.io before importing participants so GrowSurf can keep the referral attributes current on each synced person.

In GrowSurf, open the Customer.io integration card, add your Site ID and Tracking API key, then save the connection. This is the supported setup flow in both the GrowSurf docs and the current app UI.

Verify the sync is active before you build segments

Connected Customer.io integration state in GrowSurf
The connected state in GrowSurf confirms the native sync is ready to keep Customer.io people up to date.

After the integration is live, GrowSurf adds or updates Customer.io people whenever participants join or are referred. If you connected late, use the documented export-and-import backfill process so older records receive the same attributes.

Create a data-driven segment from the synced referral fields

In Customer.io, build a segment around the referral state you actually want to message. Common starting points are people whose referral count is still zero, people whose referral status has changed, or people who are close to the next milestone.

  • Use {{customer.grsf_referral_status}} when you want the journey to react to pending versus awarded referrals.
  • Use {{customer.grsf_total_referral_count}} when you want to distinguish new advocates from repeat referrers.
  • Use {{customer.grsf_next_milestone}} when you want the journey to push people toward the next reward.

Attach the segment to the right Customer.io journey

Once the segment is defined, enroll it in a Customer.io journey for the actual outcome you want: first-share nudges, milestone reminders, or reward follow-ups. Customer.io's current docs describe this as a data-driven segment workflow, so you do not need a separate GrowSurf event bridge to start the journey.

Test with a real participant record

Preview the segment and journey against a Customer.io person whose state you can confirm in GrowSurf. That keeps the automation grounded in the same referral data your team already trusts.

Tips

Connect before you import

Connecting Customer.io first is the cleanest path because GrowSurf only syncs attributes after the integration is active. If you already imported people, use the documented backfill process instead of rebuilding the list by hand.

Start with one segment rule and one journey

Pick a single referral state that matters, such as zero referrals or near-milestone participants, and prove that journey first before layering on more branches.

Use synced fields instead of duplicate tags

GrowSurf already maintains the referral status and counts in Customer.io, so it is safer to branch from those synced attributes than to invent a parallel tagging workflow.

FAQ

Does GrowSurf send custom Customer.io events for this integration?

No native GrowSurf Customer.io integration is documented as a people-attribute sync. The supported workflow is to use the synced referral attributes on Customer.io people and build segments or journeys from those fields.

Which Customer.io rules are best for referral journey triggers?

Start with rules based on referral status, total referral count, or next milestone text because those fields map cleanly to common referral follow-ups such as first-share reminders, milestone pushes, and reward emails.

What if I connected Customer.io after importing participants into GrowSurf?

You can backfill a fix for this case: connect the integration, export your Customer.io people as CSV, then import that CSV into GrowSurf so the referral attributes sync back onto those records.

Set up your refer a friend program with customer referral and affiliate program software that lowers your acquisition costs, increases customer loyalty, and saves you gobs of time.

Trusted by marketing and product teams at fast-growing B2C, fintech, and SaaS companies