Depending on the feature functionality you are leveraging, setting up web applications requires some or all of the following:
- Tag Deployment - Required for all configurations
- Identity Configuration - Required for all configurations
- Jurisdiction Configuration - Required for all configurations
- Experience Trigger Configuration - Required only if you intend to leverage Preference Management Experiences.
Implement this script as high in the global head of the page as possible.
Tag Manager Implementation
Because Ketch helps ensure consumer's data privacy choices are accurately enforced within data management systems, identity management is an important topic. Once you have decided what identity spaces should be passed to Ketch and created them within the product, you can leverage one of the following methods to pass them to Ketch:
We strongly recommend that any identity you want to pass to Ketch, that you do so through a data layer.
A data layer is an object that contains all of the information that you want to pass to a Tag Management System, or any external party that is on your website. For more information on data layers and how to set one up, please reference the following documentation:
Once you have made the identity a variable on page, make sure to update the configuration in the Property.
If you have chosen not to implement a data layer, you can still insert the identity into the page as a variable. Once you have made the identity a variable on page, make sure to update the configuration in the Property.
If you do not want to pass the identity into a variable on the page to be picked up, simply indicate the location "Cookie" in the data layer configuration of the Property. Provided the cookie is a first party cookie (set by the same domain of the application), Ketch will be able to pick it up and use it.
No First Party Cookie
If you are early in the development of your consumer identity management strategy and have not yet implemented a cookie on your site, Ketch will set and maintain a first party cookie space on your behalf.
If you have chosen to pass Jurisdiction data to Ketch, you must do so through the data layer. Jurisdiction variables are expected to contain the code of the Jurisdiction.
If you are leveraging the Experience Server, while the Consent & Disclosure Experiences are displayed automatically, you will need to call a Ketch function when you want to show the Preference Management Experience. Frequently, this is attached to a link in the footer for "privacy preferences", "my privacy settings", or "privacy details".