CONNECTIONS / Wasabi / Wasabi to Meta Custom Audience
Wasabi objects into Meta, built for Meta lookalike and suppression seeds.
Connect Wasabi and point Signals at your Wasabi objects; it keeps Meta audiences synced as adds and removals so lists never drift each time a new file lands, hashed and consent-checked for Meta.
- ● wasabi → meta.audience :: live
- > read segments rows=30,752
- hash sha256(email,phone) consent=filtered
- route meta deliver
- ✓ delivered · 25,832 matched
WHAT THIS ENABLES
Wasabi to Meta Custom Audience
Wasabi to Meta Custom Audience: your Wasabi objects, hashed and consent-checked, feed Meta as Signals keeps Meta audiences synced as adds and removals so lists never drift each time a new file lands.
- Customer segments from your Wasabi objects 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 Wasabi objects by teams archiving to Wasabi.
WHAT FLOWS WHERE
Wasabi to Custom Audience, mapped.
Each sync hands the customer segments from your Wasabi objects 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 Wasabi objects 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.
Teams archiving to Wasabi activating Meta lookalike and suppression seeds straight from Wasabi objects.
From kickoff to verified events.
-
Connect
A read-only key scoped to the Wasabi bucket you name to feed Meta's Custom Audiences API, sized for audience refresh cadence.
-
Map
Signals picks up your Wasabi objects, 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 Wasabi objects, keeps Meta audiences synced as adds and removals so lists never drift, and processes only the newly dropped file, 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 Wasabi objects and processes only the newly dropped file.
Always-current lookalike seeds and exclusions from your Wasabi objects, with transfer overhead steady because Signals processes only the newly dropped file.
A per-run match report from Meta's Custom Audiences API on audience refresh cadence, straight out of your Wasabi objects.
What Custom Audience actually receives.
- ● signals :: audience upload
- > POST /customaudiences source=wasabi.segments
- schema ["EMAIL_SHA256","PHONE_SHA256"]
- num_received 30,752 · num_invalid_entries -336
- audience_id "1698169" · session "upsert"
- ✓ accepted match=84%
Adjacent moves on the same stack.
from Wasabi
Wasabi to Google Customer Match
Wasabi to Google Customer Match: your Wasabi objects, hashed and consent-checked, feed…
Learn more
from Wasabi
Wasabi to TikTok Custom Audience
Wasabi to TikTok Custom Audience: your Wasabi objects, hashed and consent-checked, feed…
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 Wasabi Meta Custom Audience sync run?
Delivery tracks Wasabi, run by teams archiving to Wasabi: a near-real-time or scheduled sync of your Wasabi objects feeds Meta on that cadence. Each run processes only the newly dropped file, so always-current lookalike seeds and exclusions holds up on audience refresh cadence. The live debugger confirms every delivery inline.
What match rate should a Wasabi-sourced Meta Custom Audience batch expect?
Match rate follows identifier coverage in your Wasabi objects, which teams archiving to Wasabi control, not Wasabi itself. A record with a current hashed email or phone matches for Meta; one missing both cannot. First-run feedback from Custom Audiences API pinpoints audience refresh cadence, the number teams archiving to Wasabi tune against.
NEXT STEP