CONNECTIONS / Vultr / Vultr to Meta Custom Audience
From Vultr Object Storage files to Meta lookalike and suppression seeds.
Connect Vultr and point Signals at your Vultr Object Storage 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.
- ● vultr → meta.audience :: live
- > read segments rows=17,092
- hash sha256(email,phone) consent=filtered
- route meta deliver
- ✓ delivered · 12,648 matched
WHAT THIS ENABLES
Vultr to Meta Custom Audience
Vultr to Meta Custom Audience: Signals reads your Vultr Object Storage 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 Vultr Object Storage 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 Vultr Object Storage files by developers on Vultr Object Storage.
WHAT FLOWS WHERE
Vultr to Custom Audience, mapped.
Signals picks up the customer segments from your Vultr Object Storage files; Signals hashes and consent-screens each record before Meta's Custom Audiences API accepts the match-ready audiences for audience refresh cadence.
Signals picks up the customer segments from your Vultr Object Storage files; Signals hashes and consent-screens each record before Meta's Custom Audiences API accepts the match-ready audiences for audience refresh cadence.
Built for the teams that own the number.
Developers on Vultr Object Storage activating Meta lookalike and suppression seeds straight from Vultr Object Storage files.
From kickoff to verified events.
-
Connect
A read-only S3 key scoped to the Vultr bucket you name to feed Meta's Custom Audiences API, sized for audience refresh cadence.
-
Map
Signals picks up your Vultr Object Storage 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 Vultr Object Storage 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 Vultr Object Storage files and processes only the newly dropped file.
Always-current lookalike seeds and exclusions from your Vultr Object Storage 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 Vultr Object Storage files.
What Custom Audience actually receives.
- ● signals :: audience upload
- > POST /customaudiences source=vultr.segments
- schema ["EMAIL_SHA256","PHONE_SHA256"]
- num_received 17,092 · num_invalid_entries 379
- audience_id "1654231" · session "upsert"
- ✓ accepted match=74%
Adjacent moves on the same stack.
from Vultr
Vultr to Google Customer Match
Vultr to Google Customer Match: Signals reads your Vultr Object Storage files and projects…
Learn more
from Vultr
Vultr to TikTok Custom Audience
Vultr to TikTok Custom Audience: Signals reads your Vultr Object Storage 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 Vultr Meta Custom Audience sync run?
You set the cadence, from near-real-time to a nightly Vultr sync of your Vultr Object Storage files into Meta. Since Signals processes only the newly dropped file, lookalike seeds and suppression lists that track your live customer base keeps pace and developers on Vultr Object Storage watch audience refresh cadence. One scoped connection sets it up, cadence adjustable later.
What match rate should a Vultr-sourced Meta Custom Audience batch expect?
In Vultr, match rate tracks the email and phone quality your Vultr Object Storage files carry. Clean identifiers land for Meta; blank ones never will. The first Custom Audiences API report shows developers on Vultr Object Storage where audience refresh cadence needs work, a data-quality task handled in Vultr.
NEXT STEP