TikTok Conversions
Use warehouse web conversion events for TikTok measurement and attribution.
Connect this destination to write warehouse web conversion events onto a TikTok pixel, for use in measurement and attribution. You do not need an audience.
This destination writes to your TikTok Ads Manager account and is a good fit when you want to:
- Get measurement and attribution in TikTok Ads Manager
- Use a warehouse table that has web events with a name, timestamp, event ID, and page URL
- Measure conversions after you connect TikTok
This maps to GrowthLoop Syncs:
| Use it for | Syncs |
|---|---|
| Sending web conversion events for measurement and attribution | ✓ |
Do not use this workflow to add contacts to a targeting audience. To activate customers for targeting, use TikTok.
Prerequisites
Make sure you have:
- A TikTok Ads Manager account. You can create one here.
- TikTok (batch or streaming) connected as a destination.
- A Pixel Code. In TikTok Ads Manager, go to Tools → Events → Web Events. If you do not have a pixel, follow TikTok's pixel setup.
Set up TikTok Conversions as a destination
- In GrowthLoop, click the Destinations tab on the left sidebar.
- Open your connected TikTok destination (batch or streaming).
- Enter the Pixel Code under credentials and click Save.
You can also add the pixel when you first connect the destination. See TikTok.
Create a sync in GrowthLoop
Create a sync from a warehouse table to write web events onto your TikTok pixel. See Syncs for information on how to complete those steps.
Select an Object Type:
| Object | Use it for | Sync modes |
|---|---|---|
| Web Event | Site actions such as purchases, form submissions, or add-to-cart | Insert |
When you configure the sync:
- Update Rule: Choose Insert. This destination adds new conversion events and does not update or remove previously uploaded events.
- Dataset/Table: Select the table that holds your web events. Use a unique event key so you do not re-send the same conversion.
- Connection: Select your TikTok destination (batch or streaming).
- Object Type: Select Web Event.
- Match Field: Map a stable identity such as email.
Each row needs an event name, event time, event ID, and page URL. Because this destination is insert-only, re-sending the same event can create duplicate conversions.
Required event fields
| Destination field | Description |
|---|---|
| Event Name | The conversion event name. TikTok accepts standard events and custom events. See TikTok standard events |
| Event Time | When the event occurred, as a Unix timestamp |
| Event ID | A unique string that identifies this event instance |
| Page URL | Where the event occurred. TikTok recommends the full URL, including query parameters |
Optional event fields
Map additional fields when you have them. A single row can include more than one identity.
| Destination field | Description |
|---|---|
| Email Address | Email used to match the conversion |
| Phone Number | Phone number used to match the conversion |
| External ID | Your identifier for the customer |
| TikTok Click ID | ttclid from the landing page |
| Cookie ID | TikTok cookie ID (ttp) |
| Public IP | Client IP address |
| User Agent | Browser user agent |
| Value | Order or item value |
| Currency | ISO 4217 currency code |
| Order ID | Order or transaction identifier |
| Content ID / Content Name / Content Category | Product or page metadata |
| Quantity | Number of items |
| Limited Data Use? | Limited data use flag |
See TikTok web event parameters for the full list.
After you map fields, click Update Route, then enable the sync with the toggle at the top of the page.
Sync behavior
This is what GrowthLoop writes when you sync web events to TikTok.
| Behavior | What happens |
|---|---|
| When it runs | GrowthLoop sends the sync as a batch on the next successful run. |
| Insert only | GrowthLoop adds new web events. Syncs do not update or remove previously uploaded events. |
| Duplicate-event risk | Re-sending the same event can create duplicate conversions in TikTok. Use unique event IDs in your source table. |
| Pixel | GrowthLoop sends events to the Pixel Code saved on the destination. |
| Object type | Web Event is the supported object. Offline, app, and CRM events are not available in this destination. |
| Deletes | GrowthLoop does not delete previously uploaded conversion events. |
| Missing identifier | Rows without the required identifier fail. |
Confirm the export was successful
When the run finishes, confirm you can use the data in TikTok.
- Web Event sync: In TikTok Ads Manager, go to Tools → Events and open Web Events.

This workflow does not create a targeting audience.
In GrowthLoop, confirm the sync appears in the Syncs table. See Syncs for more information.
Congrats on successfully exporting to TikTok Conversions!
Troubleshooting
These are the issues we see most often. You can always email us at [email protected] for help.
| Problem | Cause | Resolution |
|---|---|---|
| The sync fails to send events | No Pixel Code is saved on the destination | Save a Pixel Code on the TikTok destination before you enable the sync. |
| Rows fail | A required event field is missing | Include Event Name, Event Time, Event ID, and Page URL on every row. |
| Event Time is rejected | The timestamp is not Unix | Use a Unix timestamp for Event Time. |
| Duplicate conversions appear | The same event was sent more than once | Use a unique Event ID. This destination is insert-only. |
Updated 17 days ago
