Implementation Details
Depending on your implementation method, follow these steps.
Implementation method | Steps |
---|---|
Tags in Adobe Experience Platform | Assuming that you have the Adobe Analytics extension installed, add the following context data variable definition to the custom code editor within the Action configuration of a Rule:s.contextData['cm.ssf'] = '1' Note: Define the contextdata variable and set it to 1 if a customer does not consent to targeted marketing. Set the contextdata variable to 0 for customers who consented to targeted marketing. |
AppMeasurement | Add the context data variable definition to the AppMeasurement.js file:s.contextData['cm.ssf'] = '1' Note: Define the contextdata variable and set it to 1 if a customer does not consent to targeted marketing. Set the contextdata variable to 0 for customers who consented to targeted marketing. |
Reporting (Optional)
You can use Adobe Analytics to report on how much of your traffic is consent based and as a result has been server-side forwarded versus how much of your traffic isn’t consent based and has not been forwarded to Adobe Audience Manager.
To configure this type of reporting, map the new context variable to a custom traffic variable (prop) via processing rules. To do so
-
Implement the “cm.ssf” variable (as shown above.)
-
Use processing rules to map the context variable to the prop.
- Go to Analytics > Admin > Report Suites , then select a report suite.
- Click Edit Report Suite > General > Processing Rules .
- Click Add Rule.
- Under Always Execute, overwrite the value of the prop you had enabled with the context variable “cm.ssf(Context Data)”.
- Click Save.