Customer.io

Rekomi's Customer.io integration identifies (creates or updates) every approved affiliate in your Customer.io workspace. Customer.io is account-wide with no list picker, segmentation happens via Customer.io's segment rules.

What syncs

When an affiliate is approved (or, optionally, when they apply), Rekomi calls PUT /api/v1/customers/{url-encoded-email} on track.customer.io (or track-eu.customer.io for EU workspaces) with:

• email
• first_name
• last_name
• created_at (Unix timestamp)
• rekomi_tags (comma-separated tag names, prefixed to avoid reserved-name collisions)

The endpoint is safe to retry: re-syncing the same affiliate updates the existing customer with no duplicate.

Region handling

Customer.io has US and EU data centers. Rekomi probes the US region first; if your workspace is on EU, the test call fails over to EU automatically. No region setting is needed in Rekomi.

Finding your credentials

In Customer.io:

1. Account Settings → API Credentials → Track API Keys (URL: https://fly.customer.io/settings/api_credentials).
2. Copy the Site ID and the Track API Key for the workspace you want Rekomi to sync to.

Make sure you copy the Track API key, not the App API key. Rekomi uses the Track API for customer identification, not the App API for messaging.

Connecting Customer.io in Rekomi

1. Go to Integrations in the dashboard sidebar.
2. Click the Customer.io card.
3. Paste your Site ID and Track API key. Click Connect.
4. Rekomi runs a test call against GET /api/v1/accounts/region.

Tags via custom attributes

Customer.io has no first-class tags. Rekomi stores the affiliate's tags as a comma-separated string in a custom attribute named rekomi_tags. To use this for segmentation, build a Customer.io Segment with a rule like:

rekomi_tags contains "Rekomi affiliate"

The Rekomi affiliate system tag is always set.

Referred customers and leads (optional)

Turn on Sync referred customers and leads on the integration page and every sale or lead Rekomi attributes to an affiliate is written to Customer.io as well, matched on email so existing contacts are updated, not duplicated. Each one carries:

• person attributes rekomi_referral_link, rekomi_campaign, rekomi_referring_affiliate, rekomi_referring_affiliate_code, rekomi_last_event, rekomi_last_sale_amount
• attributes rekomi_customer: true or rekomi_lead: true, plus a rekomi_sale or rekomi_lead event you can trigger campaigns on
• Affiliates synced by the section above also get Rekomi referral link, Rekomi campaign and Rekomi affiliate status in the same fields, so you can merge a partner's link into your emails.

Refunded, denied and fraud-quarantined conversions are never pushed, and imported historical conversions are skipped. It is off by default.

When sync fires

• Default: only Approved affiliates sync.
• Optional: turn on "Include applicants before approval" to also sync Pending affiliates.

Per-campaign overrides

Each campaign can override the account-level configuration. From a campaign's detail page, open Settings and use the CRM sync for this campaign section to add campaign-specific tags or disable Customer.io for that campaign.

Per-affiliate sync visibility

Open any affiliate's detail page. The CRM sync panel shows the per-CRM status. Resync clears prior jobs and re-fires the sync.

Troubleshooting

• 401 on both US and EU, Credentials are invalid. Re-copy from Customer.io's API Credentials page and reconnect. Repeated auth failures mark the integration "action needed" and trigger a reconnect email once per breakage; after reconnecting, use Resync all on the Failed tile of the integration page.
• Customer not appearing in your workspace, Customer.io customers are workspace-scoped. Confirm you copied the Site ID + API key from the SAME workspace where you expect the customer to land.
• Reserved attribute warnings in Customer.io, Rekomi uses the rekomi_ prefix on the tags attribute so it never collides with Customer.io reserved names (email, id, created_at, cio_id).

Disconnecting

From the Customer.io connect page, click Disconnect. The integration row and per-campaign overrides are deleted. Historical sync history rows are preserved for audit.

See the customer-io integration overview on the marketing site for use-cases, persona fit, and unique automation patterns.