Skip to content
Integrations

Connect Sortment to BigQuery

Use customer data from BigQuery to build audiences, find lifecycle opportunities, personalize campaigns, and measure performance in Sortment.

Guided setup · Live in a day · No migration · Compatible with leading ESPs

From signal to action

What Sortment can do with BigQuery data

Once connected, Sortment helps your lifecycle team turn warehouse data into audiences, campaigns, and performance insights without waiting on one-off data pulls.

Builds the audience and routes it

Create segments from customer profiles, events, transactions, and lifecycle traits stored in BigQuery, without relying on the engineering team.

Finds the drop before your team notices it

Surface drop-offs, retention gaps, conversion windows, and high-intent audiences from customer behavior proactively.

Create campaigns

Turn approved opportunities into campaign briefs, content, journeys, and tests.

Perform RCA

Sortment distinguishes between causes, ranks the most likely ones, and rules out the ones that don't fit.

Getting started

We'll help you connect BigQuery

Sortment works with your technical owner to set up the connection, map the right data, and validate the first lifecycle workflow.

View setup docs

1 Follow the setup guide

Your technical owner uses the BigQuery setup guide to share the required access. Sortment can join the setup process to confirm permissions and answer questions.

2 Map the right data

We help identify the customer tables, events, user IDs, and lifecycle fields Sortment should use first, so your team does not have to define everything from scratch.

3 Check that everything works

Once connected, we validate that audiences, attributes, and campaign data are flowing correctly before your team starts using Sortment in live workflows.

Start where you are. Go as far as you want.

How teams use Sortment

Add Sortment to Braze, Iterable, or any other ESP without migrating, or use it to replace your CEP entirely.

With your existing stack

Full CEP replacement

Keep your CEP, add Sortment where it helps.

Your BigQuery. Your ESP. Sortment sits in between.

Sortment monitors customer data in BigQuery, finds lifecycle opportunities, and turns them into audiences, attributes, and campaign direction your team can send through your ESP.

Replace scattered tools with one AI-native CEP.

One platform. Every channel. No handoffs.

Sortment replaces your CEP entirely. Journeys, campaigns, segments, content, analytics, and AI agents all run in one platform.

No more coordinating across Asana, Jira, or Slack. No shared resources, no data team tickets, no waiting. Everything your lifecycle team needs to execute, in one place.

Ready to connect your BigQuery?

Read the setup guide to connect BigQuery.

View setup docs

FAQs

Can Sortment send campaigns and run journeys?
Yes. Sortment supports full campaign and journey orchestration, including event and segment triggers, delays, branching, frequency caps, exits, and multi-channel delivery across email, push, and more.
Do I need a technical team to use Sortment?
No. Minimal engineering help is needed for the initial setup, usually about an hour. After that, Sortment’s AI agents handle everything. Your team can engage with your audience without requiring technical assistance.
Will migrating from my current tools be difficult?
No. Sortment's AI migration agents move your campaigns, journeys and templates over within a day, with white-glove onboarding for every customer. Your campaigns will continue to run smoothly throughout the transition.
Does Sortment work with my existing stack?
Yes. Sortment integrates with all popular analytics, product, CRM, and data tools. We’re constantly adding new integrations so you can connect and grow with confidence.
Is Sortment secure and compliant?
Yes. Sortment is SOC 2 compliant, ISO 27001 certified, and GDPR compliant. Your data is always safe, private, and never used for model training.

See what Sortment can do for your goals.

Book a 30-minute call. We'll walk you through Sortment with your goals, your data and your stack in mind.

No migration · Works alongside your existing stack