RudderStack Docs – Syncs

Audiences: Sync Audiences to Facebook Custom Audience

Mon, 01 Jan 0001 00:00:00 +0000

This guide takes you through the steps to sync Audiences created in RudderStack to your Facebook Custom Audience destination.

You can sync your audiences to multiple destinations.

Setup

Set up an audience in RudderStack using the Audience Builder.
Go to the Syncs tab of the audience page and click Add sync. Then, select Facebook Custom Audience.
Click New destination — you can also select an already-configured destination here.
Specify a unique name to identify this destination in RudderStack.
In the Event delivery account section, click Select to choose from an existing Facebook Ads account from the list. You can also click Add account and authenticate using a Facebook API access token:

Setting	Description
Account Name	Specify a unique Custom Audience account name
Access Token	Enter the access token of your business application set up for accessing the Facebook Marketing API
App Secret	This field is optional. Enter the app secret from the Basic app settings page of your Facebook Developer account

The Ad Account ID field is automatically pre-populated based on the selected Facebook Ads account — select the relevant ID from the dropdown. Then, click Next.

Configure sync

This section lists the settings to correctly configure your audience syncs to the Facebook Custom Audience destination.

RudderStack supports syncing to the following two audience types:

Custom Audiences

Value-based lookalike audiences — see Create new value-based lookalike audiences section for more information.

Select audience

In this section, you can create a new audience or use an existing one.

Create new audience: Use this option to create a new custom audience in Facebook. You can specify the name and description of the new Facebook audience.

If you select the Create new audience option, RudderStack creates a new audience in Facebook with the same Ad Account ID configured in the connection settings.

Use existing audience: Use this option if you have an existing custom audience. RudderStack automatically populates this field with the relevant audiences based on your specified connection settings.

Sync mode

RudderStack supports only Mirror mode for this integration.

Map identifiers

In this section, you can map your warehouse columns to specific Custom Audience fields that represent your audience’s identity.

Advanced settings

Setting	Description
Automatically hash PII data	When set to Yes, RudderStack hash-encodes user data irrespective of whether the data is already hashed or not. Note: Facebook expects the user data to be hash encoded using `SHA256`. See Data hashing section for more information.
Normalize data formatting	When set to Yes, Facebook automatically cleans and standardizes the audience data, like emails and phone numbers. See Data normalization section for more information.
Specify where your data originates from	Select the relevant field from the dropdown that describes the origin of your data — this helps Facebook classify the user list and apply appropriate matching and privacy rules.
Specify identifier type	Choose the relevant identifier type from the dropdown that allows Facebook Ads to match users to their profiles.

Sync settings

RudderStack provides two options to schedule your audience syncs:

Run syncs automatically based on a specified frequency (every 5 minutes, 10 minutes, 15 minutes, 30 minutes, 1 hour, 3 hours, 6 hours, 12 hours, or 24 hours) and a specific time (in UTC).
Run syncs manually — you can trigger a sync manually by clicking the Sync Now button in the sync details page. Note that in this setting, you will need to click Run sync every time you want to sync your audience.

Sync observability settings

Setting

Description

Retain sync logs

This setting is toggled on by default and instructs RudderStack to store the sync logs in your warehouse. You can also configure the below settings:

Setting	Description
Sync log retention	Specify the retention period of the sync logs in your warehouse. If you set it to 1, then RudderStack deletes any sync log older than a day (in UTC time).
Snapshot table retention	Specify the number of snapshot tables to retain.

Retry failed records

This setting is toggled on by default and causes RudderStack to continually retry sending the failed records.

Storing sync logs and snapshot tables may incur additional warehouse costs.

Enable sync

Once the setup is complete, make sure to click Enable sync to enable and activate the sync.

Manage value-based lookalike audiences

This section describes the steps to map your warehouse data to a new or existing value-based lookalike audience.

New audience

To create a new value-based lookalike audience, map a relevant warehouse column to the Lookalike Value field in the Identifier mappings:

In the Select audience section, select Create new audience and specify the audience name and description.
In the Choose identifier mappings window, map a relevant warehouse column to the Lookalike Value field.

Note that:

RudderStack will not create a value-based lookalike audience if you do not include the Lookalike Value in your identifier mappings — it will create a custom audience instead.

You can update the mapping for the Lookalike Value field after the audience is created.

Set up the other identifier mappings as per your requirement.
Continue with the rest of the setup.

Existing value-based lookalike audience

In the Select audience section, select Use existing audience and select the value-based lookalike audience from the dropdown.
In the Choose identifier mappings window, map a relevant warehouse column to the Lookalike Value field.

You can update the mapping for the Lookalike Value field after the audience is created.

Set up the other identifier mappings as per your requirement.
Continue with the rest of the setup.

You cannot change the audience type from a value-based lookalike audience to a regular custom audience (and vice versa) after the audience is created.

Schema fields mapping

The following table details the schema fields mappings specified in the RudderStack dashboard:

Dashboard field name	Marketing API schema field (RudderStack-supported field name)
`EMAIL`	`EMAIL`
`PHONE`	`PHONE`
`GENDER`	`GEN`
`MADID`	`MADID`
`EXTERN_ID`	`EXTERN_ID`
`DOB YEAR (YYYY)`	`DOBY`
`DOB MONTH (MM)`	`DOBM`
`DOB DATE (DD)`	`DOBD`
`LAST NAME`	`LN`
`FIRST NAME`	`FN`
`FIRST NAME INITIAL`	`FI`
`CITY`	`CT`
`US STATES`	`ST`
`ZIP`	`ZIP`
`COUNTRY`	`COUNTRY`

Note that the MADID and EXTERN_ID fields are not hashed.

RudderStack modifies the schema names visible in the dashboard to ensure better readability. However, during the event call, the field names must be exactly the same as the schema names specified by Facebook Marketing API, as mentioned in the table above.

Data normalization

By default, RudderStack formats the data as prescribed by Facebook before sending it to the destination, as shown in the below table:

Schema field name	Example input	Formatted output (before hashing)
`EMAIL`	`ABC@gmail.com`	`abc@gmail.com`
`PHONE`	`0@96346895`	`96346895`
`GEN`	`FEMALE`	`f`
`DOBD`	`2`	`02`
`DOBM`	`1`	`01`
`LN & FN`	`Abc,@`	`abc@`
`FI`	`Mr.`	`mr.`
`CT`	`HN#`	`hn`
`ST`	`? AL ?`	`al`
`ZIP`	`11502 @bc`	`11502@bc`
`COUNTRY`	`IN`	`in`

If you enable the Normalize data formatting setting, RudderStack formats the user data as prescribed by the Facebook Marketing API.

After normalization, RudderStack validates each field before sending it to Facebook.

If a field is determined to be invalid, RudderStack does not send it to Facebook.
If all fields in a row are invalid, then the entire row is rejected and marked as failed

RudderStack first normalizes the data and then validates it, skipping any invalid rows. Then, it hashes the data before sending it to Facebook.

Data hashing

The Automatically hash PII data setting lets you hash your user data before sending it to Facebook. This setting is enabled by default.

Configure the setting to Yes if your incoming data is not pre-hashed
Configure this setting to No if your data is already hashed

Incorrect configuration of the Automatically hash PII data setting will result in failures.

If the Automatically hash PII data setting is configured to Yes and your data is pre-hashed, the event will fail.

If the Automatically hash PII data setting is configured to No and your data is not pre-hashed, the event will fail.

RudderStack rejects such events with a clear error message, for example:

Hashing is disabled but the value for field EMAIL appears to be unhashed. Either enable hashing or send pre-hashed data.

You will also see errors in the Events tab for cases that were previously marked as successful, but were effectively resulting in no matches, helping you quickly identify and fix any data quality or configuration issues.

FAQ

Where can I find the Ad Account ID?

Go to your Facebook Ads Manager account where you can find the Ad Account ID in the account’s drop-down menu:

You can click on See More Ad Accounts if the required Ad account is not visible.

Where can I find the user Access Token for the application?

To generate the user access token for your application, you must first add it as a system user asset with manage permissions.

Follow these steps to generate a user access token required to use the Facebook Marketing API:

Under the system user, click the Generate New Token button and select the app from the dropdown.

Choose the Token expiration time.

Under Available permissions, select ads_read and ads_management.

Click the Generate Token button and copy the token credentials.

Why am I seeing the error “Failed to update the custom audience. Facebook responded with error code: 2650?

This error is not explicitly documented by Facebook but is a known API-level limitation. Error 2650 typically occurs when attempting to add users to a custom audience that was created using a different data source.

For example:

Audience originally created via manual file upload
Audience created through another platform or integration

Facebook does not allow mixing data source types within the same custom audience.

Audiences: Sync Audiences to Google Ads Remarketing Lists (Customer Match)

Mon, 01 Jan 0001 00:00:00 +0000

This guide takes you through the steps to sync Audiences created in RudderStack to your Google Ads Remarketing Lists destination.

You can sync your audiences to multiple destinations.

Prerequisites: Google Ads permissions

This integration relies on the authorizing Google Ads user’s underlying permissions.

Note that the API calls to Google Ads will fail if you authorize this integration without the Standard or Admin permissions.

Setup

Set up an audience in RudderStack using the Audience Builder.
Go to the Syncs tab of the audience page and click Add sync. Then, select Google Ads Remarketing Lists.
Click New destination — you can also select an already-configured destination here.
Specify a unique name to identify this destination in RudderStack.
In the Event delivery account section, click Select to choose from an existing Google Ads account from the list. You can also click Add account and authenticate via OAuth, by specifying the following settings:

Setting	Description
Account Name	Specify a unique account name
oAuth settings	Click Connect account, sign in with Google, and give RudderStack the required permissions to access your Google Ads account.

RudderStack automatically pre-populates the Custom ID associated with your Google Ads account — select the relevant ID from the dropdown.
Turn on the Subaccount setting if you are using a Google Ads subaccount.

Note: See this guide for more information on subaccounts.
If Subaccount is toggled on, enter the Login Customer ID of the parent (manager) account associated with the subaccount.
Click Next to configure the mapping settings.

Mapping settings

This section lists the settings to correctly map data from your audience to the Google Ads Remarketing Lists destination.

Select user list

In this section, you can create a new user list or use an existing one.

Create new list: Use this option to create a new list in Google Ads. You can specify the name and description of the new list.
Use existing list: Use this option if you have an existing list in Google Ads. RudderStack automatically populates this field with the relevant lists based on your specified connection settings.

Sync mode

RudderStack supports only Mirror mode for this integration.

Select list type

If you select the Create new list option, you need to select the type of list where you want to sync the data. RudderStack provides three options:

List type	Description
CONTACT_INFO	You can send email, phone number, and address information in this list
CRM_ID	You can send internal customer IDs in this list
MOBILE_ADVERTISING_ID	You can send mobile advertising IDs (IDFA/GAID) in this list Note: If selected, specify the App ID of the mobile app the data was collected from. For iOS, it is the 9-digit number at the end of the App Store URL, for example, `123456789`. For Android, it’s the package name, for example, `com.sampleapp.samplename`.

Map identifiers

In this section, you can map your warehouse columns to specific Google Ads fields that represent your audience’s identity.

The fields available for mapping depend on the list type you select.

Advanced settings

Setting	Description
Automatically hash PII data	When set to Yes, RudderStack hash-encodes sensitive user data like email, phone, first name, and last name in the SHA-256 format. See Data hashing section for more information.
Specify user consent	Specify the consent type for the uploaded users for using their data in Google Ads. RudderStack provides four options for this setting: Unspecified Unknown Granted Denied Note that if you do not set this field, RudderStack sets it to Unspecified, by default.
Specify ad personalization consent	Specify consent for uploaded users for personalizing ads. RudderStack provides four options for this setting: Unspecified Unknown Granted Denied Note that if you do not set this field, RudderStack sets it to Unspecified by default.

Sync settings

RudderStack provides two options to schedule your audience syncs:

Run syncs automatically based on a specified frequency (every 5 minutes, 10 minutes, 15 minutes, 30 minutes, 1 hour, 3 hours, 6 hours, 12 hours, or 24 hours) and a specific time (in UTC).
Run syncs manually — you can trigger a sync manually by clicking the Sync Now button in the sync details page. Note that in this setting, you will need to click Run sync every time you want to sync your audience.

Sync observability settings

Setting

Description

Retain sync logs

This setting is toggled on by default and instructs RudderStack to store the sync logs in your warehouse. You can also configure the below settings:

Setting	Description
Sync log retention	Specify the retention period of the sync logs in your warehouse. If you set it to 1, then RudderStack deletes any sync log older than a day (in UTC time).
Snapshot table retention	Specify the number of snapshot tables to retain.

Retry failed records

This setting is toggled on by default and causes RudderStack to continually retry sending the failed records.

Storing sync logs and snapshot tables may incur additional warehouse costs.

Enable sync

Once the setup is complete, make sure to click Enable sync to enable and activate the sync.

Data normalization

By default, RudderStack automatically cleans and standardizes the data as prescribed by Google Ads.

After normalization, RudderStack validates each field before sending it to Google Ads:

If a field is determined to be invalid, RudderStack does not send it to Google Ads.
If all fields in a row are invalid, then the entire row is rejected and marked as failed

RudderStack first normalizes the data and then validates it, skipping any invalid rows. Then, it hashes the data before sending it to Google Ads.

Data hashing

The Automatically hash PII data setting lets you hash your user data before sending it to Google Ads. This setting is enabled by default.

Configure the setting to Yes if your incoming data is not pre-hashed
Configure this setting to No if your data is already hashed

Incorrect configuration of the Automatically hash PII data setting will result in failures.

If the Automatically hash PII data setting is configured to Yes and your data is pre-hashed, the event will fail.

If the Automatically hash PII data setting is configured to No and your data is not pre-hashed, the event will fail.

RudderStack rejects such events with a clear error message, for example:

Hashing is disabled but the value for field EMAIL appears to be unhashed. Either enable hashing or send pre-hashed data.

FAQ

What are the account permissions required for the Google Ads Remarketing Lists integration?

Make sure the customer account used for OAuth verification adheres to Google’s Customer Match policy and has Standard or higher (Administrative) access level permissions.

For more information on the access level permissions, refer to this Google Ads support page.

Follow these steps to set the access level:

Sign into to your Google Ads account and go to TOOLS AND SETTINGS > Access and security:

Enter the email address of the account. From the list of permissions, select Standard or Administrative. Then, click SEND INVITATION:

The account will have the required access-level permissions once they accept the invitation.

Why am I getting a 400 Bad Request error message while setting up the Google Ads Remarketing Lists destination?

If you get a 400 Bad Request error while configuring the destination, make sure your customer account is allowlisted and configured to have Standard or Administrative access levels in Google Ads.

See the above FAQ for steps on setting the access level permissions for the account.

Audiences: Sync Audiences to LinkedIn Audience

Mon, 01 Jan 0001 00:00:00 +0000

This guide takes you through the steps to sync Audiences created in RudderStack to your LinkedIn Audience destination.

You can sync your audiences to multiple destinations.

Setup

Set up an audience in RudderStack using the Audience Builder.
Go to the Syncs tab of the audience page and click Add sync. Then, select LinkedIn Audience.
Click New destination — you can also select an already-configured destination here.
Specify a unique name to identify this destination in RudderStack.
In the Event delivery account section, click Select to choose from an existing LinkedIn account from the list. You can also click Add account and authenticate via OAuth, by specifying the following settings:

Setting	Description
Account Name	Specify a unique account name
oAuth settings	Click Connect account, sign in with LinkedIn, and give RudderStack the required permissions to access your LinkedIn Ads account.

Click Next to configure the mapping settings.

Configure sync

This section lists the settings to correctly configure your audience syncs to the LinkedIn Audience destination.

Select LinkedIn account

Select your LinkedIn Ads account from the dropdown — all the data will be synced with this account.

Audience type

Select the audience type from the dropdown. RudderStack supports two types - User and Company.

Select audience

In this section, you can create a new audience or use an existing one.

Create new audience: Use this option to create a new custom audience in LinkedIn. You can specify the name and description of the new LinkedIn audience.
Use existing audience: Use this option if you have an existing audience in LinkedIn. RudderStack automatically populates this field with the relevant audiences based on your specified connection settings and audience type configured above.

Sync mode

RudderStack supports only Mirror mode for this integration.

Mapping settings

Select a warehouse columns that act as identifiers for your records and map them to the relevant LinkedIn identifiers based on your audience type — see Identifier mappings section below for more information.
Map the other warehouse columns to specific LinkedIn fields that represent your audience’s identity.

Identifier mappings

RudderStack supports specifying multiple identifiers for both the User and Company audience types.

For the User audience type, RudderStack supports the below LinkedIn identifiers to which you can map your warehouse columns:

Identifier	Description
Email (SHA256)	User’s email in a hex-encoded string format with a maximum length of 64 characters.
Email (SHA512)	User’s email in a hex-encoded string format with a maximum length of 128 characters.
Google Advertising ID	Plain text string (in lower case) with a maximum length of 32 characters.

For the Company audience type, RudderStack supports the below identifiers:

Identifier	Description
Company Name	The company name.
Company Email Domain	Company’s email domain string in a URL format, for example, `linkedin.com`.
Company Website Domain	Company’s website domain string in a URL format, for example, `www.linkedin.com`.
Company Page URL	The LinkedIn company page URL with a maximum length of 100 characters, for example, `linkedin.com/company/acmecorp`.
Organization URN	The LinkedIn company page URN, for example, `urn:li:organizationUrn:123`.

Other mappings

Apart from the identifier mappings, the User audience type also supports the below field mappings:

Field	Description
First Name	User’s first name with a maximum length of 35 characters, for example, `Alex`.
Last Name	User’s last name with a maximum length of 35 characters, for example, `Keener`.
Title	User’s title in the company with a maximum length of 50 characters, for example, `Engineer`.
Company	User’s company name with a maximum length of 50 characters, for example, `Acme Corp`.
Country	ISO standard two letter country code, for example, `US`.

For the Company audience type, RudderStack supports the below field mappings:

Field	Description
Stock Symbol	Stock symbol of the company with a maximum length of 5 letters, for example, `ACME`.
Industries	Three industry names for the company with a maximum length of 50 characters, for example, `Technology`, `Software`.
City	City of the company with a maximum length of 50 characters, for example, `New York`.
State	State or province of the company with a maximum length of 50 characters, for example, `Louisiana`.
Country	ISO standard two letter country code, for example, `US`.
Postal Code	Postal code of the company with a maximum length of 20 characters, for example, `560001`.

Advanced settings

Setting	Description
Automatically hash PII data	When set to Yes, RudderStack hash-encodes user data to LinkedIn. Note that: This setting is applicable only for the User audience type. Do not use this setting if you are syncing already-hashed data from your warehouse to LinkedIn. Otherwise, it can lead to failures. See Data hashing section for more information.

Sync settings

RudderStack provides two options to schedule your audience syncs:

Run syncs automatically based on a specified frequency (every 5 minutes, 10 minutes, 15 minutes, 30 minutes, 1 hour, 3 hours, 6 hours, 12 hours, or 24 hours) and a specific time (in UTC).
Run syncs manually — you can trigger a sync manually by clicking the Sync Now button in the sync details page. Note that in this setting, you will need to click Run sync every time you want to sync your audience.

Sync observability settings

Setting

Description

Retain sync logs

This setting is toggled on by default and instructs RudderStack to store the sync logs in your warehouse. You can also configure the below settings:

Setting	Description
Sync log retention	Specify the retention period of the sync logs in your warehouse. If you set it to 1, then RudderStack deletes any sync log older than a day (in UTC time).
Snapshot table retention	Specify the number of snapshot tables to retain.

Retry failed records

This setting is toggled on by default and causes RudderStack to continually retry sending the failed records.

Storing sync logs and snapshot tables may incur additional warehouse costs.

Enable sync

Once the setup is complete, make sure to click Enable sync to enable and activate the sync.

Data hashing

The Automatically hash PII data setting lets you hash your user data before sending it to LinkedIn. This setting is enabled by default.

Configure the setting to Yes if your incoming data is not pre-hashed
Configure this setting to No if your data is already hashed

Incorrect configuration of the Enable Hashing setting will result in failures.

If the Enable Hashing setting is configured to Yes and your data is pre-hashed, the event will fail.

If the Enable Hashing setting is configured to No and your data is not pre-hashed, the event will fail.

RudderStack rejects such events with a clear error message, for example:

Automatically hash PII data is disabled but the value for field EMAIL appears to be unhashed. Either enable hashing or send pre-hashed data.

Audiences: Sync Audiences to TikTok Audiences

Mon, 01 Jan 0001 00:00:00 +0000

This guide takes you through the steps to sync Audiences created in RudderStack to your TikTok Audiences destination.

You can sync your audiences to multiple destinations.

Setup

Set up an audience in RudderStack using the Audience Builder.
Go to the Syncs tab of the audience page and click Add sync. Then, select TikTok Audiences.
Click New destination — you can also select an already-configured destination here.
Specify a unique name to identify this destination in RudderStack.
In the Event delivery account section, click Select to choose from an existing TikTok account from the list. You can also click Add account and authenticate via OAuth, by specifying the following settings:

Setting	Description
Account Name	Specify a unique account name
oAuth settings	Click Connect account, sign in with TikTok, and give RudderStack the required permissions to access your TikTok Ads account.

The Advertiser ID field is automatically pre-populated based on the selected TikTok account — select the relevant ID from the dropdown.
Click Next to configure the mapping settings.

Configure sync

This section lists the settings to correctly configure your audience syncs to the TikTok Audiences destination.

Select audience

In this section, you can create a new audience or use an existing one.

Create new audience: Use this option to create a new custom audience in TikTok. You can specify the name and description of the new TikTok audience.
Use existing audience: Use this option if you have an existing audience in TikTok. RudderStack automatically populates this field with the relevant audiences based on your specified connection settings.

Sync mode

RudderStack supports only Mirror mode for this integration.

Map identifiers

In this section, you can map your warehouse columns to specific TikTok fields that represent your audience’s identity.

Advanced settings

Setting	Description
Automatically hash PII data	When set to Yes, RudderStack automatically hash-encodes user data in the SHA-256 format before sending it to TikTok. Do not use this setting if you are sending already-hashed data from your warehouse to TikTok. Otherwise, it can lead to failures. See Data hashing section for more information.

Sync settings

RudderStack provides two options to schedule your audience syncs:

Run syncs automatically based on a specified frequency (every 5 minutes, 10 minutes, 15 minutes, 30 minutes, 1 hour, 3 hours, 6 hours, 12 hours, or 24 hours) and a specific time (in UTC).
Run syncs manually — you can trigger a sync manually by clicking the Sync Now button in the sync details page. Note that in this setting, you will need to click Run sync every time you want to sync your audience.

Sync observability settings

Setting

Description

Retain sync logs

This setting is toggled on by default and instructs RudderStack to store the sync logs in your warehouse. You can also configure the below settings:

Setting	Description
Sync log retention	Specify the retention period of the sync logs in your warehouse. If you set it to 1, then RudderStack deletes any sync log older than a day (in UTC time).
Snapshot table retention	Specify the number of snapshot tables to retain.

Retry failed records

This setting is toggled on by default and causes RudderStack to continually retry sending the failed records.

Storing sync logs and snapshot tables may incur additional warehouse costs.

Enable sync

Once the setup is complete, make sure to click Enable sync to enable and activate the sync.

Supported mappings

You can map your warehouse columns to the following TikTok fields:

Field	Description
IDFA_MD5	MD5 hash of an iOS IDFA
AAID_MD5	MD5 hash of an Android AAID/GAID
IDFA_SHA256	SHA256 hash of an iOS IDFA
AAID_SHA256	SHA256 hash of an Android AAID/GAID
EMAIL_SHA256	SHA256 hash of email ID — see Important Notes for Streaming API- Email Specific Normalization section for more information
PHONE_SHA256	SHA256 hash of a phone number in E.164 format, for example, `+1231234567`

After normalization, RudderStack validates each field before sending it to TikTok.

If a field is determined to be invalid, RudderStack does not send it to TikTok.
If all fields in a row are invalid, the entire row is skipped and the event is marked as failed.

Data hashing

The Automatically hash PII data setting lets you hash your user data before sending it to TikTok. This setting is enabled by default.

Configure the setting to Yes if your incoming data is not pre-hashed
Configure this setting to No if your data is already hashed

TikTok expects the incoming data to be hashed. Hence, incorrect configuration of the Automatically hash PII data setting will result in failures:

If the Automatically hash PII data setting is configured to Yes and your data is already hashed, the event will fail.

If the Automatically hash PII data setting is configured to No and your data is not pre-hashed, the event will fail.

RudderStack rejects such events with a clear error message, for example:

Automatically hash PII data is disabled but the value for field EMAIL appears to be unhashed. Either enable hashing or send pre-hashed data.

FAQ

Why can’t I add a Reverse ETL source from the destination page?

The Reverse ETL feature supports only source-driven pipeline configuration. It means that you must configure a Reverse ETL source in RudderStack and then connect it to a new or existing destination. Note that this destination should not be connected to any other source.

See Reverse ETL FAQ for more information.

How do I view the synced segments in TikTok?

To view the synced audience, go to your TikTok Ads Manager and go to Tools > Audience manager.

To see the sync status, check the Availability column.