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-liveramp-audiences/index.md
+33-2Lines changed: 33 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ hide-boilerplate: true
4
4
hide-dossier: false
5
5
id: 644ad6c6c4a87a3290450602
6
6
private: true
7
-
hidden: true
7
+
hidden: false
8
8
---
9
9
10
10
[LiveRamp](https://liveramp.com/){:target="_blank"} gives companies and their partners the power to connect, control, and activate data to transform customer experiences and generate more valuable business outcomes. Segment's integration with LiveRamp enables you to push user audiences created in [Twilio Engage](https://www.twilio.com/en-us/engage){:target="_blank"} into your LiveRamp account to execute various marketing use cases.
@@ -35,13 +35,44 @@ The LiveRamp Audiences destination can be connected to **Twilio Engage sources o
35
35
5. Enable the destination and configured mappings.
36
36
6. On the **Engage > Audiences > (your audience)** page, click **Add Destination** and select the destination just created.
37
37
7. Disable *Send Identify* and Enable *Send Track*. Keep event names as they are.
38
+
8. File a [support case](https://docs.liveramp.com/connect/en/considerations-when-uploading-the-first-file-to-an-audience.html#creating-a-support-case) with the LiveRamp team to configure and enable ingestion
38
39
39
40
{% include components/actions-fields.html settings="false"%}
40
41
42
+
## Public Beta Insturctions
43
+
* The Segment team will need to enable the feature for your Engage spaces.
44
+
* Once you agree to join the public beta, we will enable all Engage spaces that are part of your Segment workspace.
45
+
46
+
*Note – Any new Engage spaces you create will not automatically be enrolled. Please contact us to have these new Engage enrolled enabled.*
47
+
48
+
41
49
## Limitations
42
50
43
51
* Audience must have at least 25 unique members, otherwise the destination will fail and the data will not be synced.
44
52
* Audience sync happens once per day.
45
53
* Audience sync is a full sync.
46
54
* Files are created per audience.
47
-
* After initial ingestion is complete, changing the mappings will cause the LiveRamp ingestion to start failing until ingestion setup is run again.
55
+
* After initial ingestion is complete, changing the mappings will cause the LiveRamp ingestion to start failing until ingestion setup is run again.
56
+
57
+
## Trait Enrichment
58
+
59
+
Use Trait Enrichment to access Segment profile traits when you sync Audiences to Destinations. With Trait Enrichment, you can use custom, SQL, computed, and predictive traits to enrich the data you map to your destinations.
60
+
61
+
> info "Trait Enrichment in beta"
62
+
> Trait Enrichment is in beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. [Contact Segment](https://segment.com/help/contact/){:target="_blank"} with any feedback or questions.
63
+
64
+
Trait Enrichment setup
65
+
66
+
1. Confirm that *Send Track* is toggled on and select Customized Setup. Select **Add Trait**. Then, select the traits you want to sync and click **Save**.
67
+
68
+

69
+
70
+
2. Update the **Identifier Data** Field in your destination **Audience Entered** Mapping (either SFTP or S3).
71
+
- To update a trait field mapping, click on the *select event variable* section and in the dropdown search for `properites.` follwed by your trait. For example, `properties.firstName`. If no matches found, click use `properties.TRAIT` as an event variable.
72
+
73
+

74
+
75
+
For best results with Trait Enrichment, Segment recommends:
76
+
- Using Trait Enrichment with new audiences.
77
+
- Using smaller audiences for real-time use cases, as data delivery is slower for large audiences.
0 commit comments