CONNECTIONS / Box / Box to Meta Custom Audience
Your Box files, wired to Meta lookalike and suppression seeds.
Connect Box and point Signals at your Box files; 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.
- ● box → meta.audience :: live
- > read segments rows=12,875
- hash sha256(email,phone) consent=filtered
- route meta deliver
- ✓ delivered · 11,588 matched
WHAT THIS ENABLES
Box to Meta Custom Audience
Box to Meta Custom Audience: Signals reads your Box files and keeps Meta audiences synced as adds and removals so lists never drift, hashed and consent-checked each time a new file lands.
- Customer segments from your Box files 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 Box files by ops teams sharing exports in Box.
WHAT FLOWS WHERE
Box to Custom Audience, mapped.
Each sync hands the customer segments from your Box files 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 Box files 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.
Ops teams sharing exports in Box activating Meta lookalike and suppression seeds straight from Box files.
From kickoff to verified events.
-
Connect
Read-only OAuth access to the Box folder you name to feed Meta's Custom Audiences API, sized for audience refresh cadence.
-
Map
Signals picks up your Box files, 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 Box files, 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 Box files and processes only the newly dropped file.
Always-current lookalike seeds and exclusions from your Box files, 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 Box files.
What Custom Audience actually receives.
- ● signals :: audience upload
- > POST /customaudiences source=box.segments
- schema ["EMAIL_SHA256","PHONE_SHA256"]
- num_received 12,875 · num_invalid_entries 75
- audience_id "1641191" · session "upsert"
- ✓ accepted match=90%
Adjacent moves on the same stack.
from Box
Box to Google Customer Match
Box to Google Customer Match: Signals reads your Box files and projects your segments into…
Learn more
from Box
Box to TikTok Custom Audience
Box to TikTok Custom Audience: Signals reads your Box files and delivers first-party…
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 Box Meta Custom Audience sync run?
Delivery tracks Box, run by ops teams sharing exports in Box: a near-real-time or scheduled sync of your Box files 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 Box-sourced Meta Custom Audience batch expect?
Match rate follows identifier coverage in your Box files, which ops teams sharing exports in Box control, not Box 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 ops teams sharing exports in Box tune against.
NEXT STEP