CRM integration

Behavioral affiliate triggers in your existing Customer.io workspace.

Customer.io is the engine your product team already uses to fire behavioral messages on user events. Rekomi pushes `affiliate_approved` into the same event stream so onboarding, retention, and affiliate-program flows all live in one data graph.

Customer.io
live
Rekomi
Behavioral-marketing SaaS PLG teams.
Starter plan and above · $29/mo
How it works

From paste-API-key to first paid affiliate in 10 minutes.

01 / 03
Connect

Paste your Customer.io API key into Rekomi. Rekomi runs a test call to verify the key, then pulls your list/audience picker live from Customer.io so you pick the right destination.

02 / 03
Approve

Affiliates apply via your public landing page or your bulk invite. Approve them manually, auto-approve on a campaign, or import an existing affiliate roster from Rewardful and six other platforms via Settings > Migrate.

03 / 03
Sync

Approved affiliates land in your Customer.io list as tagged subscribers within seconds. Rekomi handles idempotency, retries, and per-campaign overrides; you handle the nurture sequence.

What syncs

The exact Customer.io fields Rekomi writes.

No surprise fields, no overwrites of contact data you already have. Empty values are omitted so existing nurture data is preserved.

  • PUT /api/v1/customers/{url-encoded-email} on track.customer.io (US) or track-eu.customer.io (EU)
  • email, first_name, last_name, created_at (Unix timestamp)
  • rekomi_tags, comma-separated tag names, prefixed to avoid Customer.io reserved-name collisions
  • Idempotent upsert: re-syncing the same customer updates in place
  • Region auto-detection: probes US first, fails over to EU
Three use-cases

What Customer.io customers actually do with Rekomi.

Use-case 01

Event-driven affiliate onboarding

Pipe Rekomi's `affiliate_approved` webhook into Customer.io as a custom event. Build a Customer.io Workflow on that event: send Email 1 immediately, wait for 'first click' event, branch on whether they got conversions in the first 7 days. Behavioral routing instead of time-based drip.

Paired commission
Hybrid: $15 first-conversion + 18% RevShare
Use-case 02

PLG-style affiliate qualification

Send the 'become an affiliate' offer only to customers whose product engagement crosses a threshold (e.g., 30-day active + 3+ feature uses). Customer.io's segment builder + Rekomi's bulk-invite API drive the qualification.

Paired commission
Tiered RevShare keyed on Customer.io engagement segment
Use-case 03

Cross-region affiliate cohort

Customer.io's US and EU regions serve different data residencies. If your affiliates span both, Rekomi syncs into whichever region your workspace lives in (auto-detected). EU GDPR + US privacy both stay clean.

Paired commission
Per-region commission with auto-detected sync
Provider-specific handling

Rekomi handles Customer.io's edge cases so you don't have to.

Every CRM API has quirks. Rekomi's integration code was built and audited against the live Customer.iodocs, these are the ones you'd otherwise hit yourself.

Region auto-detection

Customer.io has US (track.customer.io) and EU (track-eu.customer.io) data centers. Rekomi probes US first; if the workspace is on EU, the test call fails over to EU automatically. No region setting required in Rekomi.

URL-encoded customer ID

Customer.io's PUT-by-email endpoint takes the email in the URL path. Rekomi URL-encodes the email (`+` and `@` and `.` all need correct treatment) to avoid 404s on emails with special characters.

Reserved property names

Customer.io reserves `id`, `email`, `created_at`, plus a few others. Rekomi prefixes custom attributes (`rekomi_tags`, `rekomi_status`) to avoid colliding with your product team's existing schema.

Who this is for

Built for SaaS PLG teams running Customer.io alongside product event-tracking. Typical setup: Segment or Rudderstack pipes product events into Customer.io; Customer.io fires behavioral messages. Rekomi adds affiliate events to that same pipeline as another behavioral signal.

FAQ

Common Customer.io questions.

Does Customer.io have an affiliate program?

Customer.io runs an Agency Partner Program for SIs and consultants, separate from customer-facing affiliate programs. Rekomi is the layer for the latter, with Customer.io as the behavioral messaging engine.

Can affiliate events fire Customer.io workflows?

Yes, Rekomi's outbound webhooks can post directly to Customer.io's Track API as custom events. Your Customer.io workflows then trigger on `affiliate_approved`, `commission_earned`, `payout_sent`, same authoring tool as your product onboarding flows.

What's the minimum Customer.io plan?

Customer.io's Essentials plan ($150/month for 5,000 profiles) is the minimum with API access. Premium ($1,250+/month) adds advanced features. Rekomi pairs cleanly with either tier.

Ready when you are

Ten minutes to first click.

14-day free trial. Native Stripe, Paddle, Braintree, and more. No card. Live this afternoon.

  • 14-day free trial
  • Cancel anytime, $0 charged