CONNECTIONS / FTP / FTP to Meta Custom Audience
Your FTP drops, wired to Meta lookalike and suppression seeds.
Signals reads your FTP drops through read-only credentials scoped to the SFTP path you name, then keeps Meta audiences synced as adds and removals so lists never drift so Meta sees match-ready audiences without an export.
- ● ftp → meta.audience :: live
- > read segments rows=22,746
- hash sha256(email,phone) consent=filtered
- route meta deliver
- ✓ delivered · 19,334 matched
WHAT THIS ENABLES
FTP to Meta Custom Audience
FTP to Meta Custom Audience: your FTP drops, 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.
- Signals keeps Meta audiences synced as adds and removals so lists never drift, reading your FTP drops each time a new file lands.
- Always-current lookalike seeds and exclusions, with no export step out of your FTP drops.
WHAT FLOWS WHERE
FTP to Custom Audience, mapped.
Signals reads the customer segments from your FTP drops each time a new file lands, hashes and screens each record, and posts the match-ready audiences to Meta's Custom Audiences API, keeping audience refresh cadence in view.
Signals reads the customer segments from your FTP drops each time a new file lands, hashes and screens each record, and posts the match-ready audiences to Meta's Custom Audiences API, keeping audience refresh cadence in view.
Built for the teams that own the number.
Teams exporting nightly to SFTP who need lookalike seeds and suppression lists that track your live customer base out of FTP drops.
From kickoff to verified events.
-
Connect
Read-only credentials scoped to the SFTP path you name, mapped to Meta's Custom Audiences API and tuned for audience refresh cadence.
-
Map
Columns from your FTP drops align to Meta's Custom Audiences API in the visual mapper, hashed as the file lands and checked for audience refresh cadence.
-
Deliver
Each time a new file lands, Signals reads your FTP drops and keeps Meta audiences synced as adds and removals so lists never drift, processes only the newly dropped file, with audience refresh cadence watched in the debugger.
What ships with this use case.
Lookalike seeds and suppression lists that track your live customer base from your FTP drops, delivered each time a new file lands.
Always-current lookalike seeds and exclusions out of your FTP drops, delivered each time a new file lands without transfer overhead climbing.
Match feedback on audience refresh cadence from Meta's Custom Audiences API each run, tied back to your FTP drops.
What Custom Audience actually receives.
- ● signals :: audience upload
- > POST /customaudiences source=ftp.segments
- schema ["EMAIL_SHA256","PHONE_SHA256"]
- num_received 22,746 · num_invalid_entries 278
- audience_id "1696578" · session "upsert"
- ✓ accepted match=85%
Adjacent moves on the same stack.
from FTP
FTP to Google Customer Match
FTP to Google Customer Match: your FTP drops, hashed and consent-checked, feed Google Ads…
Learn more
from FTP
FTP to TikTok Custom Audience
FTP to TikTok Custom Audience: your FTP drops, hashed and consent-checked, feed TikTok as…
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 FTP Meta Custom Audience sync run?
You set the cadence, from near-real-time to a nightly FTP sync of your FTP drops into Meta. Since Signals processes only the newly dropped file, lookalike seeds and suppression lists that track your live customer base keeps pace and teams exporting nightly to SFTP watch audience refresh cadence. One scoped connection sets it up, cadence adjustable later.
What match rate should a FTP-sourced Meta Custom Audience batch expect?
Match rate follows identifier coverage in your FTP drops, which teams exporting nightly to SFTP control, not FTP 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 exporting nightly to SFTP tune against.
NEXT STEP