Meta Custom Audience
Meta Custom Audiences, refreshed automatically.
Build and refresh Meta Custom Audiences from your CRM, warehouse, or SingleView, with hashed identifiers and scheduled updates.
- ● meta.custom_audience :: live
- > segment high_ltv_customers size=48,210
- hash sha256(em,ph) schema=EMAIL_SHA256,PHONE_SHA256
- sync add 1,240 · remove 380 match 74%
- ✓ uploaded · audience updated
WHAT THIS ENABLES
Meta Custom Audience
Meta Custom Audience is the automated sync that builds and refreshes Meta audiences from your CRM, warehouse, or SingleView, uploading hashed identifiers on a schedule so suppression, lookalike, and retention lists never go stale.
- Acquisition budget stops paying to reach people who have already bought.
- Lookalike models seeded from your highest-value cohorts rather than a stale export.
- Audience membership that tracks your source data instead of a quarterly manual re-upload.
Built for the teams that own the number.
Brands running suppression, lookalike, and retention plays at scale.
From kickoff to verified events.
-
Connect
Audience source connection to CRM, warehouse, or SingleView.
-
Segment
Segment rules or predictive scoring input.
-
Push
Meta Audience push with hashed keys.
-
Refresh
Automatic refresh cadence so audiences never go stale.
WHAT FLOWS WHERE
One use case, every source.
Your segment definition updates in the source system, Signals hashes the member identifiers and computes the additions and removals, then syncs them to Meta's Custom Audiences API.
Your segment definition updates in the source system, Signals hashes the member identifiers and computes the additions and removals, then syncs them to Meta's Custom Audiences API.
What ships with this offering.
Suppression of existing customers from acquisition spend.
Lookalike seeds built from high-LTV cohorts.
Retention and cross-sell audiences kept current.
ON THE WIRE
What the platform actually receives.
Identifiers are hashed with SHA-256 at source. The payload the destination sees never contains raw PII.
- ● signals :: audience payload
- > POST /{audience_id}/users schema=[EMAIL_SHA256,PHONE_SHA256]
- op add · rows 1240
- em sha256 "c81f04…" · ph sha256 "2d6b77…"
- op remove · rows 380
- ✓ audience_updated · num_received 1620
Adjacent moves on the same stack.
cross-channel
Custom Audiences
Datahash builds and refreshes custom audiences across Meta, Google, Snap, TikTok, LinkedIn, and X from your CRM, warehouse, or SingleView.
Learn more
Google Customer Match
Datahash builds and refreshes Google Customer Match audiences from your CRM, warehouse, or SingleView, with hashed identifiers.
Learn more
snap
Snap Custom Audience
Build and refresh Snap audiences from your CRM, warehouse, or SingleView with hashed identifiers.
Learn more
meta
Meta Web CAPI
Datahash is a Meta Business Partner. We set up Meta Conversions API on your website server-side, deduped with your existing Meta Pixel, hashed and privacy-safe.
Learn moreBring it from where the data lives.
Every source that supports this use case. Pick a platform to see the exact setup.
CRM
Databases
Files / storage
Data warehouses
Datahash API
Custom
Questions your team will ask.
Do audiences expire on Meta?
Uploaded Custom Audiences persist on Meta indefinitely; they do not expire on their own. What changes is membership, as your source data changes. Because Datahash refreshes the sync on a schedule, people who no longer qualify for a segment are removed and new matches are added automatically, so the audience stays current without anyone re-uploading a list by hand.
What match rate should we expect?
With email and phone present on most records, Meta list match rates commonly land between 50 and 80 percent for Custom Audience uploads. More hashed keys per record, such as name or external ID, improve the match further. Datahash reports the accepted audience size and match rate after every sync, so you always know how many uploaded users Meta actually matched.
Can one audience feed multiple ad accounts?
Yes. The same segment definition, whether it is a suppression list, a lookalike seed, or a retention cohort, can push to several ad accounts under one Business Manager. Each destination ad account keeps its own refresh schedule and match reporting, so teams running campaigns from different accounts can share one audience source without duplicating the segment logic.
NEXT STEP
Live in fifteen minutes. Measurable in a week.
Talk to our team of solutions engineers. We map your source data, propose an integration plan, and give you a live setup in the same call where possible.