Skip to content

Commit fd0ea1c

Browse files
authored
Merge pull request #75 from segmentio/repo-sync
repo sync
2 parents 805df55 + e4bb98f commit fd0ea1c

File tree

3 files changed

+146
-1
lines changed
  • src
    • _data/actions
    • connections
      • destinations/catalog/tiktok-conversions
      • sources/catalog/libraries/website/javascript

3 files changed

+146
-1
lines changed

src/_data/actions/tiktok.yml

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
settings:
2+
- category: Connection Settings
3+
settings:
4+
- name: Access Token (required)
5+
description: TikTok Long Term Access Token. You can generate this from the TikTok Marketing API portal. Please follow TikTok's [Authorization guide](https://ads.tiktok.com/athena/docs/index.html?plat_id=-1&doc_id=100010&id=100681&key=e98b971a296ae45d8e35a22fba032d1c06f5973de9aab73ce07b82f230cf3afd){:target="_blank"} for more info.
6+
default:
7+
- name: Secret Key (required)
8+
description: TikTok App Secret Key. You can find this key in the "Basic Information" tab of your TikTok app.
9+
default:
10+
- name: App Id (required)
11+
description: TikTok App Id. You can find this key in the "Basic Information" tab of your TikTok app.
12+
default:
13+
- name: Pixel Code (required)
14+
description: An ID for your pixel. Required to send events to the TikTok pixel.
15+
default:
16+
actions:
17+
- action: Report Web Event
18+
blurb: Report events directly to TikTok.
19+
fields:
20+
- name: Email
21+
description: Email address of the user who triggered the conversion event.
22+
default: coalesce(properties.email, traits.email)
23+
- name: External ID
24+
description: Uniquely identifies the user who triggered the conversion event.
25+
default: coalesce(userId, anonymousId)
26+
- name: Event Name
27+
description: Conversion event name. Please refer to the "Supported Web Events" section on [this](https://ads.tiktok.com/marketing_api/docs?id=1701890979375106){:target="_blank"} page for accepted event names.
28+
default:
29+
- name: Event ID
30+
description: Any hashed ID that can identify a unique user/session.
31+
default: messageId
32+
- name: Event Timestamp
33+
description: Timestamp that the event took place, in ISO 8601 format.
34+
default:
35+
- name: Segment Event Type
36+
description: The Segment Event type, for example, "page".
37+
default: type
38+
- name: Properties associated with the event
39+
description: Additional properties such as content info, description, and currency.
40+
default:
41+
- name: Phone Number
42+
description: Phone number of the user who triggered the conversion event, in E.164 standard format, e.g. +14150000000.
43+
default: coalesce(properties.phone, traits.phone)
Lines changed: 102 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,102 @@
1+
---
2+
title: TikTok Conversions
3+
hide-boilerplate: true
4+
hide-dossier: true
5+
hidden: true
6+
---
7+
8+
{% include content/plan-grid.md name="actions" %}
9+
10+
The TikTok Conversions Destination enables advertisers to send Segment events to report events directly to TikTok. Data shared can power TikTok solutions like dynamic product ads, custom targeting, campaign optimization and attribution.
11+
12+
Reporting web events allows advertisers to send user data directly to TikTok for downstream targeting and optimization. Advertisers will be able to see their event data in TikTok Events Manager.
13+
14+
> info ""
15+
> This document is about a feature which is in beta. This means that the Destination Actions are in active development, and some functionality may change before it becomes generally available
16+
17+
> success ""
18+
> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) TikTok Conversions Segment destination.
19+
20+
## Benefits
21+
22+
1. **Streamlined stability and security**: Integrate and iterate without client-side limitations, like network connectivity or ad blocker issues.
23+
2. **Configurable privacy controls**: Stay compliant with rapidly evolving requirements with flexible privacy controls that let you adapt what data you share and when you share it.
24+
3. **Maximum event measurement**: Capture more events with improved accuracy across different browsers, apps and devices to get a unified view of your customer's journey from page view to purchase.
25+
26+
## Getting started
27+
28+
Follow the instructions below to enable your TikTok ads account, and add the TikTok Conversions destination to your Segment workspace.
29+
30+
### TikTok Requirements
31+
32+
1. [Create a TikTok For Business account](https://ads.tiktok.com/marketing_api/docs?id=1702715936951297){:target="_blank"}.
33+
2. [Register as a developer](https://ads.tiktok.com/marketing_api/docs?id=1702716323359809{:target="_blank"}).
34+
3. [Create a developer application](https://ads.tiktok.com/marketing_api/docs?id=1702716474845185){:target="_blank"}.
35+
4. Follow instructions for [Authorization](https://ads.tiktok.com/marketing_api/docs?id=1701890912382977){:target="_blank"} and generate a long term access token.
36+
37+
### Configuring TikTok Conversions in Segment
38+
39+
1. From the Segment web app, click **Catalog**, then click **Destinations**.
40+
2. Find the Destinations Actions item in the left navigation, and click it.
41+
3. Click **Configure TikTok Conversions**.
42+
4. Select an existing Source to connect to TikTok Conversions.
43+
5. On the next page enter your TikTok Access Token, Secret Key, App Id, and Pixel Code. Click Verify credentials.
44+
45+
46+
{% include components/actions-fields.html name="tiktok" connection="true" %}
47+
48+
## Pre-built subscriptions
49+
50+
By default a new TikTok Conversions destination comes with the following subscriptions.
51+
52+
| Subscription Name | Trigger | TikTok Conversions Action |
53+
| ----------------- | --------------------------------------------------- | ------------------------- |
54+
| Products Searched | All events where the name is `Products Searched` | Report Web Event |
55+
| Add Payment Info | All events where the name is `Payment Info Entered` | Report Web Event |
56+
| Initiate Checkout | All events where the name is `Checkout Started` | Report Web Event |
57+
| Order Completed | All events where the name is `Order Completed` | Report Web Event |
58+
| View Content | All **Page** events | Report Web Event |
59+
60+
Choose **Quick Setup** during configuration to can select these subscriptions. You can enable, edit, and disable them from the Actions tab of the destination.
61+
62+
The pre-built TikTok Conversions Subscriptions trigger the same action, **Report Web Event**. The default subscriptions map events that follow Segment's Spec to the TikTok spec. You can create new subscriptions and map events that best suit your configuration.
63+
64+
The table below shows the mapping of the Segment semantic ecommerce or custom event names to the TikTok semantic conversion event names in the prebuilt subscriptions.
65+
66+
| Segment Event Name | TikTok Semantic Conversion Event Name |
67+
| -------------------- | ------------------------------------- |
68+
| Checkout Started | InitiateCheckout |
69+
| Products Searched | Search |
70+
| Payment Info Entered | AddPaymentInfo |
71+
| Order Completed | PlaceOrder |
72+
73+
| Segment Event Type | TikTok Semantic Conversion Event Name |
74+
| -------------------------- | ------------------------------------- |
75+
| All **Segment Page Calls** | ViewContent |
76+
77+
<!-- The section below provides reference tables for the actions defined in your destination. Create the unordered list. The Segment Docs team will assist with populating the data file referenced by this include. -->
78+
79+
## Available TikTok Conversion actions
80+
81+
Combine the supported [triggers](/docs/connections/destinations/actions/#components-of-a-destination-action) with the following TikTok-supported actions:
82+
83+
- [Report Web Event](#report-web-event)
84+
85+
{% include components/actions-fields.html name="tiktok" %}
86+
87+
All TikTok Conversions subscriptions trigger the Report Web Event action.
88+
89+
This action sends a request from Segment to the [TikTok Events Web API](https://ads.tiktok.com/marketing_api/docs?id=1701890979375106){:target="_blank"}.
90+
91+
Ensure you've created your TikTok Pixel within Events Manager before sending events. Instructions to create a pixel can be found [here](https://ads.tiktok.com/help/article?aid=10021){:target="_blank"}.
92+
93+
## Notes
94+
95+
- The TikTok Events API supports QPS =< 1k per app(TikTok Marketing API app)per endpoint. If more is required, please contact your TikTok account representative.
96+
- Requests report events to one pixel ID. This restriction is because authorization is done at user/pixel level. See the Authorization section for details.
97+
- Data that is shared to the Events API is processed similar to information shared through other TikTok data integration business tools, like the TikTok pixel and TikTok SDK.
98+
99+
100+
101+
<!-- Add information about steps needed to migrate from a classic version of your destination here. The Segment Docs team will assist you with populating the data file referenced by this include. The table at the bottom maps classic settings to the new destination.-->
102+

src/connections/sources/catalog/libraries/website/javascript/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ strat: ajs
1111
Analytics.js 2.0, the latest version of Segment's JavaScript source, enables you to send your data to any tool without having to learn, test, or use a new API every time.
1212

1313
> note ""
14-
> Analytics.js 2.0 is available to Segment customers subject to the terms of their subscription agreement with Segment. Analytics.js 2.0 is not available as an open-source project.
14+
> Analytics.js 2.0 is available as an [open-source project](https://github.com/segmentio/analytics-next/){:target="_blank"}.
1515
1616

1717
## Benefits of Analytics.js 2.0

0 commit comments

Comments
 (0)