Customer.io events

Send identified Nimriz conversions to Customer.io as customer events through the Journeys Track API.

Availability: Customer.io setup is available on Professional and Enterprise plans.

Requirements

• A Professional plan or higher.
• Customer.io Track API credentials: Site ID and API key.
• The correct Customer.io data region, US or EU.
• Conversion callbacks that include user_data.external_id.

Customer.io documents regional endpoints and Basic authentication in its Track API reference.

Connect Customer.io in Nimriz

1. In Customer.io, open the API credentials for the intended workspace and copy its Site ID and Track API key.
2. Confirm whether the workspace is hosted in the US or EU region.
3. In Nimriz, go to Integrations›Destinations›Browse catalog and choose Customer.io.
4. Enter the Site ID, API key, and Region.
5. Keep the default event name nimriz_conversion or provide the event name used by your campaigns and segments.
6. On Review, enter a temporary Sample external ID and confirm that Customer.io will receive a real customer event. Nimriz does not save the sample ID.
7. Select Save, test, and enable. Nimriz encrypts the credentials, saves the destination disabled, sends the real test event, and enables delivery only when that test succeeds.

If the provider test fails, the saved destination stays disabled. Correct the credentials, region, or event name, then select Retry test and enable.

Changing any of those values invalidates the prior test.

Delivery behavior

US workspaces use track.customer.io; EU workspaces use track-eu.customer.io. Nimriz sends the event to /api/v1/customers/{external_id}/events with Basic authentication and a deterministic event ID for deduplication.

Only identified conversions qualify. Clicks, scans, card events, anonymous activity, internal subject IDs, ip_hash, raw IP, and complete User-Agent strings are not sent.

Troubleshooting

• Credentials rejected: confirm you copied Track API credentials, not an App API bearer token.
• Wrong region: select the region where the Customer.io workspace stores its data. Nimriz does not rely on cross-region redirects.
• Event not visible: confirm the sample or live external ID identifies the expected Customer.io person and review the event name.
• Missing external ID: include user_data.external_id in the conversion callback. Nimriz suppresses the delivery safely without consuming destination volume.