Email Retargeting for Advertisers - Hash Redirect Pixel
Overview
The Traverse Retargeting synchronous pixel integration allows an advertiser to look up the email hash of a given site visitor via an HTTP redirect.
Calling our pixel
Our endpoint uses the following URL:
https://api.traversedlp.com/retargeting/v1/match/lookup
OR
https://api.traversedlp.com/s1rml
URL Parameters
| Parameter | Description | Required |
|---|---|---|
campaignId |
Your campaign ID | Yes |
redirect |
URL to have the request redirected to. This should be URLencoded if additional parameters are included. If no protocol is specified, we will assume https. | Yes |
timeout |
Timeout, in MS for the lookup. Defaults to 1000. | No |
Any values passed using non-reserved parameters will be sent to your redirect
URL with the same parameter names. The following parameters are reserved:
emailMd5Lower, emailSha1Lower, timeout, campaignId, and redirect.
Redirect URL
Our tag will 302 redirect to the URL you provide. If a match is found, the MD5
email hash and SHA1 hash will be returned as emailMd5Lower and emailSha1Lower
respectively. We do not support returning SHA256 at this time.
As specified above, any values passed using non-reserved parameters will be sent to your redirect URL with the same parameter names.