Show Menu
TOPICS×

Namespaces

Each ID that you want to be able to search for is assigned a namespace, which is a custom string that identifies that ID in any variable where it is used across all your report suites.
The namespace string is used to identify the field(s) that you want searched when providing an ID as part of a GDPR request. When a GDPR request is submitted, the request will include a JSON section specifying the data subject IDs to use for the request. Multiple IDs can be included as part of a single request for a data subject. The JSON includes:
  • A "namespace" field containing the namespace string.
  • A "type" field that for most Adobe Analytics requests contains the value "analytics".
  • A "value" field containing the ID that Analytics should search for in the associated namespace variables from each of your report suites.
Refer to the Experience Cloud GDPR API documentation for more details.

Custom Visitor ID

{
     namespace: "customVisitorID",
     type: "analytics",
     value: "<ID>"
}

The namespace is also predefined for the custom visitor ID.

IDs in Custom Variables

{
    namespace: "Email Address",
    type: "analytics", 
    value: "john@xyz.com" }, 
{
    namespace: "CRM ID", 
    type: "analytics", 
    value: "123456-ABCD" 
}

For IDs in custom traffic or conversion variables (props or eVars), label the variable with an ID-DEVICE or ID-PERSON label, then assign your own namespace name to that type of ID. See Provide a Namespace when Labeling a Variable as ID-DEVICE or ID-PERSON .
You can also see namespaces that you have previously defined for other variables or report suites and reuse one of those, so that the same namespace can easily be used for all your report suites that store that type of ID. It is also possible to assign the same namespace to multiple variables within a report suite. For example, some customers store a CRM ID in a traffic variable and a conversion variable (depending on the page, it is sometimes in one or the other or both), and they could assign the namespace "CRM ID" to both variables.
Avoid using the friendly name of a variable (the name displayed in the reporting UI) or the variable’s number (such as eVar12) when specifying the namespace to the GDPR API, unless it is the namespace specified when applying the ID-DEVICE or ID-PERSON label. Using a namespace rather than a friendly name allows the same user identity block to specify the correct variable for multiple report suites. For example, if the ID is in different eVars in some of the report suites, or if the friendly names don’t match (such as when the friendly name has been localized for a specific report suite).
The namespaces "visitorId" and "customVisitorId" are reserved for identifying the Analytics legacy tracking cookie and the Analytics customer visitor ID. Do not use these namespaces for custom traffic or conversion variables.