Klaviyo events

Send identified Nimriz conversions to Klaviyo as profile events for lifecycle segmentation and flows.

Availability: Klaviyo setup is available on Professional and Enterprise plans.

Requirements

• A Professional plan or higher.
• A Klaviyo private API key with events:write.
• Conversion callbacks that include user_data.external_id.

Nimriz calls the server-side Create Event endpoint and pins API revision 2026-04-15. The revision is managed by Nimriz and is not an editable destination field.

Connect Klaviyo in Nimriz

1. In Klaviyo, create or choose a private API key with the events:write scope.
2. Go to Integrations›Destinations›Browse catalog and choose Klaviyo.
3. Paste the Private API key.
4. Keep the default metric name Nimriz Conversion or enter the metric your flows and segments expect.
5. On Review, enter a temporary Sample external ID and confirm that Klaviyo will receive a real profile event. Nimriz does not save the sample ID.
6. Select Save, test, and enable. Nimriz encrypts the key, 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 key or metric, then select Retry test and enable.

Changing the key or metric invalidates the prior test.

Delivery behavior

Nimriz sends the customer identifier as the Klaviyo profile external_id. The configured metric identifies the event, and the stable Nimriz event or conversion ID becomes unique_id so retries do not create another logical event. Klaviyo explains this behavior in its Events API overview.

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

• Key rejected: confirm the value is a private API key and includes events:write.
• Event accepted but not found: review the profile external ID, metric name, and event filters.
• Flow did not run: verify the Klaviyo flow uses the configured metric and that its own filters permit the test profile.
• Missing external ID: include user_data.external_id in the conversion callback. Nimriz suppresses the delivery safely without consuming destination volume.