Fulfill Data Subject Requests with LiveRamp Integrations

The Integrations Gallery includes two out-of-the-box LiveRamp workflows that help organizations fulfill data deletion and right to opt-out privacy requests from OneTrust to LiveRamp. Together, these workflows enable joint OneTrust and LiveRamp customers to send privacy requests to LiveRamp directly from OneTrust using the information provided by the requester. This helps privacy teams manage deletion and opt-out requests within the same privacy automation process they already use, reducing manual work, improving operational consistency, and lowering the risk of delays that could affect compliance timelines.

Prerequisites

Contact your LiveRamp account manager to request Privacy API access and additional support for your organization.

Before configuring the integration, obtain the username, password, client ID, client secret, and organization ID that LiveRamp provides. Store these values securely and do not share secrets through email, chat, or support tickets.

  • Integration manager role to create and configure workflows

  • Access to a request workflow in Privacy Rights Automation

  • A valid email address on each privacy request (DSR)

  • Your LR-Org-ID for API request headers

  • Provision of the following details from LiveRamp (required for OneTrust-based credentials):

    • Username

    • Password

    • Client ID

    • Client Secret

Tip:

For more information on LiveRamp APIs, see the following developer resources:

To create credentials

  1. On the Integrations menu, click Credentials.

    The Credentials screen appears.

  2. Click the Add credential button.

    The Create credentials - Select existing system screen appears.

  3. Search and select LiveRamp in the field, then click the Next button.


    The Create credentials - Enter credential details screen appears.

  4. Configure the credential with the following:


    Field
    Description
    Credential name

    Provide a unique name for this new credential.

    Application type

    Select Web app.

    Authentication method

    Select OAuth 2.0.

    Grant type

    Select Password credentials.

    Access token URL

    Enter this access token URL: https://serviceaccounts.liveramp.com/authn/v1/oauth2/token

    User Name

    Provide your username from the LiveRamp account.

    Password

    Provide your password from the LiveRamp account.

    Client ID

    Provide the Client ID from the LiveRamp account.

    Client Secret

    Provide the Client Secret from the LiveRamp account.

    Hostname

    Ensure this is provided.

    Send authentication parameters in

    Select Form URL encoded.

    Send credentials in

    Select HTTPS headers.

    Additional headers and parameters

    Ensure this is disabled.

  5. Click the Save button.

To create the Data Deletion workflow

  1. On the Integrations menu, click Gallery.

    The Integration gallery screen appears.

  2. Search and select the LiveRamp tile.


    The Gallery details screen appears.

  3. Click the Add button on the [PRA] - Fulfill request - Create data deletion request in LiveRamp workflow.


    The Add workflow name modal appears.

  4. Provide the new workflow with a unique name, credentials, and notification email, then click the Create button.


    The Integration builder screen appears.

  5. For the POST - Create Deletion Privacy Requests action, you will need to provide the value for the LR-Org-ID in the request headers.


  6. Click the Activate button to enable the workflow for use. You can now use this connection to either:

    • Add connections to specific request workflow stages during workflow configuration that will trigger upon advancement to that stage.

    • Add connections to active requests on the current stage to automatically launch the connection.



To create the Opt-Out workflow

  1. On the Integrations menu, click Gallery.

    The Integration gallery screen appears.

  2. Search and select the LiveRamp tile.


    The Gallery details screen appears.

  3. Click the Add button on the [PRA] - Fulfill request - Create data opt-out request in LiveRamp workflow.


    The Add workflow name modal appears.

  4. Provide the new workflow with a unique name, credentials, and notification email, then click the Create button.


    The Integration builder screen appears.

  5. For the POST - Create Opt-out Privacy Requests action, you will need to provide the value for the LR-Org-ID in the request headers.


  6. Click the Activate button to enable the workflow for use. You can now use this connection to either:

    • Add connections to specific request workflow stages during workflow configuration that will trigger upon advancement to that stage.

    • Add connections to active requests on the current stage to automatically launch the connection.



To add connections to active requests

Note:

Both workflows can be added in this manner. The following steps use the deletion workflow as an example.

  1. On the Privacy Rights Automation menu, click Requests.

    The Requests screen appears.

  2. Search and select for a Data Deletion request.

    The Data subject request details screen appears.

  3. Go to the Subtasks tab on the current workflow stage.
  4. Click the Add connection button.


    The Add connection side pane appears.

  5. Select Create a new subtask.

    The Add existing connection section appears.

  6. Search and select your create data deletion request workflow, then click the Next button.


    The Configure subtask section appears.

  7. Update the subtask name and details as needed, then click the Add button.
    Note:

    This configuration ability can be used to edit the subtask name to align with an existing integration that references a unique subtask name for its trigger. If you do not edit the default name to match, downstream connections may be broken or not be able to run as intended.



  8. The subtask will fire and be in Processing. Use the Refresh icon to update the status.


  9. If the subtask connection is successful, it will update to Complete.


  10. If the subtask fails, use the Context menu icon to either retry the task or check the Integration log for troubleshooting.


  11. You can validate that the request was created successfully by checking the integration logs.


FAQ

Can we test the LiveRamp integration before going live?

Yes. Use the staging credentials and staging URL provided by LiveRamp when configuring the integration in OneTrust. After the credential test succeeds, save the credential, add and activate the required LiveRamp workflows, and manually attach a workflow to a test data subject request. Verify the request in the OneTrust integration logs before moving to production.

For technical information about LiveRamp Privacy API authentication and requests, see the LiveRamp developer site.

What is the most common or likely setup issue?

A valid email address is required. If the request email is missing or mapped from a custom attribute incorrectly, the subtask can fail and the activity details may indicate that the API requires a valid email address.

What happens if the integration fails?

If a system subtask fails, users can open the Context menu on the subtask and select Retry Task to rerun it.

Do these workflows have to be tied to a workflow stage?

No. These workflows can be added to a workflow stage so they run automatically when the request reaches that stage. A subtask can also be added manually for testing instead of being seeded to a stage first.

Does the request type label need to match LiveRamp exactly?

No. For deletion requests, the integration sends a static deletion value in the API call. Customers can attach the subtask to whatever internal workflow or stage they use for deletion, even if the request label uses different wording such as Right to Be Forgotten or Deletion Request.

Should deletion and opt-out be handled in the same workflow? If both are handled in one workflow, what should customers consider?

It depends on the customer’s process. Customers may structure these requests in different ways depending on workflow, department, or legal review needs, so a single shared path is not always the best option.

Customers may need separate stages and should think carefully about sequencing. For example, if a customer opts a user out and then deletes their data, the later step may remove the email address or other customer data needed for follow-up processing.

Is every request detail required in order to use the integrations?

No, because fields like First Name, Last Name, and Zip Code can be blank without causing the request to fail. Optional values may still be passed as empty strings in the API request.

What happens if the request is a duplicate?

If the same email address has already been used for a similar request, LiveRamp can return a duplicate response. Customers should review the subtask response to confirm how the request was handled.

Should expected processing time be configured during the connection setup?

This is optional if you want to provide estimated guidance on expected processing.