01
Customer identity stays customer-owned
Only conversions carrying your external ID qualify for Customer.io. Nimriz never substitutes an internal account, touch, card, or user identifier.
CRM and lifecycle
LiveSend identified conversions to Customer.io
Turn attributed link outcomes into Customer.io customer events using the external identifier your lifecycle programs already recognize.
- Identified conversions
- Conversion value and currency
- Campaign context
Event flow
Async deliveryConversion APIAttributed conversionCustomer.io event
Nimrizredact · filter · map
Customer.io
Bot traffic is excluded by default. Delivery runs off the redirect path with automatic retries.
Why Customer.io with Nimriz
Use attributed campaign outcomes in lifecycle automation without sending an anonymous click stream. Nimriz routes each qualifying conversion to the correct Customer.io region and customer identifier.
02
Conversion context without anonymous activity
Send conversion type, value, currency, campaign context, and mapped properties without forwarding clicks, scans, raw IP, or complete User-Agent strings.
03
Verified before delivery starts
A real provider test confirms the current Customer.io configuration before live conversion delivery can be enabled.
Conversion bridge
From click to attributed conversion.
Conversions carry type, value, and currency, with deduplication through stable event identifiers and idempotency keys. Refunds, cancellations, and reversals reference the original sale instead of overwriting it.
- 01
Your backend reports a conversion
The signed Conversion API request includes a customer-supplied external ID and the outcome details you want to track.
- 02
Nimriz resolves attribution
The conversion joins its eligible link touch and keeps the customer identifier outside the canonical integration event.
- 03
Destination rules are applied
Filters and mapping shape the conversion while privacy rules remove identifiers that the destination does not need.
- 04
Customer.io receives the identified event
Delivery runs asynchronously with safe retries, stable identifiers, and customer-safe delivery health.
Under the hood
What Nimriz sends, and how.
Post identified customer events through the US or EU Journeys Track API with Basic authentication.
Plan note
Customer.io lifecycle delivery is available on Professional and Enterprise plans.
- Delivery
- Journeys Track API customer event
- Regions
- Explicit US or EU endpoint selection
- Identity
- Customer external ID in the request path
- Deduplication
- Deterministic ULID for the logical conversion event
Guided setup
Connected in four reviewed steps.
- 01
Choose credentials
Copy the Track API Site ID and API key for the workspace.
- 02
Select the region
Choose US or EU and confirm the conversion event name.
- 03
Send a test event
Use a temporary sample external ID to create a real customer event.
- 04
Enable delivery
Nimriz enables delivery after the saved credentials and event settings pass the real test.
Use cases
- Lifecycle triggers
- Customer segmentation
- Post-click outcome journeys
Privacy notes
Privacy-aware delivery uses only the customer-supplied external ID for matching and omits anonymous activity, internal subject IDs, visitor hashes, raw IP, and complete User-Agent strings.
Nimriz never forwards raw IP addresses or complete User-Agent strings in integration payloads. Strict privacy mode omits visitor hashes and selected granular fields such as city.
Analytics privacy docsMore in CRM and lifecycle
Pair Customer.io with the rest of the catalog.
Live
HubSpot
Turn attributed Nimriz outcomes into HubSpot custom event occurrences matched through the customer identifier your CRM already owns.
Live
Klaviyo
Turn attributed link outcomes into Klaviyo profile events using the external identifier and metric your lifecycle flows expect.
Beta
Pipedrive
Create completed activities on exactly matched Pipedrive People.
Beta
Attio
Attach conversion notes to exactly matched existing Attio records.