Converlay Now Syncs Your Shopify Customers to Meta Custom Audiences and Klaviyo Lists — Server-Side

Custom audiences are one of the highest-value tools in a Shopify merchant's advertising stack. A list of people who bought from you in the last 30 days retargets better than almost anything else you can build. A list of abandoned checkouts, properly suppressed from awareness campaigns and targeted with a recovery sequence, consistently outperforms cold traffic. A segment of high-lifetime-value customers is the foundation of a lookalike audience that actually converts.

The problem is that all three of those audiences are built on browser pixels — and browser pixels have been degrading for years. iOS 14 intelligent tracking prevention, Safari's aggressive cookie expiry, Chrome's third-party cookie changes, and the ad blockers that roughly 40% of online shoppers now run have turned pixel-based audience building into a leaky bucket. The customers who are most valuable to retarget — repeat buyers, high spenders, premium-device users — are disproportionately the ones whose pixels fire least reliably.

Converlay v2.21.0 introduces Audience Sync: a new engine that builds your retargeting segments from the verified server-side event data already flowing through Converlay, and pushes them to Meta Custom Audiences and Klaviyo Lists on a daily schedule — with no CSV uploads, no separate integration, and no dependency on the browser pixel at all.

What the Problem Actually Looks Like

If your Meta Custom Audience for "Purchasers — last 30 days" is built from the Meta Pixel, it only includes customers whose purchase event the pixel fired and sent successfully to Meta. On a typical Shopify store with a standard client-side setup, that is somewhere between 50% and 70% of actual purchases — sometimes less, depending on the customer's device, browser, and consent choices.

The customers who do not appear in that audience are not random. They are systematically skewed toward privacy-conscious shoppers, mobile users on iOS, and anyone using an ad blocker. These are often your best customers. They buy more, they return, and they recommend. They are also the ones most likely to be invisible to your pixel-based retargeting list.

The result is a retargeting audience that is not just smaller than it should be — it is biased. You are showing retargeting ads to the fraction of your customers who opted in to tracking, and missing the fraction who are more valuable but harder to reach. And because the audience is built from incomplete data, the lookalike audiences derived from it inherit the same bias.

How Audience Sync Works

Converlay has always received purchase events, checkout events, and session data on the server side — before any browser restriction, ad blocker, or consent dialog can interfere. That data is stored in Converlay's event store, already tied to verified customer identities.

Audience Sync uses that stored data to build three customer segments automatically:

• Recent purchasers — customers who completed a purchase in the configured lookback window (default 30 days), drawn from server-side purchase events.
• Abandoned checkouts — customers who initiated checkout but did not complete a purchase within the session, drawn from checkout and purchase event pairs.
• High-LTV customers — customers whose total order value across all tracked purchases exceeds the configurable LTV threshold for your store.

Once a day, Converlay runs a diff-based sync for each segment: it computes which customer identifiers should be added to the audience and which should be removed (because they fell out of the lookback window, completed a purchase, or had their data deleted), then pushes only the delta to each platform. Platforms receive hashed, encrypted identifiers — no plaintext email addresses or phone numbers ever leave Converlay.

Consent Is Fail-Closed

Audience Sync is built around the same consent model Converlay uses for all event forwarding. A customer is only included in a synced audience if their most recent tracked event carries explicit consent for both ad_storage and ad_user_data. A customer who has not granted both signals — or whose consent record is ambiguous — is excluded from every audience sync. There is no fallback, no opt-out-based inference, and no way to configure the engine to include unconsented identifiers.

This means the audience you sync to Meta or Klaviyo is smaller than your total customer list — it is the consented subset. But it is also the subset that platforms can legally use for retargeting in GDPR jurisdictions, and the subset that is least likely to generate consent disputes when a customer's ad preferences are audited.

GDPR Purge Is Automatic

When a customer requests data deletion under GDPR, Converlay's existing GDPR flow now includes audience membership. Before purging the customer's local event rows, Converlay removes the customer's hashed identifiers from every platform audience they belong to. If the platform removal fails — a temporary API error, a rate limit — Converlay retains the local row and retries on the next sync cycle, so a transient failure cannot result in a customer remaining in a platform audience after a deletion request has been confirmed.

This sequencing — platform removal first, local purge second — means your GDPR compliance posture is not dependent on a manual process or a separate integration. The same deletion request that removes the customer from Converlay's event store also removes them from your Meta and Klaviyo audiences.

Setting Up Audience Sync

Audience Sync is available on the Converlay Pro plan. To enable it:

1. Open your Converlay dashboard from the Shopify admin.
2. Navigate to the Audiences page in the left sidebar.
3. Connect the platforms you want to sync to. Meta requires a Meta Ads account ID and reads your ad account permissions before enabling — Converlay checks that the account has the necessary Custom Audiences access before allowing any sync.
4. Select the segments you want to enable for each platform. You can enable all three (recent purchasers, abandoned checkouts, high-LTV) or only the ones relevant to your current campaigns.
5. Save your configuration. The first sync runs within 24 hours and subsequent syncs run daily.

Once configured, the Audiences page shows each segment's current member count, the last sync time, and the platform sync status. If a sync encounters a rate limit from Meta or Klaviyo, the page surfaces a rate-limit banner rather than silently reporting success — you always know whether the last sync actually completed.

What This Changes for Retargeting

The immediate practical effect is that your retargeting audiences become more complete. A Meta Custom Audience built from server-side purchase events captures the customers the pixel missed — the iOS users, the ad blocker users, the customers who declined third-party cookies. For most Shopify stores, that is a material increase in audience size, and a more representative one.

The secondary effect is on lookalike audiences. Meta's lookalike algorithm performs better with a larger, more representative seed audience. If your current seed was built from 60% of your actual purchasers, switching to a server-side seed that covers 95% gives the algorithm a more accurate signal about who your actual buyers are — and the lookalike it generates reflects that.

For Klaviyo, the benefit is slightly different. A Klaviyo list built from server-side abandoned checkouts is more complete than one built from browser-triggered flows, because the checkout event fires on the server before any browser issue can prevent it. Merchants who run abandoned checkout sequences in Klaviyo can expect a meaningful increase in the number of customers entered into that flow.

How to Get Started

If you are already on Converlay Pro, Audience Sync is available in your dashboard today. Navigate to the Audiences page to configure your first sync. If you are on a free plan and want to try it, upgrading to Pro unlocks Audience Sync along with the full reports suite, health score monitoring, and priority support.

If you are not yet using Converlay, Audience Sync is one of more than a dozen features available after a single pixel install. Converlay connects your Shopify store to 26 destinations — Google Analytics 4, Meta, TikTok, Pinterest, Klaviyo, and more — via server-side event forwarding that works independently of browser restrictions and ad blockers.

Install Converlay from the Shopify App Store and start building audiences from your complete server-side purchase data today.