Add the 33across hem optional parameter to the documentation

prebid · Jan 8, 2025 · b0f0b3e · b0f0b3e
1 parent 9aaf096
commit b0f0b3e
Showing 1 changed file with 6 additions and 2 deletions.
diff --git a/dev-docs/modules/userid-submodules/33across.md b/dev-docs/modules/userid-submodules/33across.md
@@ -30,6 +30,7 @@ The following configuration parameters are available:
 | name | Required | String | The name of this sub-module | `"33acrossId"` |
 | params ||| Details for the sub-module initialization ||
 | params.pid | Required | String | Partner ID (PID) | Please reach out to [[email protected]](mailto:[email protected]) and request your PID |
+| params.hem | Optional | String | Hashed email address in sha256 format | `"ba4235544d6c91865fb07.."` |
 | params.storeFpid | Optional | Boolean | Indicates whether a supplemental first-party ID may be stored to improve addressability | `true` (default) or `false` |
 | params.storeTpid | Optional | Boolean | Indicates whether a supplemental third-party ID may be stored to improve addressability | `true` (default) or `false` |
 | storage |||||
@@ -46,8 +47,7 @@ pbjs.setConfig({
     userIds: [{
       name: "33acrossId",
       params: {
-        pid: "0010b00002GYU4eBAH", // Example ID
-        storeFpid: true
+        pid: "0010b00002GYU4eBAH" // Example ID
       },
       storage: {
         name: "33acrossId",
@@ -59,3 +59,7 @@ pbjs.setConfig({
   }
 });
 ```
+
+## HEM Collection
+
+33Across ID System supports user's hashed emails (HEMs). HEMs could be collected from 3 different sources in following priority order: `hem` configuration parameter, global `_33across.hem.sha256` field or from storage (cookie or local storage).