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/engage/using-engage-data.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ You can send your Computed Traits and Audiences to your Segment Destinations, wh
9
9
<!-- TODO: image here? -->
10
10
11
11
> success ""
12
-
> **Tip!**You can also use the [Profile API](/docs/unify/profile-api/) to activate Engage data programmatically.
12
+
> You can also use the [Profile API](/docs/unify/profile-api/) to activate Engage data programmatically.
13
13
14
14
## Engage Destination types: Event vs. List
15
15
@@ -215,8 +215,8 @@ Engage includes logic to automatically enrich payloads going to these destinatio
215
215
216
216
If you send events to a destination that requires specific enrichment Segment doesn't already include, [contact Segment](https://segment.com/help/contact/){:target="_blank"}, and we‘ll do our best to address it.
217
217
218
-
> note ""
219
-
> **Note**: Profiles with multiple identifiers (for example, `user_id` and `email`) will trigger one API call per identifier when the audience or computed trait is first synced to a destination.
218
+
> info ""
219
+
> Profiles with multiple identifiers (for example, `user_id` and `email`) will trigger one API call per identifier when the audience or computed trait is first synced to a destination.
220
220
221
221
222
222
## Multiple identifiers of the same type
@@ -273,10 +273,11 @@ When you create a new Computed Trait or Audience in Engage, you can choose to ca
273
273
> success ""
274
274
> **Why would I disable historical data?** You might want to disable historical data if you're sending a triggered campaign. For example, if you want to send an email confirming a purchase, you _probably_ don't want to email users who bought something months ago, but you *do* want to target current users as they make purchases (and thus enter the audience).
275
275
276
-
**Note**: The Facebook Custom Audiences Website destination does not accept historical data, and so only uses data from after the moment you configure it.
276
+
> warning ""
277
+
> The Facebook Custom Audiences Website destination does not accept historical data, and so only uses data from after the moment you configure it.
277
278
278
279
> info ""
279
-
> Use the [Engage settings](/docs/engage/settings/#destinations-settings)){:target="_blank"} to add a destination to your Engage space.
280
+
> Use the [Engage settings](/docs/engage/settings/#destinations-settings){:target="_blank"} to add a destination to your Engage space.
0 commit comments