LiveRamp Audiences Destination
Destination Info
- Accepts Track calls.
- Refer to it as Liveramp Audiences, or LiveRamp Audiences in the Integrations object
- This destination is in Beta
LiveRamp 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 into your LiveRamp account to execute various marketing use cases.
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.
The LiveRamp Audiences destination can be connected to Twilio Engage sources only.
Getting started
Set up your file drop
SFTP
- Contact your LiveRamp representative to gain a set of SFTP credentials.
- Connect to the SFTP server using the client of your choice, and create a new folder under
/uploads
with the name of your audience.
S3
- Create a new S3 bucket.
- Create a new IAM Role with
PutObject
access to the S3 bucket. - Create a new IAM User and assign them the role.
- Generate a new Access Key pair for the user and note them down; you’ll use it for the settings.
Connect LiveRamp Audiences
- Create and configure your Engage Audience.
- Navigate to Engage > Engage Settings > Destinations and click Add Destination.
- Select LiveRamp Audiences, select your Audience Space as the source, and name your destination.
- 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.
- Enable the destination and configured mappings.
- On the Engage > Audiences > (your audience) page, click Add Destination and select the destination 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
- File a support case with the LiveRamp team to configure and enable ingestion.
Available Actions
Build your own Mappings. Combine supported triggers with the following LiveRamp Audiences-supported actions:
Mapping limits per destination
Individual destination instances have support a maximum of 50 mappings.
Audience Entered (SFTP)
Uploads audience membership data to a file through SFTP for LiveRamp ingestion.
Audience Entered (SFTP) is a Cloud action. The default Trigger is: event = "Audience Entered"
Field | Description |
---|---|
Username | Type: STRING User credentials for establishing an SFTP connection with LiveRamp. |
Password | Type: PASSWORD User credentials for establishing an SFTP connection with LiveRamp. |
Folder Path | Type: STRING Path within the LiveRamp SFTP server to upload the files to. This path must exist and all subfolders must be pre-created. |
LiveRamp Audience Key* | Type: STRING Unique ID that identifies members of an audience. A typical audience key might be client customer IDs, email addresses, or phone numbers. See more information on LiveRamp Audience Key |
Identifier Data | Type: OBJECT Additional data pertaining to the user to be written to the file. |
Hashable Identifier Data | Type: OBJECT Additional data pertaining to the user to be hashed before written to the file. Use field name phone_number or email to apply LiveRamp’s specific hashing rules. |
Delimeter* | Type: STRING Character used to separate tokens in the resulting file. |
Filename* | Type: STRING Name of the CSV file to upload for LiveRamp ingestion. |
Batch data* | Type: BOOLEAN Receive events in a batch payload. This is required for LiveRamp audiences ingestion. |
Batch Size | Type: NUMBER Maximum number of events to include in each batch. Actual batch sizes may be lower. |
Audience Entered (S3)
Uploads audience membership data to a file in S3 for LiveRamp ingestion.
Audience Entered (S3) is a Cloud action. The default Trigger is: event = "Audience Entered"
Field | Description |
---|---|
AWS Access Key ID | Type: STRING IAM user credentials with write permissions to the S3 bucket. |
AWS Secret Access Key | Type: PASSWORD IAM user credentials with write permissions to the S3 bucket. |
AWS Bucket Name | Type: STRING Name of the S3 bucket where the files will be uploaded to. |
AWS Region (S3 only) | Type: STRING Region where the S3 bucket is hosted. |
LiveRamp Audience Key* | Type: STRING Unique ID that identifies members of an audience. A typical audience key might be client customer IDs, email addresses, or phone numbers. See more information on LiveRamp Audience Key |
Identifier Data | Type: OBJECT Additional data pertaining to the user to be written to the file. |
Hashable Identifier Data | Type: OBJECT Additional data pertaining to the user to be hashed before written to the file. Use field name phone_number or email to apply LiveRamp’s specific hashing rules. |
Delimeter* | Type: STRING Character used to separate tokens in the resulting file. |
Filename* | Type: STRING Name of the CSV file to upload for LiveRamp ingestion. |
Batch data* | Type: BOOLEAN Receive events in a batch payload. This is required for LiveRamp audiences ingestion. |
Batch Size | Type: NUMBER Maximum number of events to include in each batch. Actual batch sizes may be lower. |
Limitations
- Audience must have at least 25 unique members, otherwise the destination will fail and the data will not be synced. This means the Actions Mapping Event Tester does not work (only one test event can be configured).
- Audience sync happens once per day. On a 24-hour cadence, but can take up to 30 hours.
- Audience Sync is a full sync, including only users or accounts in the audience at the time of sync.
- Files are created per audience.
- After initial ingestion is complete, changing the mappings will cause the LiveRamp ingestion to start failing until ingestion setup is run again.
- Time to first sync can be up to 3 days, please be patient.
Trait Enrichment
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.
Trait Enrichment in beta
Trait Enrichment is in beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. Contact Segment with any feedback or questions.
Trait Enrichment setup
- Confirm that Send Track is toggled on and select Customized Setup. Select Add Trait, select the traits you want to sync, and click Save.
- Update the Identifier Data Field in your destination Audience Entered Mapping (either SFTP or S3).
- 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, useproperties.TRAIT
as an event variable.
- To update a trait field mapping, click on the Select event variable section and in the dropdown search for
For best results with Trait Enrichment, Segment recommends the following:
- Use Trait Enrichment with new audiences.
- Use smaller audiences for real-time use cases, as data delivery is slower for large audiences.
This page was last modified: 01 May 2024
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!