CONNECTIONS / OneDrive / OneDrive to Meta Custom Audience
From OneDrive files to Meta lookalike and suppression seeds.
Connect OneDrive and point Signals at your OneDrive 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.
- ● onedrive → meta.audience :: live
- > read segments rows=38,460
- hash sha256(email,phone) consent=filtered
- route meta deliver
- ✓ delivered · 33,845 matched
WHAT THIS ENABLES
OneDrive to Meta Custom Audience
OneDrive to Meta Custom Audience: Signals reads your OneDrive 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 OneDrive 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 OneDrive files by teams sharing exports via OneDrive.
WHAT FLOWS WHERE
OneDrive to Custom Audience, mapped.
Each sync hands the customer segments from your OneDrive 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 OneDrive 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.
Teams sharing exports via OneDrive activating Meta lookalike and suppression seeds straight from OneDrive files.
From kickoff to verified events.
-
Connect
Read-only OAuth access to the OneDrive folder you name to feed Meta's Custom Audiences API, sized for audience refresh cadence.
-
Map
Signals picks up your OneDrive 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 OneDrive 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 OneDrive files and processes only the newly dropped file.
Always-current lookalike seeds and exclusions from your OneDrive 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 OneDrive files.
What Custom Audience actually receives.
- ● signals :: audience upload
- > POST /customaudiences source=microsoft-onedrive.segments
- schema ["EMAIL_SHA256","PHONE_SHA256"]
- num_received 38,460 · num_invalid_entries -96
- audience_id "1680167" · session "upsert"
- ✓ accepted match=88%
Adjacent moves on the same stack.
from OneDrive
OneDrive to Google Customer Match
OneDrive to Google Customer Match: Signals reads your OneDrive files and projects your…
Learn more
from OneDrive
OneDrive to TikTok Custom Audience
OneDrive to TikTok Custom Audience: Signals reads your OneDrive files and delivers…
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 OneDrive Meta Custom Audience sync run?
The pace follows your OneDrive files: Signals sends changes from OneDrive to Meta each time a new file lands. Because it processes only the newly dropped file, lookalike seeds and suppression lists that track your live customer base stays current while teams sharing exports via OneDrive keep audience refresh cadence in view. Delivery needs no export and no manual upload.
What match rate should a OneDrive-sourced Meta Custom Audience batch expect?
Coverage of hashed identifiers across your OneDrive files decides it, and teams sharing exports via OneDrive own that inside OneDrive. A live email or phone matches into Meta; neither, and it will not. First-run feedback flags audience refresh cadence, which teams sharing exports via OneDrive then raise inside your OneDrive files.
NEXT STEP