BigQuery to Klaviyo
Use customer history from Google BigQuery to prepare Klaviyo lists and profile attributes through Amperity, with BigQuery Sharing inbound, identity resolution and audience selection in Amperity, and the Klaviyo REST API outbound.
See the Klaviyo docsBigQuery Bridge docs
How to send BigQuery data to Klaviyo
Share selected customer data. Publish a BigQuery data listing and configure its subscriber permissions for an inbound Amperity Bridge.
Define an email-keyed audience. Resolve identity in Amperity, then select customers and profile fields using available history.
Update the Klaviyo list. Send query results through the Klaviyo destination; enable profile updates when including customer attributes.
Build Klaviyo lists from BigQuery customer history
Prepare store-buyer lists from available transaction history.
Populate Klaviyo profiles with selected purchase-context properties.
Refresh replenishment audiences in named Klaviyo lists.
Supply location attributes for Klaviyo profile-based segmentation.
What the BigQuery to Klaviyo connection supports
Audience or field | Mapping and behavior | Documentation |
|---|---|---|
Audience list | Send email-keyed query results to an existing or new named list; validate membership behavior before production. | |
Profile identity | Use email as the audience key; alias a chosen external identifier to external_id when needed. | |
Standard attributes | Map given_name to first_name and surname to last_name; enable profile updates. | |
Location | Map address1, city, region, and zip into the nested location object. | |
Custom properties | Other columns become properties. NULL columns explicitly clear the corresponding field. |
Bring purchase context into Klaviyo audiences
Follow up with store buyers
Identify customers who bought a product in a store using transaction history shared through BigQuery. Send their email addresses and selected product attributes to Klaviyo, where the team can prepare relevant follow-up messaging and apply current consent controls.
Prepare a replenishment list
Define a replenishment audience from purchase dates and categories available in Amperity. Send updates to its named Klaviyo list on your chosen schedule, and use selected custom properties to give the messaging team purchase context.
Set up the BigQuery to Klaviyo workflow
Create a BigQuery exchange and listing, then grant the Amperity-generated subscriber account access. Verify source types and permissions before syncing the inbound connection. Follow the BigQuery Bridge setup.
Authorize Klaviyo with OAuth or a private API key with lists:write and profiles:write scopes. Review profile-update settings, NULL clearing, and current consent; validate list membership and attributes with a sandbox sample before production. Follow the Klaviyo destination setup.