Untitled

Pass hashed email for enhancing conversions →

Amazon Advertising tag supports the use of your customers’ “hashed” email addresses as an alternative ad identifier to the standard browser cookie

<aside> <img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/fcb5a1f3-6d17-4aa0-adac-91771380b23c/BLANK_ICON.png" alt="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/fcb5a1f3-6d17-4aa0-adac-91771380b23c/BLANK_ICON.png" width="40px" /> With the tag base code added to the page, to include hashed email as an alternative ad-identifier with your event, you can call the JavaScript API with 3 methods. Each of these ad-identity methods requires an identity token to be configured. Token configuration code can be added to the head of the page if you have access to your customers’ emails at page load time. You can also be added it in-line if emails are collected on the specific page. Here’s a valid token configuration ⬇️

</aside>

      const tokenConfig = {
      gdpr: {
      enabled: false, // GDPR is mandatory for EU region token request.
      consent: '', // Valid IAB consent string, v1 or v2 (required if `enabled` is `true`)
      },
      hashedRecords: [{
      type: 'email',
      record: 'aa33a69554a987bff19300338c26ddcb8dd5f99e88183080b41683f9f280e4c9', //SHA256 Hash Required
      }],
      ttl: 9600, // token TTL in seconds
      };

After creating an identity token, the identity JavaScript methods may be called.

To renew the token

• Request a new AMZN-Token, if no AMZN-Token exists in browser cookie and then store the received token in browser cookie.
• This AMZN-Token will be attached to future Amazon Advertising tag submitted events for user identity resolution.
• The Token has an expiration date at most 7 days from the initial token request timestamp. The Token is stored in a browser cookie as: amznToken=sampleTokenValue.
  • A valid token requires valid token request configurations, which are specified above. If no valid consent information is provided for a specific region, an AMZN-NoCookieConsent token is stored in the browser cookie to avoid unnecessary future network requests.

renewToken(tokenConfig);

Here is the complete code including the identity config:

const tokenConfig = {
  gdpr: {
    enabled: false, // GDPR is mandatory for EU region token request.
    consent: '', // Valid IAB consent string, v1 or v2 (required if `enabled` is `true`)
  },
  },
  hashedRecords: [{
    type: 'email',
    record: 'aa33a69554a987bff19300338c26ddcb8dd5f99e88183080b41683f9f280e4c9',
  }],
  ttl: 9600, // token TTL in seconds
};
renewToken(tokenConfig);

To update the token

• Request a new AMZN-Token and store the received token in the browser cookie.
  • It differs from renewToken in that updateToken sends a request regardless of AMZN-Token existence in the browser cookie.
• This AMZN-Token will be attached to future Amazon Ad tag events for user identity resolution.
  • The Token has an expiration date at most 7 days from the initial token request timestamp.
• The Token is stored in the browser cookie as: amznToken=sampleTokenValue. A valid token requires valid token request configurations, which are specified above.

updateToken(tokenConfig);

To delete the token

• Remove existing AMZN-Token or AMZN-NoCookieConsent from browser cookie

deleteToken();