Activation & reverse ETL
Give your teams customer data they can act on.
Sync warehouse audiences, lead scores, and customer insights to your business applications. Keep sales and marketing working from the customer data your team maintains in the warehouse.
Make your models useful beyond reporting
Send customer audiences and scores to the tools your sales and marketing teams use.
Choose which records and fields to update
Choose the destination object, field mappings, and merge key before running a sync.
See what reached the destination
Review loaded and failed row counts for each activation run and object.
Follow the delivery
Know your audience reached its destination.
Check loaded and failed row counts before your team uses a new audience. Open the object and stage results to investigate delivery failures.
- Sync a modeled audience from Snowflake to Salesforce Marketing Cloud
- Include the customer fields and offer context your team needs
- Review loaded and failed row counts for each destination object
Customer audiences
Give marketing an audience it can use.
Send eligible customers, offer details, and personalization fields to your marketing application.
- Keep audience rules in warehouse models your data team can review.
- Deliver eligible customers and offer context to marketing.
- Check the sync results before using the audience in a campaign.
Demo data is synthetic. Campaigns and email sends are managed in your marketing application.
Questions before you start
What can I send to my business applications?
Sync customer audiences, lead scores, product usage, or other prepared data to supported destination objects. Choose the source objects and fields to deliver; the available destinations and write options depend on the connectors.
Can I activate data from files or spreadsheets?
Yes. Alongside warehouse tables and views, activation supports file and worksheet objects exposed by compatible source connectors. Select the source data and map it to a supported business application.
Do I have to map every field manually?
Auto Map suggests matches using field names and data types. Review the mappings, adjust them where needed, and check required destination fields before running the sync.
How do I update the correct destination records?
In Merge mode, map a source field to a supported destination record ID, external ID, or primary key. That key identifies the records to match. Available keys and write behavior depend on the destination connector.
Can an activation sync only new or changed data?
Yes, when the source supports incremental sync and has a suitable cursor or built-in change tracking. Other objects use full syncs on their configured schedule.
Can activation run after my dbt models finish?
Yes. Add the activation pipeline and transformation project to an orchestration, then set the activation to wait for its data preparation steps. Check the completed activation’s loaded and failed row counts to verify delivery.
Connect your models to your business tools.
Try Supaflow or walk through your use case with us.
See plans and pricing