CONNECTIONS / BigQuery / BigQuery to Snap Custom Audience
From BigQuery datasets to Snapchat audience matching.
Point Signals at the dataset behind a read-only service account, and it matches your segments into Snapchat for targeting and customer suppression on the cadence your scheduled query already keeps.
- ● bigquery → snap.audience :: live
- > read audiences.segment_members rows=45,612
- hash sha256(email,phone) consent=filtered
- route snap deliver
- ✓ delivered · 40,139 matched
WHAT THIS ENABLES
BigQuery to Snapchat Custom Audience
BigQuery to Snapchat Custom Audience: A scheduled query reads the customer segments in your BigQuery tables, and Signals matches your segments into Snapchat for targeting and customer suppression, hashed and consent-checked whenever the scheduled query reruns.
- Signals matches your segments into Snapchat for targeting and customer suppression, reading your BigQuery tables whenever the scheduled query reruns.
- Snapchat audiences that stay in step as the segment rebuilds, fed by analytics engineers running BigQuery scheduled queries.
WHAT FLOWS WHERE
BigQuery to Custom Audience, mapped.
A scheduled query hands the customer segments to Signals, which hashes and consent-filters each row before Snapchat's Custom Audiences API logs the match-ready audiences for list sizing on Snapchat.
A scheduled query hands the customer segments to Signals, which hashes and consent-filters each row before Snapchat's Custom Audiences API logs the match-ready audiences for list sizing on Snapchat.
Built for the teams that own the number.
Analytics engineers running BigQuery scheduled queries who need Snapchat audiences that stay in step as the segment rebuilds.
From kickoff to verified events.
-
Connect
A read-only service account with dataViewer on the one dataset you nominate to feed Snapchat's Custom Audiences API, sized for list sizing on Snapchat.
-
Map
A scheduled query reads your BigQuery tables, and its columns map to Snapchat's Custom Audiences API in the visual mapper, hashed and checked for list sizing on Snapchat.
-
Deliver
Whenever the scheduled query reruns, Signals matches your segments into Snapchat for targeting and customer suppression, scans only the rows the query changed, with list sizing on Snapchat watched in the debugger.
What ships with this use case.
Snapchat audiences that stay in step as the segment rebuilds on every run, since Signals scans only the rows the query changed.
Audiences that rebuild as the segment does, delivered whenever the scheduled query reruns without BigQuery slot cost climbing.
Each run returns a match report on list sizing on Snapchat from Snapchat's Custom Audiences API, read from your BigQuery tables whenever the scheduled query reruns, at flat BigQuery slot cost.
What Custom Audience actually receives.
- ● signals :: audience upload
- > POST /audience_match source=bigquery.audiences.segment_members
- schema ["EMAIL_SHA256","PHONE_SHA256"]
- external_audience_id "aud_56045"
- id_list_size 45,612 · matched 40,139
- ✓ accepted match=88%
Adjacent moves on the same stack.
from BigQuery
BigQuery to Meta Custom Audience
BigQuery to Meta Custom Audience: A scheduled query reads the customer segments in your…
Learn more
from BigQuery
BigQuery to Google Customer Match
BigQuery to Google Customer Match: A scheduled query reads the customer segments in your…
Learn more
same use case
ActiveCampaign to Snap Custom Audience
ActiveCampaign to Snapchat Custom Audience: Signals reads your ActiveCampaign contacts and…
Learn moregeneric
Snap Custom Audience
Build and refresh Snap audiences from your CRM, warehouse, or SingleView with hashed…
Learn moreAsked on almost every call.
How often does the BigQuery Snap Custom Audience sync run?
The scheduled query sets the pace: rebuild the customer segments nightly and delivery to Snapchat is nightly, or refresh hourly for an hourly feed. Each run only reads the rows the query changed, so Snapchat audiences that stay in step as the segment rebuilds stays current for list sizing on Snapchat while BigQuery slot cost barely moves.
What match rate should a BigQuery-sourced Snap Custom Audience batch expect?
Coverage in your BigQuery tables decides the rate, not BigQuery. A row with a current hashed email or phone matches; one missing both cannot, however the query is tuned. The first run's report from Snapchat's Custom Audiences API sets a baseline, the number Snapchat advertisers building lookalikes and excluding current buyers weigh against list sizing on Snapchat.
NEXT STEP