Skip to content

Commit 486bcac

Browse files
authored
Merge pull request #5360 from segmentio/rajul/liveramp-docs-update
LiveRamp Docs
2 parents ff43e31 + a7d7225 commit 486bcac

File tree

3 files changed

+38
-7
lines changed

3 files changed

+38
-7
lines changed

src/connections/destinations/catalog/actions-liveramp-audiences/index.md

Lines changed: 38 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,45 +3,76 @@ title: LiveRamp Audiences Destination
33
hide-boilerplate: true
44
hide-dossier: false
55
id: 644ad6c6c4a87a3290450602
6-
private: true
7-
hidden: true
86
---
97

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.
8+
[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 lets you 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.
119

1210
The LiveRamp Audiences destination allows users to connect their Engage Audiences to LiveRamp through their SFTP or a customer-managed S3 cloud storage bucket. Users will be able to configure their delivery preferences within Segment.
1311

1412
The LiveRamp Audiences destination can be connected to **Twilio Engage sources only**.
1513

1614
## Getting started
1715

18-
### Setup your file drop
16+
### Set up your file drop
1917

2018
#### SFTP
19+
2120
1. Contact your LiveRamp representative to gain a set of [SFTP](https://docs.liveramp.com/connect/en/upload-a-file-via-liveramp-s-sftp.html){:target="_blank"} credentials.
2221
2. Connect to the SFTP server using the client of your choice, and create a new folder under `/uploads` with the name of your audience.
2322

2423
#### S3
24+
2525
1. Create a new S3 bucket.
2626
2. Create a new IAM Role with `PutObject` access to the S3 bucket.
2727
3. Create a new IAM User and assign them the role.
2828
4. Generate a new Access Key pair for the user and note them down; you'll use it for the settings.
2929

3030
### Connect LiveRamp Audiences
31+
3132
1. Create and configure your Engage Audience.
32-
2. Navigate to **Engage > Engage Settings > Destinations** tab and click **Add Destination**.
33+
2. Navigate to **Engage > Engage Settings > Destinations** and click **Add Destination**.
3334
3. Select **LiveRamp Audiences**, select your Audience Space as the source, and name your destination.
3435
4. On the **Mappings** tab, click **Add Mapping** and choose whether your will be using S3 or SFTP to upload the files. Within the mapping, configure which fields from your payload will be included in the files.
3536
5. Enable the destination and configured mappings.
3637
6. On the **Engage > Audiences > (your audience)** page, click **Add Destination** and select the destination just created.
37-
7. Disable *Send Identify* and Enable *Send Track*. Keep event names as they are.
38+
7. Disable **Send Identify** and Enable **Send Track**. Keep event names as they are.
39+
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){:target="_blank"} with the LiveRamp team to configure and enable ingestion.
3840

3941
{% include components/actions-fields.html settings="false"%}
4042

43+
## Public Beta instructions
44+
45+
* The Segment team will need to enable the feature for your Engage spaces.
46+
* Once you agree to join the public beta, Segment will enable all Engage spaces that are part of your Segment workspace.
47+
* New Engage spaces you create won't automatically be enrolled. [Contact Segment](https://segment.com/help/contact/){:target="_blank"} to get these spaces enrolled.
48+
4149
## Limitations
4250

4351
* Audience must have at least 25 unique members, otherwise the destination will fail and the data will not be synced.
4452
* Audience sync happens once per day.
4553
* Audience sync is a full sync.
4654
* 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**, select the traits you want to sync, and click **Save**.
67+
68+
![Alt text](traitEnrichment-EngageSettings.png)
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 `properties`, followed by your trait. For example, `properties.firstName`. If no matches are found, use `properties.TRAIT` as an event variable.
72+
73+
![Alt text](traitEnrichment-Mappings.png)
74+
75+
For best results with Trait Enrichment, Segment recommends the following:
76+
77+
- Use Trait Enrichment with new audiences.
78+
- Use smaller audiences for real-time use cases, as data delivery is slower for large audiences.
Loading

0 commit comments

Comments
 (0)