Skip to main content

LiveRamp’s Wholesale Web Match Data

LiveRamp can provide you with a real-time redirection of web match data from our large network of publishers, so that you can read/set your cookie IDs and link them to the hashed email addresses we pass in those redirects. Our web match data consists of the log-in, email open, and logged-in session data our publisher partners send us.

Creating a cookie <> hashed email mapping can power a range of use cases, including CRM on-boarding, offline and cross-device attribution.


For information on receiving mobile app match data, see “LiveRamp's Wholesale Mobile Match Data Feed”.

To enable this, you provide LiveRamp with a tag, which LiveRamp can then redirect to from the publisher’s traffic, including the hashed email address.

For example, when a user with the email address “” signs in to Gotham Daily (a publisher working with LiveRamp), the page loads a LiveRamp tag, passing the email hash (MD5 email hash “1238ac93cb2676d76da8a116b55097e8”).

The LiveRamp tag redirects to your tag:

You then set your cookie on the user’s browser, and record the MD5 hash as linked to that cookie ID.

Set Up Web Match Data Deliveries

To set up web match data real-time deliveries, provide LiveRamp with a tag that supports HTTPS and returns a transparent 1x1 image (typically a gif). The tag must be limited to a single redirect and should complete loading in <500ms. You can download a transparent 1x1 at

LiveRamp will redirect to this tag from our publisher traffic and will include the hashed email address. Here’s an example of a redirect:{MD5 email hash}

LiveRamp also needs the following information:

  • The hash types you want to receive (available hash types are MD5, SHA-1, and SHA-256).

  • Whether you want to receive one hash per hash type or multiple hashes per hash type. To receive multiple email hashes for a user (in the case where we have more than one email for the user), your pixel must be able to accept parameters like

    “{MD5 hash}&md5={2nd MD5 hash}”.

  • The countries you want to receive data from (e.g., U.S. only).

  • Whether you want to receive only users where we have already been able to set and read a cookie ID.


    We recommend against this, as we will not be able to send users we are seeing for the first time (where we are setting a cookie, but have not had a chance to read it as well before sending to buyers). In addition, we generally charge for cookieable data only so this does not result in reduced costs.

  • The number of days we should wait to send hashed email data on the same browser (typically we use 5 days TTL).

  • Any known sources you would like to disable.

  • Whether you want pseudonymized source IDs to be passed as part of the pixel URL. Some buyers want to differentiate between different LiveRamp publishers for quality metrics, reporting, and revenue segmentation, so we can pass a numeric publisher ID (e.g., “24”, “1031”, “5001”) in the redirect.

  • Whether you want our default level of linkages (maximum scale) or a custom level. See “Volume Levers for Wholesale Data” for more information.


Before hashing, all emails are lowercased and any whitespace is removed.