Convert User IDs from Amperity to Universal IDs
Beta feature
Use the DSP integration with the Amperity customer data platform to convert your organization’s first-party hashed email addresses to universal IDs for targeted advertising.
-
(To convert email addresses to RampIDs; advertisers with ÃÛ¶¹ÊÓƵ Analytics for Advertising) Set up tracking to enable Analytics measurement.
-
Compare the number of universal IDs with the number of hashed email addresses.
Step 1: Set up tracking for Analytics measurement analytics-tracking
Advertisers with ÃÛ¶¹ÊÓƵ Analytics for Advertising)
To convert email addresses to RampIDs or ID5 IDs, you must do the following:
-
(If you haven’t already done so) Complete all prerequisites for implementing Analytics for Advertising and make sure that the AMO ID and EF ID are being populated in your tracking URLs.
-
Register with the universal ID partner and deploy universal ID-specific code on your webpages to match conversions from the IDs on desktop and mobile web browsers (but not mobile apps) to view-throughs:
- For RampIDs: You must deploy an additional JavaScript tag on your webpages to match conversions from the IDs on desktop and mobile web browsers (but not mobile apps) to view-throughs. Contact your ÃÛ¶¹ÊÓƵ Account Team, who will give you instructions to register for a LiveRamp LaunchPad tag from LiveRamp Authentication Traffic Solutions. Registration is free, but you must sign an agreement. Once you register, your ÃÛ¶¹ÊÓƵ Account Team will generate and provide a unique tag for your organization to implement on your webpages.
Step 2: Create an audience source in DSP source-create
-
Create an audience source to import audiences to your DSP account or an advertiser account. You can choose to convert your user identifiers to any of the available universal ID formats.
The source settings will include an auto-generated source key, which you’ll use to push the segment data.
-
After you create the audience source, share the source code key with the Amperity user.
Step 3: Prepare and share segment-mapping data map-data
The advertiser must prepare and share segment-mapping data.
-
Within Amperity, hash the email IDs for the audience using the SHA-256 algorithm.
-
The advertiser must give segment-mapping data to the ÃÛ¶¹ÊÓƵ Account Team to create the segments in DSP. Use the following column names and values in a comma-separated values file:
-
External Segment Key: The Amperity segment key associated with the segment.
-
Segment Name: The segment name.
-
Segment Description: The purpose or rule of the segment, or both.
-
Parent ID: Keep blank
-
Video CPM: 0
-
Display CPM: 0
-
Segment Window: The segment time-to-live.
-
Step 4: Request a data push from Amperity to DSP push-data
-
After the segment is mapped within DSP, the advertiser must work with their Amperity representative to distribute the segment data to DSP.
-
The advertiser must then confirm with the ÃÛ¶¹ÊÓƵ Account Team that the segment data was received.
The segments should be available in DSP within 24 hours. Verify in your audience library (which is available when you create or edit an audience from Audiences > All Audiences or within placement settings) that the segment is available and is populating.
The segments will be refreshed as configured for the advertiser within Amperity. Regardless of how frequently the segment is refreshed, inclusion in a segment expires after 30 days by default or after a customer-specified expiration period. Refresh your segments by re-pushing them from Amperity prior to the expiration. To request a custom segment expiration, contact your ÃÛ¶¹ÊÓƵ Account Team.
Step 5: Compare the number of universal IDs with the number of hashed email addresses compare-id-count
After DSP receives the segment data, the audience count should be visible within nine (9) hours.
In your audience library (which is available when you create or edit an audience from Audiences > All Audiences or within placement settings) compare the number of universal IDs with the number of original hashed email addresses. For information about acceptable ID translation rates and why the segment counts can vary, see “Data Variances Between Email IDs and Universal IDs.â€
Troubleshooting
To troubleshoot translation rate and user count issues, see “Support for Activating Universal IDs.â€
To troubleshooting issues with the conversion procedure, contact your ÃÛ¶¹ÊÓƵ Account Team or adcloud-support@adobe.com.