A conversion is useful to a CRM only when it belongs to the right customer. Nimriz now sends identified conversions to HubSpot, Customer.io, and Klaviyo using the external identifier supplied by the customer's own conversion callback. Anonymous clicks and internal Nimriz identifiers are never substituted as person identity.
Start with an attributed conversion
Your backend sends a signed conversion to Nimriz with user_data.external_id. Nimriz joins the outcome to its eligible link touch, stores the customer identifier as an identity alias, and resolves it only when a CRM or lifecycle destination is dispatched.
The identifier is not added to the shared canonical event. Analytics, alert, spreadsheet, and warehouse destinations therefore do not receive the CRM identity. If a conversion has no external ID, CRM delivery is suppressed safely without consuming live destination volume.
Send custom events to HubSpot
HubSpot uses managed OAuth and a customer-defined custom behavioral event. You provide the fully qualified event name and the custom matching-ID property configured in HubSpot. Nimriz sends identified conversions through HubSpot's event endpoint and places the external identifier in that matching property alongside mapped conversion fields.
The HubSpot destination is available on Professional and Enterprise plans.
Trigger Customer.io lifecycle events
Customer.io uses a site ID, API key, and explicit US or EU region. Nimriz sends the event to the customer identified by the external ID. The default event name is nimriz_conversion, and a deterministic ULID gives retries a stable provider identifier.
This lets a lifecycle workflow react to an attributed lead or sale without forwarding anonymous link traffic. Customer.io is available on Professional and Enterprise plans.
Record Klaviyo profile events
Klaviyo uses a private API key scoped to event writing. Nimriz sends the configured metric, defaulting to Nimriz Conversion, against a profile external ID. A stable event unique ID prevents a retry from becoming another logical event.
Klaviyo is available on Professional and Enterprise plans.
Test side effects before enabling
CRM provider tests require a non-persisted sample external ID and clearly state that they create a real provider event. Nimriz keeps the destination disabled until the current configuration and authorization pass. Delivery health then reports success, retries, reconnect requirements, and customer-safe errors without storing provider response bodies.
Connect the system that owns follow-up
Use HubSpot when a behavioral event should appear against an exactly matched CRM contact. Use Customer.io or Klaviyo when an identified outcome should enter a lifecycle or messaging workflow. In every case, keep identity customer-owned and send only the conversion context the destination needs.