CONNECTIONS / Zithara / Zithara to Meta Custom Audience
From Zithara customer records to Meta lookalike and suppression seeds.
Connect Zithara and point Signals at your Zithara customer records; it keeps Meta audiences synced as adds and removals so lists never drift as records change, hashed and consent-checked for Meta.
- ● zithara → meta.audience :: live
- > read segments rows=67,844
- hash sha256(email,phone) consent=filtered
- route meta deliver
- ✓ delivered · 61,060 matched
WHAT THIS ENABLES
Zithara to Meta Custom Audience
Zithara to Meta Custom Audience: your Zithara customer records, hashed and consent-checked, feed Meta as Signals keeps Meta audiences synced as adds and removals so lists never drift as records change.
- Customer segments from your Zithara customer records activated for Meta, as Signals keeps Meta audiences synced as adds and removals so lists never drift.
- Lookalike seeds and suppression lists that track your live customer base, drawn from your Zithara customer records by retail CRM teams running Zithara.
WHAT FLOWS WHERE
Zithara to Custom Audience, mapped.
Each sync hands the customer segments from your Zithara customer records to Signals, which hashes and filters every record, then Meta's Custom Audiences API logs the match-ready audiences for audience refresh cadence.
Each sync hands the customer segments from your Zithara customer records to Signals, which hashes and filters every record, then Meta's Custom Audiences API logs the match-ready audiences for audience refresh cadence.
Built for the teams that own the number.
Retail CRM teams running Zithara activating Meta lookalike and suppression seeds straight from Zithara customer records.
From kickoff to verified events.
-
Connect
Scoped OAuth access to Zithara, reading only your Zithara customer records to feed Meta's Custom Audiences API, sized for audience refresh cadence.
-
Map
Signals reads your Zithara customer records, and its columns map to Meta's Custom Audiences API in the visual mapper, hashed and checked for audience refresh cadence.
-
Deliver
On each run, Signals pulls your Zithara customer records, keeps Meta audiences synced as adds and removals so lists never drift, and sends only the records that changed, with audience refresh cadence in the debugger.
What ships with this use case.
Lookalike seeds and suppression lists that track your live customer base on every run, as Signals reads your Zithara customer records and sends only the records that changed.
Always-current lookalike seeds and exclusions from your Zithara customer records, with API call volume steady because Signals sends only the records that changed.
A per-run match report from Meta's Custom Audiences API on audience refresh cadence, straight out of your Zithara customer records.
What Custom Audience actually receives.
- ● signals :: audience upload
- > POST /customaudiences source=zithara.segments
- schema ["EMAIL_SHA256","PHONE_SHA256"]
- num_received 67,844 · num_invalid_entries -202
- audience_id "1695523" · session "upsert"
- ✓ accepted match=90%
Adjacent moves on the same stack.
from Zithara
Zithara to Google Customer Match
Zithara to Google Customer Match: your Zithara customer records, hashed and…
Learn more
from Zithara
Zithara to TikTok Custom Audience
Zithara to TikTok Custom Audience: your Zithara customer records, hashed and…
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 does the Zithara Meta Custom Audience sync run?
You set the cadence, from near-real-time to a nightly Zithara sync of your Zithara customer records into Meta. Since Signals sends only the records that changed, lookalike seeds and suppression lists that track your live customer base keeps pace and retail CRM teams running Zithara watch audience refresh cadence. One scoped connection sets it up, cadence adjustable later.
What match rate should a Zithara-sourced Meta Custom Audience batch expect?
In Zithara, match rate tracks the email and phone quality your Zithara customer records carry. Clean identifiers land for Meta; blank ones never will. The first Custom Audiences API report shows retail CRM teams running Zithara where audience refresh cadence needs work, a data-quality task handled in Zithara.
NEXT STEP