Overview

Create a scheduled sync that writes warehouse data to a destination.

Syncs are scheduled writes from a warehouse table to a destination. Use them when the destination needs warehouse data on a schedule, not when you only need list membership.

How a sync writes depends on the destination:

  • Personalization and CRM syncs update profiles or records that already exist, or create them when the destination allows it
  • Conversion syncs insert event rows for measurement
  • Campaign syncs change campaign settings, such as location targets

Audience exports and journeys manage who is in a list or who enters a step. Destination pages document the objects, match fields, and sync modes for that platform.

When to use a sync

Use a sync when you need warehouse data written into the destination itself:

  • Personalize email, SMS, or push with profile attributes such as first name or loyalty tier
  • Create or update CRM records in tools such as HubSpot or Salesforce
  • Send conversion events to ad platforms
  • Change campaign settings, such as Google Ads location targets

Export an audience when you need membership in a list, segment, or ad audience. Do not use a sync to rebuild targeting in a downstream tool.

Choose a destination

Pick the sync type, then open that destination for objects, match fields, and sync modes.

Personalization syncs

Write profile or CRM fields so you can personalize messages. These syncs do not add or remove people from a list.

DestinationObjectsUse it for
BrazeEvent, Purchase, Profile Attribute, Subscription Group StatusEvents, purchases, profile fields, and subscription state
DotdigitalContactsContact data fields
HubSpotContacts, Companies, Deals, Tickets, Line ItemsCRM records
IterableUser, EventUser profiles and events
KlaviyoIdentityExisting Klaviyo profiles
MarketoLead, Custom objectLeads and custom objects
Microsoft DynamicsAccount, Contact, Lead, Opportunity, custom objectsDynamics records
Recurly EngageUserUser traits
Salesforce CRMAccount, Contact, Lead, Opportunity, custom objectsSalesforce records
Salesforce Marketing CloudData ExtensionRows in an existing Data Extension
Salesforce PardotProspectProspect profiles
SAP EmarsysContactsContact attributes
ShopifyUsersCustomer profiles
TealiumVisitorVisitor events in AudienceStream
VoyadoContactContact profiles

Conversion syncs

Send warehouse conversion events to an ad platform for measurement.

DestinationObjectsUse it for
Facebook ConversionsConversion, AMAPIConversion events and Advanced Measurement API events
Google Ads ConversionsConversionsClick conversions and offline click conversions
Google Campaign Manager 360 ConversionsConversion, Enhanced ConversionOffline conversions and enhanced conversions
Google Firebase ConversionsApp ConversionMobile app conversion events in GA4
Microsoft Ads (Bing) ConversionsConversionOffline conversion events
Pinterest ConversionsConversion EventWeb, in-app, or offline conversion events
Reddit Ads ConversionsWeb ConversionsConversion events for Reddit measurement
Rokt ConversionsEventConversion events for Rokt measurement
Snapchat ConversionsConversionsWeb, app, or offline conversion events
The Trade Desk ConversionsOffline ConversionConversion events for measurement and attribution
TikTok ConversionsWeb EventSite actions such as purchases or add-to-cart

Campaign syncs

Write campaign settings in the destination. This is not audience membership and not a conversion event.

DestinationObjectsUse it for
Google AdsCampaignAdd or remove campaign location targets

Don't over-sync

Keep syncs small. Copying extra columns into SaaS tools creates data sprawl and can raise destination costs.

  • Field count: Sync only the fields the destination needs for activation or personalization.
  • Targeting vs personalization: Keep targeting logic in GrowthLoop and export audience membership. Do not sync a wide set of filter columns so another tool can rebuild the same audience.

Prerequisites

Make sure you have:

  • A connected destination
  • A warehouse dataset that holds the records or events you want to write
  • The match field the destination uses to look up a record, for example email or an event ID. See the destination page for required fields

Create a sync

  1. Click the Syncs tab on the left sidebar.
  2. Click New Sync in the upper right corner.
  1. Configure the sync:
FieldDescription
Route NameName this sync in GrowthLoop
Dataset/TableThe warehouse table that holds the records or events
ConnectionThe destination that should receive the rows
Object TypeThe object the destination writes, for example Identity, Contacts, or a conversion event. See the destination page for the objects it supports
Match FieldThe column GrowthLoop uses to look up the record in the destination
Sync FrequencyHow often the sync should run
Update RuleHow GrowthLoop writes rows. Destinations offer some combination of Insert, Update, and Insert or update (sometimes labeled Upsert). Use the modes listed on that destination page
  1. Map source columns to destination fields. Map the required identifier first, then any additional fields the destination accepts.
  2. Click Save Sync. Some destinations later show Update Sync, Save Route, or Update Route.
  3. Enable the sync with the toggle at the top of the page.

Confirm the result

The sync appears in the Syncs table. Open the destination page for that platform to see what GrowthLoop writes, when it runs, and how to confirm the records in the destination.

Congrats on successfully creating a sync!

Troubleshooting

These are the issues we see most often. You can always email us at [email protected] for help.

ProblemCauseResolution
You cannot create or save the syncRequired mappings are missingMap the match field and any other required destination fields
Rows fail in the syncThe match field is blank or the destination rejected the valueFix the warehouse column, then check the destination page for required formats
You expected list membership to changeSyncs write warehouse data to a destination. They do not add or remove people from a listExport an audience to manage membership

What’s Next

Connect a destination, then map its objects and fields

Did this page help you?