LiveRamp LiveRamp gives companies and their partners the power to connect, control, and activate data to transform customer experiences and generate more valuable business outcomes. Our integration with LiveRamp enables you to push user audiences created in Audience Manager into your LiveRamp account to execute various marketing use cases.
In order to enable the mParticle integration with LiveRamp, you will need the credentials for the SFTP location used to upload files to LiveRamp.
Contact your LiveRamp rep and request that uploads from mParticle be enabled. Let your LiveRamp rep know which of your LiveRamp audiences you wish to upload Device and PII data to.
The LiveRamp integration only supports SFTP for uploading data to LiveRamp.
At this time the integration only supports LiveRamp in the United States, not the United Kingdom, Canada or France.
Send PII to LiveRampis selected, you will be able to select the columns and data contained in the PII file that is sent to LiveRamp. You will also have the option of hashing all email and phone values sent to LiveRamp. If
Send Device IDs to LiveRampis selected, the standard LiveRamp file format for DeviceIDs will be used and you will not have the option to choose file format and contents.
Depending on the Connection Settings that you select see Connection Settings, LiveRamp will use one or more of the following IDs to match users:
Send Device IDs to LiveRamp is selected, a file containing the following IDs will be sent to LiveRamp:
Send PII to LiveRamp is selected, a file containing the fields specified in the Connection Settings will be sent to LiveRamp:
The LiveRamp Audience Integration uploads data to the SFTP location you specify nightly at 12am EST. When the integration is first configured and connected to an Audience the first file(s) will be sent at 12am EST. As long as the integration is active, each night the audience membership will be evaluated and new file(s) will be uploaded to LiveRamp. This allows you to keep the audiences in LiveRamp and other downstream systems in sync.
When you connect an mParticle audience to LiveRamp, mParticle will upload a CSV file to LiveRamp nightly for each selected data type (Device and PII). The files will be named using a combination of your mParticle Org ID, the Audience ID, the upload date, and the data type. For example
3242_17095-D_2020-04-01.csv. Each file will be available as a “segment” in LiveRamp. You should ignore these segments in LiveRamp, unless you specifically want to distribute the mParticle audience as it was on one particular day.
LiveRamp will also create segments with names based on the External Name of the mParticle audience. For example, if your mParticle audience is called
High-value customers, then the segments in LiveRamp will be called
High-value customers-D (Device) and
High-value customers-PII (PII). LiveRamp updates these segments each night based on the data uploaded by mParticle. These are the segments you should add to LiveRamp distributions, since LiveRamp will keep your distributions up to date as mParticle sends more data.
LiveRamp enforces certain file limitations for all files sent to LiveRamp. If you attempt to send data to LiveRamp that does not meet these criteria LiveRamp may not process the files.
|Setting Name||Data Type||Default Value||Description|
||Blank||The name of the integration configuration.|
||Blank||Username for logging into the SFTP destination.|
||Blank||Password for logging into the SFTP destination.|
|Encrypt this file||
||False||If enabled, all files sent to LiveRamp will be GPG/PGP-encrypted using LiveRamp’s public key and will be automatically decrypted when automated ingestion is set up within LiveRamp. Even if this option is not selected, the data will be securely transmitted using the SFTP protocol.|
|Data Type Settings|
|Send Device IDs to LiveRamp||
||False||If enabled, mParticle will send all Device IDs to LiveRamp.|
|Send PII to LiveRamp||
||False||If enabled, mParticle will send PII values the user selects to LiveRamp.|
Was this page helpful?