BigQuery to Facebook Ads
Use customer history from Google BigQuery to build Facebook Ads audiences through Amperity, with BigQuery Sharing inbound, identity resolution and audience selection in Amperity, and the Facebook Marketing API outbound.
Meta Ads Manager docsBigQuery Bridge docs
How to send BigQuery data to Facebook Ads
Share customer data. Publish a BigQuery data listing and configure an inbound Amperity Bridge.
Define the audience. Resolve identity in Amperity and use available purchase history and permissions to select customers.
Update Meta Custom Audiences. Send mapped identifiers through the Meta Ads Manager destination, then configure advertising in Meta.
Build Facebook Ads audiences from customer history
Create repeat-buyer Custom Audiences from available transactions.
Prepare existing-customer Custom Audiences for exclusion in Meta ad sets.
Refresh named Custom Audiences as customer eligibility changes.
Include mapped customer identifiers in customer-list Custom Audiences.
What the BigQuery to Facebook Ads connection supports
Audience or field | Mapping and behavior | Documentation |
|---|---|---|
Named Custom Audience | Set its name and ad account; Amperity creates it if absent. | |
Customer identity | Example mappings: amperity_id → EXTERN_ID, email → EMAIL, phone → PHONE. Check all fields required by the selected send path. | |
Audience membership | Replace Users replaces existing audience members with the sent list. | |
Customer file source | Declare user-provided, partner-provided, or both sources in destination settings. | |
Availability | Allow up to 24 hours after Amperity finishes sending updates. |
Use BigQuery history to refine Facebook audiences
Find customers ready to buy again
Use purchase dates and categories available in Amperity to define a repeat-purchase audience. Send its mapped customer identifiers to Meta, where the media team selects the audience and configures the ad campaign.
Separate buyers from acquisition audiences
Build an existing-buyer Custom Audience from customer history shared through BigQuery. Configure it as an exclusion in the relevant Meta ad sets, and review the result after updates become available. Audience delivery alone does not apply ad-set exclusions.
Set up the BigQuery to Facebook Ads workflow
Create a BigQuery exchange and listing, then grant the generated Amperity subscriber account access. Confirm source types and permissions before syncing the inbound bridge. Follow the BigQuery Bridge setup.
Authorize Meta through OAuth, accept its Custom Audience terms, and set the ad account and audience name. Review identifier mappings and validate a sample in a sandbox before production; hashing does not establish permission to advertise. Follow the Meta Ads Manager setup.