If Treasure AI is your CDP (Customer Data Platform), you can now push profiles, events and segments straight into Batch. And it works both ways: engagement data from your Batch campaigns flows back into Treasure AI. No CSV exports. No homegrown scripts. Setup happens in the Treasure AI console.
The upshot? A segment rebuilt overnight can power a push, email or SMS campaign the next morning. Then the opens, clicks and unsubscribes from that campaign feed your next round of segments.
Your CDP is full of great data. Your campaigns can't see it.
Treasure AI pulls customer data together at scale: online and in-store purchases, browsing, loyalty, customer service. Your data team builds sharp segments and scores on top of it. Then everything stalls the moment someone tries to use that data in a campaign.
Segments get exported by hand, often once a week.
The attributes you need for personalization (loyalty tier, favorite category) never leave the CDP.
Campaign results don't come back, or show up days late.
The Treasure AI x Batch connector fixes all three.
Three ways to send Treasure AI into Batch
The connector runs on a SQL query or a Treasure AI Audience Studio segment. Every row in the result becomes one operation in Batch. Column names do the mapping for you: identifier, native attribute, custom attribute or event.
Update customer profiles
In Attributes mode, one row updates one profile.
Native attributes: email, phone, email and SMS consent, language, time zone, country, topic preferences.
Custom attributes: up to 50 per profile. Loyalty tier, signup date, interests, average basket.
Use them in Batch to target and personalize your messages.
Send events
In Events mode, one row is one event tied to a profile. An in-store purchase, a new subscription or a cancellation logged in Treasure AI can kick off an automation in Batch.
Sync audiences
In Audience mode, a Treasure AI segment becomes a Batch audience you can include in, or exclude from, any campaign.
Add: new members join the audience.
Remove: members drop out.
Replace: the whole audience is rebuilt on every sync. Leave the segment, leave the Batch audience.
Good to know
You schedule every sync from Treasure AI, as often as you need (daily, hourly or with a cron expression).
The return trip: campaign results flow back into Treasure AI
The integration also runs from Batch to Treasure AI. You can import three kinds of data.
Profiles: native and custom attributes, with an optional Batch segment filter. Last email open and click dates included.
Events: sends, deliveries, opens, clicks, bounces, spam complaints and unsubscribes across email, SMS and push. Filter by orchestration if you like.
Reachability: who you can actually contact, and on which channel (email, push, SMS).
Turn on incremental loading and each run only pulls what's new, within a 90-day window.
Now your data team sees the full picture in Treasure AI: what customers buy, and how they respond to your messages. Someone who opens every email but never buys is not the same as someone who's gone quiet everywhere. They deserve different playbooks.
Four ways to turn data into campaigns
VIP customers segment, rebuilt every night: audience in replace mode, early-access sale campaign by push and email.
In-store purchase sent from the POS: event that triggers a thank-you email with recommendations within 24 hours.
Churn-risk score computed in the CDP: custom attribute that routes customers to a win-back journey matched to their risk level.
Customers reachable by SMS but no longer by email, per the Batch import: segment pushed back to Batch to switch the follow-up to the right channel.
Every time, the business logic lives in Treasure AI. Batch handles orchestration, channel choice and delivery.
Treasure AI x Batch: FAQ
Do I need developers to set it up?
Not for the setup itself. It happens in the Treasure AI console, using your Batch project's REST API Key and Project Key. Someone does need to write the SQL query that exposes the right columns. For data teams already working in Treasure AI, that's business as usual.
Which identifier should I use?
Batch's Custom User ID: the customer ID shared across your tools. For logged-out users, the app installation ID works too.
What happens if a value is empty in Treasure AI?
By default, the existing attribute in Batch stays as is. Flip one setting and empty values erase the attribute in Batch instead, which is handy for cleaning out stale data.
How do I get started?
Reach out to the Batch team. We'll help you pick the data to sync and get everything configured.
👉 Contact the Batch team to set up the connector.
Anna Guigner
Content Marketing Manager @ Batch