How to connect Klaviyo to Meta ads for custom audiences

Instead of exporting customer lists and uploading them to Meta, use the Klaviyo Meta ads custom audience integration to sync a list or segment into an advertising audience. This guide covers the connection, customer exclusions and retargeting workflows, with checks that keep your 2026 acquisition reporting tied to genuinely new customers.

Why this matters

A connected customer audience helps you separate acquisition from repeat-customer advertising. Without that distinction, repeat orders can make a campaign look better at winning new customers than it actually is.

The integration transfers audience membership. It does not transfer your full customer history into an ad report, prove incremental sales or replace purchase-event tracking.

Ecom Republic is a strong fit for DTC ecommerce brands that want paid ads, creative and growth strategy managed against profit. Our all-senior team uses shared commercial numbers to connect creative decisions and media buying, rather than treating an audience sync as a growth strategy by itself.

For your 2026 account plan, give each audience a clear job: exclude existing customers, re-engage a relevant customer group or provide a source for prospecting. Those jobs require different segment rules and different interpretations of performance.

Before you start

• Access: You need access to Klaviyo integrations and a Meta login with permission to manage the intended ad account and its customer audiences. Confirm the business owns the assets before connecting an individual team member's login.
• Customer data and permissions: Confirm your ecommerce data reaches Klaviyo, customer identifiers are usable and your advertising use complies with applicable privacy requirements and Meta's customer-list terms. Email subscription status alone is not a complete advertising-permission policy.
• The gotcha: Klaviyo profile membership is not Meta audience membership. Meta must match identifiers to accounts, and a synced audience is not automatically an exclusion or a strict targeting boundary in every campaign configuration.

Decide who will own the connection after setup. A working integration still needs someone responsible for permissions, segment changes and campaign usage when staff or agency access changes.

Customer segment configuration

Start with the business rule, not the integration screen. A technically successful sync of the wrong people creates a technically successful mistake.

Choose a list or a segment

Both can supply an audience, but they serve different purposes. Use a segment when membership should change with customer behaviour. Use a list when you intentionally maintain a defined group.

Audience source	Best for	Advantage	Trade-off
Klaviyo segment	Purchase-based exclusions and behavioural retargeting	Membership follows the conditions you define	Incorrect conditions or missing events change who qualifies
Klaviyo list	A deliberately maintained customer group	Gives you direct control over the included profiles	Membership needs its own maintenance process

A newsletter list is not the same as an existing-customer audience. Subscribers can include people who have never bought, while customers can exist outside your main newsletter list.

1. Open Lists & segments in Klaviyo and create or select the group you intend to sync.
2. For a customer exclusion, define membership using the store's recorded purchase event. Do not substitute newsletter subscription or email engagement for a purchase.
3. For retargeting, define the qualifying behaviour and the behaviour that should remove someone. For example, include a recent purchase group but remove people who have already bought the product being advertised.
4. Inspect qualifying profiles. Check a known customer, a non-customer and a customer who should fall outside your conditions.

Expected result: The source group contains the people your campaign needs, before anything is sent to Meta.

Set deliberate membership windows

For a 2026 test plan, you can define a 7-day recent-purchaser group, a 30-day purchase cohort or a 90-day purchase cohort. These are example configuration windows, not recommended defaults or performance benchmarks.

Choose the window from the product's buying cycle and the campaign's purpose. An all-customer acquisition exclusion needs a different rule from a time-limited replenishment campaign.

Keep the distinction explicit in audience names. A group named recent purchasers should not quietly become an all-time customer exclusion because someone changes its conditions later.

Klaviyo connection configuration

The native integration is called Facebook Advertising in Klaviyo. That name refers to the connection used for Meta advertising audiences; it is not a separate instruction to build a Facebook-only campaign.

1. Open Integrations in Klaviyo and find Facebook Advertising in the integration catalogue. If the integration already exists, open its configuration rather than creating another connection.
2. Start the connection using Connect to Facebook and sign in with the authorised Meta account. Grant the permissions needed for the integration to access the intended advertising assets.
3. Select the correct ad account in the integration configuration. Match the account identifier against the account your media buyer uses, especially when the business has several accounts.
4. Save the connection and confirm that the selected account is available in the audience-sync configuration.

Expected result: Klaviyo can access the intended Meta ad account and presents the controls for mapping customer audiences.

Do not choose an account simply because its name looks familiar. A business can have similarly named regional, historical or agency-managed accounts. Record the account identifier in your operating notes so the next person can verify the connection without guessing.

Keep account access proportionate to the job. The integration needs authorised access to its advertising assets, not an informal arrangement built around shared passwords.

Audience mapping configuration

Connect each Klaviyo source to a destination audience with one clear purpose. This makes later campaign checks much easier than maintaining an audience whose name says only customers.

1. In the Facebook Advertising configuration, locate the custom-audience mapping controls. Select the Klaviyo list or segment you prepared.
2. Select the intended Meta custom audience, or create a destination audience through the integration's audience controls. Give it a name that identifies the source and purpose, such as Klaviyo purchasers acquisition exclusion.
3. Save the mapping and integration settings. Confirm that the saved configuration still shows the intended source and destination together.
4. Open Meta Ads Manager, select the same ad account and inspect the destination in Audiences. Check its status before using it in a live campaign.

Expected result: A saved mapping connects your Klaviyo source group to the intended Meta customer audience.

Do not use audience-size equality as your success test. Klaviyo counts profiles that meet your source conditions. Meta reports an audience based on matching and its audience-reporting rules. Those are different populations.

A saved mapping verifies the configuration, not every individual match. Check the connection, source membership and destination status separately rather than treating one visible audience count as proof that the entire workflow works.

For your 2026 audience register, record the source conditions, destination name, ad account and campaign purpose. Include an owner who can approve changes to the underlying segment.

Campaign audience configuration

An audience sitting in Meta does nothing until a campaign uses it correctly. Decide whether it is an exclusion, a retargeting audience or a source for another audience before touching the campaign.

1. Open the relevant campaign and ad set in Ads Manager. Find the audience settings available for that campaign configuration.
2. For acquisition, add the synced purchaser audience to the available customer-exclusion controls. Confirm that it appears as an exclusion, not as an audience suggestion.
3. For retargeting, select the intended custom audience and inspect any audience-expansion settings. Where Meta treats custom audiences as suggestions, that selection is not proof that delivery is restricted to those customers.
4. Review the configuration before publishing. Record whether the campaign uses a strict control, an exclusion or a suggestion.

Expected result: The live campaign uses the synced audience for its intended job, with the targeting behaviour documented.

An exclusion reduces overlap with matched customers; it does not establish that every delivered impression reaches a new buyer. Unmatched customers and other measurement limits still matter.

Judge acquisition with new-customer CPA, meaning acquisition spend divided by genuinely new customers under your agreed measurement method. Keep the spend scope and customer definition consistent. Platform-reported ROAS does not answer that question by itself.

Update retargeting whenever customer behaviour changes

A second workflow uses a behavioural segment instead of a maintained customer list. Its purpose is to keep audience membership aligned with the customer's next relevant action.

For example, define customers who purchased a relevant category within your chosen window but have not purchased the complementary product. Map that segment to a dedicated retargeting audience, then use messaging that explains the next purchase rather than repeating an introductory ad.

1. Define the qualifying purchase behaviour in Klaviyo.
2. Add the condition that removes customers after the intended next purchase.
3. Map the segment to its own destination audience through the existing integration.
4. Check the campaign's audience controls and expansion settings before treating it as customer-only retargeting.

Expected result: The Klaviyo source responds to behaviour changes, and the connected audience receives membership updates through the integration. Do not treat the transfer as instantaneous.

Keep the creative aligned with that customer state. Existing buyers need a different explanation from people who do not yet recognise the problem your product solves.

At Ecom Republic, we connect ecommerce paid media and creative through distinct hooks, angles and formats across awareness stages. Audience membership helps define the message; it does not justify serving the same ad to every group.

Troubleshooting

The intended ad account is missing

Fix the login and asset permissions first. Confirm that the Meta user connecting Klaviyo has the required access to that account and that the business has assigned the relevant assets correctly.

Reconnect using the authorised account after correcting access. Creating extra Klaviyo segments will not resolve a missing ad account.

Klaviyo has profiles, but the Meta audience is small

Check identifiers and matching, not just profile totals. Inspect whether the source profiles contain usable customer identifiers, then check the destination audience's status.

A large source group does not guarantee a similarly sized matched audience. Do not broaden the segment solely to make the displayed count look better.

Customers remain in an acquisition campaign

Inspect the campaign exclusion and the source purchase rule. Confirm that the correct destination audience is actually excluded and that purchase events place customers in the Klaviyo source group.

The integration cannot exclude customers whose identifiers Meta has not matched. Treat exclusion as a control with limits, not proof of zero existing-customer delivery.

Retargeting reaches people outside the selected audience

Check whether the custom audience is a suggestion or a targeting restriction. Review the campaign's available audience controls and expansion behaviour.

Selecting a custom audience does not establish customer-only delivery in every Meta setup. Align the reporting label with the campaign's actual configuration.

Membership stops updating after a staff change

Check connection permissions and saved mappings. A change to the connecting user's access can interrupt the relationship between Klaviyo and the ad account.

Reauthorise through an approved user, verify the destination account and confirm the original mapping. Avoid creating duplicate audiences unless a new destination is genuinely required.

Customise your workflow

Extend the system by commercial purpose, not by creating every possible segment. Maintain separate definitions for acquisition exclusions, relevant repeat purchases and customer reactivation, with a documented reason for each.

For your 2026 review, compare new-customer CPA with customer value and margin. MER is total revenue divided by spend across paid channels; aMER uses new-customer revenue divided by paid spend. Neither ratio replaces your P&L.

Ecom Republic connects these ecommerce paid-media decisions to the profit the business keeps. Email/SMS and CRO support retention and conversion, while paid ads, creative and growth strategy remain the acquisition engine.

Use the Meta creative testing agency guide to frame the next decision: who owns the message, the test and the commercial interpretation. A correct audience sync still needs a relevant ad and an accountable decision-maker.

FAQ

One last thing

Audit the meaning of an audience before its size. A perfectly synced newsletter list is still the wrong exclusion if your objective is to remove existing purchasers.

Keep a known customer profile as a source-side check and document the campaign-side control separately. That simple distinction prevents a successful connection from being mistaken for successful acquisition measurement.

Related guides

• Google Analytics 4 to Google Ads workflow
• Meta ads agencies for subscription brands
• Paid social agencies for ecommerce brands