DMS Direct Linkage Pixel Example Guide

Contents

• Overview
• Web Pixel Examples
• Email Pixel Example
• Tokens

Overview

This guide outlines how to implement the DMS Direct Linkage Pixel for users who are licensing linkage data from us. There are two types of pixel implementations: Web and Email. These pixels allow us to pass hashed identifiers and session metadata to you for your own identity resolution and intent enrichment.

Pixel Types

Web Pixel Examples

Provide us with a “pixel” (image/script/tag) that is to be deployed on our network, using the following as examples:

<img src="https://example.com?id=&md5=&sha1=&sha256=" />

or

<script type="text/javascript" src="https://example.com?id=&md5_email=&sha1_email=&sha256_email="></script>

We also support more complex/nuanced implementations beyond these examples. Please provide us with details of your use case, and we can help you implement the pixel in a way that works best for you.

Email Pixel Example

Provide us with a “pixel” (image or redirection) that is to be deployed in your email creative, using the following as an example:

https://example.com/pixel.gif?id=&md5_email=&sha1_email=&sha256_email=

As with web pixels, we can include any other parameters you need in the URL. The above is simply an example.

Available Tokens

Please let us know which tokens are required and which are optional for your use case. The following tokens are available for use in the pixel. Other tokens may be available upon request.