Receive Klaviyo events
Bring the selected Klaviyo profile, flow, or order event into Adscriptly through a mapped webhook payload or a Zapier workflow you control.
Klaviyo + Meta Ads
Webhook or ZapierLifecycle marketing
Use a selected Klaviyo outcome in a Meta Ads event workflow.
Send a mapped Klaviyo lifecycle or revenue event through a webhook or Zapier, require the property conditions that count, include only permitted event and identity fields, and review the Meta destination.
K
Source
Klaviyo
MA
Destination
Meta Ads
Intended outcome
Keep a specific customer or revenue milestone distinct from a generic profile update before it enters the Meta event path.
Connection scope
This page covers lifecycle and revenue event routing. It does not replace the native Klaviyo Meta audience-sync integration.
What the connection does
Choose which Klaviyo events to send to Meta Ads.
Choose the lifecycle outcome
Use the event name, flow state, segment condition, or order property that represents the business outcome.
Map permitted identity fields
Include only the consented first-party and event fields required for the selected Meta destination.
Review the Meta Ads output
Choose the Meta Ads account and event destination, inspect the mapping, and test the external handoff before enabling it.
Data flow
Know what moves between systems.
KlaviyoAdscriptly logicMeta Ads
Klaviyo
Klaviyo lifecycle or revenue event
Adscriptly logic
Event-name and property check
Meta Ads
Selected Meta event
Klaviyo
Event and mapped properties
Adscriptly logic
Selected event eligibility rule
Meta Ads
Eligible Meta event
Klaviyo
Consented identity and event fields
Adscriptly logic
Normalize the configured event payload
Meta Ads
Matched Meta event
Klaviyo
Klaviyo event or order ID
Adscriptly logic
Stable event identity and duplicate handling
Meta Ads
Stable event record
Setup
Set up and test the Klaviyo event route.
- 01
Choose a Klaviyo trigger
Start with the lifecycle, flow, or revenue milestone that represents the business outcome you want to route.
- 02
Send a test payload
Use Zapier or your webhook sender to deliver representative fields, including consented identity and event fields when attribution depends on it.
- 03
Map the qualification rule
Define the event and property conditions that count. Keep records that do not meet the rule out of the advertising signal.
- 04
Review the Meta Ads destination
Confirm the Meta account or dataset, event name, event time, and value rule before the external handoff is enabled.
Connection controls
Review the connection method, event rule, and destination.
- The connection uses a mapped webhook or Zapier route; it is not a native source integration.
- Klaviyo must send the fields used by the mapping.
- Identity and event fields require appropriate notice, consent, and destination configuration.
- The Meta Ads destination is reviewed before the handoff is enabled.
Related integrations
Integration FAQ
Before you connect.
How does the Klaviyo Meta Ads integration work in Adscriptly?
Adscriptly receives a mapped Klaviyo event through a webhook or Zapier, applies the configured rule, and prepares the eligible outcome for the selected Meta Ads destination.
What must Klaviyo send?
The payload must include the event fields used for qualification and a stable event identifier. When click-level attribution is required, it must also include the supported identifier captured before the handoff.
Does this sync Klaviyo segments to Facebook audiences?
No. Use the native Klaviyo integration for audience sync. This Adscriptly route is scoped to selected lifecycle or revenue events.
Does Adscriptly change records in Klaviyo?
No. This route receives the mapped event for qualification and delivery. It does not edit the source record, workflow, audience, catalog, or storefront configuration.
Klaviyo + Meta Ads
Send a selected Klaviyo event to Meta Ads.
Choose the trigger, send a representative payload, map the rule, and review the destination before enabling the external handoff.
