01
Customer identity stays customer-owned
Only conversions carrying your external ID qualify for Klaviyo. Nimriz never substitutes an internal account, touch, card, or user identifier.
CRM and lifecycle
LiveSend identified conversions to Klaviyo
Turn attributed link outcomes into Klaviyo profile events using the external identifier and metric your lifecycle flows expect.
- Identified conversions
- Conversion value and currency
- Campaign context
Event flow
Async deliveryConversion APIAttributed conversionKlaviyo profile event
Nimrizredact · filter · map
Klaviyo
Bot traffic is excluded by default. Delivery runs off the redirect path with automatic retries.
Why Klaviyo with Nimriz
Feed campaign outcomes into Klaviyo without treating every click as a person. Nimriz creates an event only when your backend supplies the external customer identifier required for the profile.
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 Klaviyo 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
Klaviyo 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.
Create server-side profile events through the Klaviyo Events API with a scoped private key.
Plan note
Klaviyo lifecycle delivery is available on Professional and Enterprise plans.
- Delivery
- Server-side Klaviyo Create Event request
- Authorization
- Private API key with events:write
- Identity
- Customer external ID on the event profile
- Deduplication
- Stable event or conversion ID as unique_id
Guided setup
Connected in four reviewed steps.
- 01
Create a scoped key
Create a private API key with events:write.
- 02
Choose the metric
Keep Nimriz Conversion or enter the metric used by your flows.
- 03
Send a test event
Use a temporary sample external ID to create a real profile event.
- 04
Enable delivery
Nimriz enables delivery after the saved key and metric pass the real test.
Use cases
- Lifecycle flow triggers
- Profile segmentation
- Revenue outcome messaging
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 Klaviyo 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
Customer.io
Turn attributed link outcomes into Customer.io customer events using the external identifier your lifecycle programs already recognize.
Beta
Pipedrive
Create completed activities on exactly matched Pipedrive People.
Beta
Attio
Attach conversion notes to exactly matched existing Attio records.