CONNECTIONS / Shopify / Shopify to Meta Custom Audience
Shopify buyers, organized into Meta Custom Audiences.
Signals segments your Shopify customer base, hashes emails and phones, and keeps the matching Meta audiences stocked with current buyers.
- ● shopify → meta.custom_audience :: live
- > sync segment repeat_purchasers rows=22,540
- hash sha256(email,phone)
- route meta.custom_audience upsert
- ✓ audience refreshed · 18,930 matched
WHAT THIS ENABLES
Shopify to Meta Custom Audience
Shopify to Meta Custom Audience keeps Meta's Custom Audiences built from your Shopify customer list, hashing emails and phone numbers at sync and pushing adds and removals on a refresh cadence you set, so suppression and lookalike campaigns always reflect who actually shops with you.
- Store customer data powering Meta audiences without an app per use case.
- Repeat-buyer and VIP segments targetable the day you define them.
- Purchasers pulled out of prospecting audiences right after checkout.
WHAT FLOWS WHERE
Shopify to Custom Audience, mapped.
Customer segment updates leave Shopify, are hashed within Signals, and populate the audience via Meta's Custom Audiences API.
Customer segment updates leave Shopify, are hashed within Signals, and populate the audience via Meta's Custom Audiences API.
Built for the teams that own the number.
D2C teams scaling lookalikes from proven repeat purchasers.
Stores suppressing recent buyers to stretch acquisition budgets.
Shopify Plus brands segmenting VIP tiers directly from order history rather than a separate CDP.
From kickoff to verified events.
-
Connect
Scoped app access to Shopify customer records, reversible from admin.
-
Map
Customer emails and phones hashed into Meta's audience schema.
-
Deliver
Segment pushes on your cadence with accepted-count feedback.
What ships with this use case.
Meta audiences built from real purchase behavior, refreshed automatically.
Lookalikes seeded by your store's best customers.
Buyer suppression that kicks in without waiting for a weekly export.
What Custom Audience actually receives.
- ● signals :: audience upload
- > POST /customaudiences source=shopify.customers
- schema ["EMAIL_SHA256","PHONE_SHA256"]
- num_received 22,540 · num_invalid_entries 177
- audience_id "1740…" · session "upsert"
- ✓ accepted match=84%
Adjacent moves on the same stack.
from Shopify
Shopify to Google Customer Match
Shopify to Google Customer Match rebuilds a Google Customer Match audience from a Shopify…
Learn more
from Shopify
Shopify to TikTok Custom Audience
Shopify to TikTok Custom Audience keeps a TikTok audience synced with a Shopify customer…
Learn more
same use case
ActiveCampaign to Meta Custom Audience
ActiveCampaign to Meta Custom Audience: Signals reads your ActiveCampaign contacts and deal…
Learn moregeneric
Meta Custom Audience
Build and refresh Meta Custom Audiences from your CRM, warehouse, or SingleView, with…
Learn moreAsked on almost every call.
How often do audiences refresh?
Daily is typical, though the refresh cadence is configurable from hourly to weekly depending on how fast a Shopify segment changes. Stores with frequent repeat-purchase activity often choose a shorter cycle so newly qualifying customers reach the Meta Custom Audience quickly, while smaller catalogs run comfortably on a weekly sync.
What match rate should we expect?
Match rate depends on identifier coverage in the underlying Shopify customer record. Hashed email and phone captured at checkout or account login match best, since Meta can compare more signals per customer. Segments built from guest checkouts with only an email tend to land lower, while accounts carrying both identifiers typically match well above that.
Can we sync to multiple ad accounts?
Yes. A single Shopify segment can push to more than one Meta ad account at once, which suits brands running separate accounts per region or business unit. Each account receives its own upsert from the same hashed segment definition, so there is no need to duplicate the mapping work for every additional destination.
NEXT STEP