Turning Klaviyo Loyalty Segments into Meta and Google Ads Audiences

Loyalty data usually stays inside email. It does not have to. Klaviyo segments built on loyalty profile properties, points balance, lifetime points, whether someone has an unlocked reward waiting, sync natively into Meta and Google Ads audiences, which means the same signal driving your flows can also drive paid targeting and exclusions. The setup is genuinely simple. The part worth understanding upfront is that a synced audience is never the same size as the segment it came from.

Which loyalty segments are actually worth syncing

Not every segment earns an ad budget. A few are worth the setup:

Reward unlocked, not redeemed. People sitting on a usable reward are close to a purchase already, which makes them a good retargeting audience with creative that names the specific reward rather than generic “you have points” messaging.

High lifetime points, low recent activity. Your best historical customers who have gone quiet. This is closer to a win-back audience than a top-of-funnel one, and the messaging should reflect that they are being brought back, not introduced to the program.

Points expiring soon, above the reward threshold. The same segment a Klaviyo win-back flow would use, run in parallel as a Meta or Google audience for the same window. Paid and email reinforcing the same message to the same people in the same few days is a reasonable use of a small, time-boxed budget.

Lifetime points, as a lookalike seed. Rather than advertising to the segment directly, use high-lifetime-points customers as the seed audience for a Meta lookalike. This is the one use case here that targets net-new people, not existing loyalty members.

What is generally not worth syncing: broad “all loyalty members” segments. It is too undifferentiated to justify creative built specifically for it, and a generic “thanks for being a member” ad rarely outperforms whatever you would otherwise show that audience.

How the sync actually works

Klaviyo’s native integrations push a segment to Meta or Google as a Custom Audience or Customer Match list. Once built in Klaviyo, syncing is a platform connection and an audience selection, not custom development. The mechanism is standard Klaviyo functionality; what makes it useful here is that the loyalty profile properties (points balance, lifetime points, points expiring soon, next reward at) are ordinary Klaviyo profile properties, so segmenting on them works exactly like segmenting on any other property.

The three constraints that shrink every audience

This is the part that trips people up, because the segment size in Klaviyo and the audience size on the ad platform are never the same number.

Meta requires a minimum of 100 profiles in a segment before it will build an audience at all. A tightly-scoped segment, “points expiring in the next 7 days AND balance covers a reward,” can easily fall under that on a smaller store. If a synced Meta audience never seems to populate, this is the first thing to check.

Only profiles matched to an existing ad account sync. Klaviyo matches on the identifiers it has (usually email, sometimes phone) against Meta’s or Google’s own user base. Not every profile in a Klaviyo segment has a matching, addressable account on the ad platform, so the resulting audience is always smaller than the segment, often meaningfully so.

Google Ads requires Customer Match eligibility on the ad account. This is an account-level requirement set by Google, not something Klaviyo or a loyalty tool can grant. If the account does not qualify, syncing a segment to Google Ads is not available regardless of how the segment is built.

Combined, these three mean a 500-profile Klaviyo segment might land as a 60-person Meta audience, or fail to sync to Google at all if Customer Match eligibility is not in place. Budget and expectations for these campaigns should be set against the realistic synced size, not the Klaviyo segment count.

A worked example

Say a store wants to run a small retargeting push for “reward unlocked, not redeemed” alongside the Klaviyo flow already covering that moment.

1. Build the segment in Klaviyo: Reward Unlocked is true AND Points Redeemed has not occurred since.
2. Check the count. If it clears 100, sync to Meta as a Custom Audience.
3. Set a short campaign window, a week or two, matching how long the underlying reward stays relevant.
4. Write creative that names the reward specifically rather than a generic loyalty message; the audience already knows they have something to spend.
5. Expect the actual Meta audience to run smaller than the Klaviyo segment count, and budget accordingly rather than being surprised by it later.

The honest limit

None of this requires anything beyond Klaviyo’s own native ad integrations and the loyalty profile properties already covered in the Klaviyo integration reference. It is not a replacement for the email flow doing the same job; it is a supplement for stores that already have paid budget and want the same segment logic reflected there. For the flows themselves, here are seven worth building first, each mapped to one of the same profile properties and metrics discussed here.