Skip to main content

Submit Domains/Bundle IDs for Privacy and Data Ethics Review

To ensure that your sites fulfill the privacy and data ethics criteria, you are required to submit the domains or bundle IDs (for Mobile ATS SDK) where ATS will be used for a review. A placement ID will be generated once you have passed the privacy review and you will then be able to implement ATS on your sites and apps.

About Placement ID

Your placement ID plays a crucial role within ATS as it will be used for determining the loading rules and for making sure your property is following all LiveRamp's requirements for running ATS. Each placement ID represents domains which are the websites where ATS will be running or bundle IDs for apps if you are running ATS via our Mobile SDK.

How it Works

Via our easy-to-use wizard, LiveRamp will perform two types of privacy review of your domain(s) for each country: an automated privacy review and a manual one by one of our team members. If you have submitted your placements for an automated review and did not meet all the criteria, you could still submit your placements for a manual review. If you have met all the criteria during the automated review, you must still go through a manual review.

You can still configure ATS in test mode while your placement is still pending for approval. During this time your configuration will use a (temporary) test ID instead of the actual placement ID and will log all library events in Console.

Note

If you’re not able to view, edit, or publish an ATS placement or configuration, you may not have the required permission to do so. If you are the account creator, all permissions will be granted by default. See Create and Manage Users to learn more.

Check the Recommendations

First, check if the countries you want to run ATS in are included in the list of ATS Supported Countries. Then, check our recommendations for your CMP and privacy policy language to ensure you pass the LiveRamp privacy and data ethics review:

If you are running ATS in multiple countries that do not include the EU, you can check out the following recommendations to save time from implementing multiple privacy policy languages:

How to Submit Your Placement for Privacy Reviews

  1. Log in to launch.liveramp.com.

  2. From the navigation menu, select the "ATS" tab.

  3. In the "Placement" area, click New.

  4. Enter a placement name and then click Let's Go.

    The Privacy Review section opens. For now, the field for Placement ID is still empty and will be automatically filled in after your request is approved.

    Placement_-_privacy_review.png

    Note

    Is an account ID or pixel ID required? Most publishers will not receive an account or pixel ID. An account ID is only used if you implement a less common "publisher ID" workflow in ATS. A pixel ID is only assigned if you're contributing third-party cookie matches to LiveRamp outside of ATS.

  5. In the "List of Countries" area, click Add to specify the countries you want to run ATS in.

    Placement_-_Add_countries.png
  6. In the "Domains/Bundle ID" area, click New to add your desired domains and privacy policies. You can do this individually or in bulk by uploading a .csv file.

    Placement_-_add_domains.png

    Caution

    You must note the following when you're adding your domains/bundle IDs:

    • Include all domains and subdomains where ATS will be used. Note that only the domains entered here can be used as a filter for ATS Analytics.

    • For domains, make sure the domain path is an exact copy of what Prebid is passing in the bid request (we do not check for www., http:// or https://).

    • For bundle IDs, it should be in the following format for Android com.liveramp.android and like so for iOS com.liveramp.ios.

    • To add your domains/bundle IDs via a .csv file:

      1. Create a .csv file with a line for each domain or subdomain, with the associated privacy policy URL separated by a comma. See the example below for domains or click here to download a .csv file template:

        PP-Request_Placement_ID-csv_file_example.png
      2. When your file is ready, click CSV Upload.

        Placement_-_Export.png
      3. In the pop up, click Yes to confirm that the upload will overwrite your previous domains.

      4. Select the .csv file you created and click Open.

        Caution

        CSV uploads overwrite your domain list, so make sure that you always provide the full list of domains in your CSV upload. Uploading a CSV file will also completely replace any existing domains or privacy policies.

    • To add your domains/bundle IDs individually:

      1. Enter a domain in the Domain field and provide the URL to its associated privacy policy.

      2. To add additional domains or subdomains, click the plus sign symbol.

      3. After you've entered all domains and subdomains, click Save.

        Placement_-_manually.png
  7. To submit your placement for privacy reviews, click Submit. Optionally, you can save your work by clicking Save and return to this page at a later time.

  8. After clicking Submit, a pop up opens. You must confirm that you’ve read the recommendations and made the necessary changes, then click Run review.

    Note

    You must still go through a manual review even after you pass all criteria during the automated review.

  9. Once an automated review is done, you will be able to see which criteria you did not meet. Click Download Report to check for any pending actions on your side. You can still submit your placement for a manual review even if you did not meet all the criteria.

  10. Click Submit to submit your placement for a manual review.

    Note

    When a Placement is already approved, the Submit button will be disabled until you make an adjustment to the Placement settings.

The status of the placement changes to "Pending Review". LiveRamp must review and approve or reject your request before you can make further changes. Once your placement request has been approved, the approval state changes to "Approved".

What's Next

You don't have to wait until your placement is approved to set up ATS. If you're ready to get started with ATS configuration, See Create an ATS for Web Configuration.

If you plan to interact directly with the ATS API, we will be in contact with you after we review your request.