You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/actions-segment-profiles/salesforce-source.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,9 +16,8 @@ Once configured, this integration lets you send Salesforce data directly to Segm
16
16
17
17
Before you begin, make sure that you have the following:
18
18
19
-
- a Segment workspace with [Unify](/docs/unify/) enabled and [Identity Resolution](/docs/unify/identity-resolution/) set up
20
-
- Administrator access to your Salesforce account
21
-
- Salesforce Unify Direct Integration enabled for your workspace. [Contact Segment](https://segment.com/help/contact/){:target="_blank"} if you don't yet have the integration enabled.
19
+
- a Segment workspace with [Unify](/docs/unify/) enabled and [Identity Resolution](/docs/unify/identity-resolution/) set up.
20
+
- Administrator access to your Salesforce account.
22
21
23
22
## Integration steps
24
23
@@ -89,4 +88,4 @@ Keep the following in mind as you work with the Salesforce Unify Direct Integrat
89
88
- Regularly review your mapping to ensure it reflects any changes in your Salesforce schema or Segment Profile needs.
90
89
- Monitor both your Salesforce source and Segment Profiles destination for errors and data discrepancies.
91
90
92
-
The Salesforce Unify Direct Integration supports mapping from a single Salesforce collection per data model. For complex use cases requiring data from multiple collections, you may need to create multiple data models and mappings.
91
+
The Salesforce Unify Direct Integration supports mapping from a single Salesforce collection per data model. For complex use cases requiring data from multiple collections, you may need to create multiple data models and mappings.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/actions-tiktok-audiences/index.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,23 +78,25 @@ The setup is complete and the audience will start syncing to TikTok. The audienc
78
78
5. On the Destination **Settings** tab, name your destination and authenticate with TikTok Audiences using OAuth.
79
79
80
80
6. Once authenticated, toggle “Enable Destination” on and click **Save Changes**.
81
+
82
+
7. Follow the steps in the [Create a TikTok Audience](#create-a-tiktok-audience) section to create an audience. Once complete, make sure to note the `audience_id` obtained during this process, then proceed to Step 8.
81
83
82
-
7. Navigate to the **Mappings** tab, click **New Mapping**, and select **Add Users**.
84
+
8. Navigate to the **Mappings** tab, click **New Mapping**, and select **Add Users**.
83
85
84
-
8. Under Select mappings, select the TikTok "Advertiser ID" of the audience segment you want to add users to. Input the `audience_id` of that audience segment under "Audience ID."
86
+
9. Under Select mappings, select the TikTok "Advertiser ID" of the audience segment you want to add users to. Input the `audience_id` of that audience segment under "Audience ID."
85
87
**A separate mapping must be created for each audience segment you plan to send Engage audiences to.** Once you've created the audience using the name of Segment's audience key, you can get the Audience ID from TikTok's Assets>Audiences page. You'll also find the Advertised ID, noted by `aadvid`, over the TikTok URL.
86
88
87
-
9. Repeat steps 7 and 8 to also set up a **Remove Users** mapping.
89
+
10. Repeat steps 7 and 8 to also set up a **Remove Users** mapping.
88
90
89
-
10. Navigate back to **Engage > Audiences** and click on the audience from Step 1.
91
+
11. Navigate back to **Engage > Audiences** and click on the audience from Step 1.
90
92
91
-
11. Click **Add Destinations** and select the TikTok Audiences destination you just created. In the settings that appear in the side panel, toggle the **Send Track** option on and do **not** change the Audience Entered/Audience Exited event names. Click **Save Settings**.
93
+
12. Click **Add Destinations** and select the TikTok Audiences destination you just created. In the settings that appear in the side panel, toggle the **Send Track** option on and do **not** change the Audience Entered/Audience Exited event names. Click **Save Settings**.
92
94
93
95
The setup is complete and the audience will start syncing to TikTok. The audience will appear in your [TikTok Ads Manager](https://www.tiktok.com/business/en-US/solutions/ads-manager){:target="_blank"} account under **Assets > Audiences**. It can take 24-48 hours for users to appear in TikTok.
94
96
95
97
To sync additional audiences from your Engage space, create a separate mapping in the TikTok Audiences destination. Navigate to **Connections > Destinations**, search and select the TikTok Audiences destination, and follow steps 7-11 above.
[Dotdigital](https://dotdigital.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} is an all-in-one customer experience and data platform (CXDP) that empowers marketing teams to exceed customer expectations with highly personalized cross-channel journeys.
9
+
[Dotdigital](https://dotdigital.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} is an all-in-one customer experience and data platform (CXDP) that empowers marketing teams to exceed customer expectations with highly personalized cross-channel journeys.
10
10
11
11
This destination is maintained by Dotdigital. For any issues with the destination, [contact the Dotdigital Support team](mailto:[email protected]).
12
12
13
13
## Getting started
14
14
15
-
1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Dotdigital".
15
+
1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank"} search for "Dotdigital".
16
16
2. Select Dotdigital and click **Add Destination**.
17
17
3. Select an existing Source to connect to Dotdigital (Actions).
18
18
4. Log in to your [Dotdigital account](https://login.dotdigital.com/){:target="_blank"}. Expand the User menu in the bottom left and go to Settings > Access > API users.
19
19
5. Note your API region (r1, r2 or r3) for step 7.
20
-
6. Create a [new API user](https://developer.dotdigital.com/docs/setting-up-an-api-user){:target="_blank”}.
20
+
6. Create a [new API user](https://developer.dotdigital.com/docs/setting-up-an-api-user){:target="_blank"}.
21
21
7. In Segment, select your Dotdigital account region and paste the **API user** and **API password** in the Dotdigital destination settings.
22
22
23
23
{% include components/actions-fields.html %}
@@ -27,8 +27,15 @@ This destination is maintained by Dotdigital. For any issues with the destinatio
27
27
### Add Contact to List
28
28
Before using the Add Context to List Action, complete the following prerequisites:
29
29
30
-
-**Lists**: [Create a contact list in Dotdigital](https://support.dotdigital.com/en/articles/8198769-create-a-contact-list){:target="_blank”}. After you've created a list in Dotdigital, return to the Segment app and select your list from the dropdown in the Segment event mapping.
31
-
-**Data Fields**: [Create or edit your data fields in Dotdigital](https://support.dotdigital.com/en/articles/8198833-create-delete-and-edit-custom-data-fields){:target="_blank”}, then return to the Segment app, open the event mapping, and map Segment properties to Dotdigital data fields.
30
+
-**Lists**: [Create a contact list in Dotdigital](https://support.dotdigital.com/en/articles/8198769-create-a-contact-list){:target="_blank"}. After you've created a list in Dotdigital, return to the Segment app and select your list from the dropdown in the Segment event mapping.
31
+
-**Data Fields**: [Create or edit your data fields in Dotdigital](https://support.dotdigital.com/en/articles/8198833-create-delete-and-edit-custom-data-fields){:target="_blank"}, then return to the Segment app, open the event mapping, and map Segment properties to Dotdigital data fields.
32
32
33
33
### Enroll Contact to Program
34
-
When you use the Enroll Contact to Program action, Dotdigital creates a contact for the identifier you provide, if the contact doesn't already exist.
34
+
When you use the Enroll Contact to Program action, Dotdigital creates a contact for the identifier you provide, if the contact doesn't already exist.
35
+
36
+
### Send SMS
37
+
Only valid mobile numbers with an international dialing prefix in E.164 format will be accepted. This format is a combination of `+[country code][phone number]`. For example: `+12133734253`.
38
+
39
+
### Send Transactional SMS
40
+
- Only valid mobile numbers with an international dialing prefix in E.164 format will be accepted. This format is a combination of `+[country code][phone number]`. For example: `+12133734253`.
41
+
- You must have SMS pay-as-you-go enabled to use this action. Learn more about how to enable SMS pay-as-you-go in [Dotdigital's documentation](https://support.dotdigital.com/en/articles/8199154-understand-sms-pay-as-you-go-and-spend-limit){:target="_blank"}.
Copy file name to clipboardExpand all lines: src/guides/intro-impl.md
+10-7Lines changed: 10 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ title: Segment for Developers
5
5
This guide explains all you need to know to get started with your Segment implementation, and directs you to more resources depending on your specific needs.
6
6
7
7
> info ""
8
-
> If you haven't already, you should read the [detailed explanation of Segment](/docs/guides/) on the previous page!
8
+
> If you haven't already, you should read the [detailed explanation of Segment](/docs/guides/) on the previous page.
9
9
10
10
{% include components/reference-button.html href="https://university.segment.com/introduction-to-segment/324262?reg=1&referrer=docs" icon="media/academy.svg" title="Segment University: Segment in Action" description="See a quick example of Segment working on an ecommerce website. (Must be logged in to access.)" %}
11
11
@@ -15,7 +15,7 @@ Segment sends messages about activities in your mobile apps, websites or servers
15
15
16
16
## Types of Segment messages
17
17
18
-
Segment's libraries generate and send messages to our tracking API in JSON format, and provide a standard structure for the basic API calls. We also provide recommended JSON structure (also known as a schema, or 'Spec') that helps keep the most important parts of your data consistent, while allowing great flexibility in what other information you collect and where.
18
+
Segment's libraries generate and send messages to our tracking API in JSON format, and provide a standard structure for the basic API calls. Segment also provides recommended JSON structure (also known as a schema, or Spec) that helps keep the most important parts of your data consistent, while allowing great flexibility in what other information you collect and where.
19
19
20
20
There are six calls in the basic tracking API, which answer specific questions:
21
21
@@ -33,19 +33,22 @@ The other three, Track, Page, and Screen, can be considered as increasingly spec
33
33
A Track call is the most basic type of call, and can represent any type of event. Page and Screen are similar and are triggered by a user viewing a page or screen, however Page calls can come from both web and mobile-web views, while Screen calls *only* occur on mobile devices. Because of the difference in platform, the context information collected is very different between the two types of calls.
34
34
35
35
> success ""
36
-
> **Tip**! Segment recommends that you always use the Page and Screen calls when recording a page-view, rather than creating a "Page Viewed" event, because the Page/Screen calls automatically collect much better context information.
36
+
> Segment recommends that you always use the Page and Screen calls when recording a page-view, rather than creating a "Page Viewed" event, because the Page/Screen calls automatically collect much better contextual information.
37
37
38
38
## Anatomy of a Segment message
39
39
40
40
{% include content/message-anatomy.md %}
41
41
42
-
## Message schemas, Blocks, and Specs
42
+
## Segment Spec and event schemas
43
43
44
-
The Segment "Specs" provide recommended message schemas - the information we recommend that you collect - for each type of call. These are recommendations not requirements, but if you follow these schema guidelines the Segment servers can more easily identify parts of your messages, and translate them to downstream tools.
44
+
The Segment Spec provides recommended message schemas for each type of event call (like Identify, Track, Page, and Scren). These schemas help you structure your events in a consistent, predictable format, making them easier to understand, maintain, and map to downstream tools.
45
45
46
-
In addition to the recommended message schemas, Segment also provides "blocks": recommendations on what information to collect and how to format it, for different industries and use cases. These are recommendations only, but by collecting all of the information in these blocks, you can ensure that common tools used in that use-case have the information they need to function.
46
+
The Spec contains two kinds of guidance:
47
47
48
-
A third section of the Spec is the "industry specs" which provide recommendations that include an explicit translation or mapping in the Segment servers, to best power the downstream Destinations commonly used in these industries.
48
+
- Mapped events, like `Order Completed` and `Product Viewed`, are event names and properties that Segment recognizes and transforms automatically for supported destinations. For example, events like `Order Completed` or `Product Viewed` are mapped to standard ecommerce fields.
49
+
- Recommended events, on the other hand, are suggestions for structuring common event types, but Segment doesn't apply automatic transformations. They serve as best practices to help you maintain clean, useful data, especially if you're designing events for custom or internal use cases.
50
+
51
+
Segment also offers industry-specific recommendations, which are collections of events and traits commonly used in verticals like ecommerce or B2B SaaS. Segment designed these recommendations to help you collect the right data to power tools typically used in your industry.
Copy file name to clipboardExpand all lines: src/unify/Traits/predictions/index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,7 +81,7 @@ To access Predictions, you must:
81
81
82
82
#### Successful trait computation
83
83
84
-
This table lists the requirements for a trait to compute successfully:
84
+
To compute a prediction successfully, the model must meet the following requirements. In particular, the target event must occur at least once per day across your workspace during the entire Feature Window. If there are days with no activity, the model may not train successfully.
0 commit comments