Getting Started with Cookie Consent Management

cookie consent management ensures that website visitors are informed about any browser storage technologies (e g , cookies, local storage) and empowers visitors to choose the categories of data they allow this is an industry standard requirement that supports global privacy regulations—including gdpr, ccpa/cpra, and other regional frameworks when a site is hosted on your domain, the responsibility for compliance remains with you as the domain owner wildfire’s goal is to ensure that your shopping portal user experience is compliant, transparent, and supported by reliable analytics our goal is to make that requirement as simple and low effort as possible why is it important it keeps you compliant with industry regulations it enables you to start receiving analytics on your shopping portal 2\ our recommended approach osano we recommend osano , a widely used consent management platform (cmp) osano is free for our partners (we cover the cost) requires no development work from your team ensures consent is obtained before analytics or marketing scripts fire provides a transparent, user friendly consent banner how it works (high level) a user lands on the portal hosted on your domain osano displays a consent banner with categories (e g , “strictly necessary,” “analytics”) osano stores the user’s preferences in a cookie that it manages user data will not be included in analytics until the user agrees to the cookie consent policy what you need to do just review and approve our use of osano in your implementation no code changes are required on your side 3\ browser storage & configuration options we maintain a documented list of all browser storage items used in the portal (purpose and expiration, cookies, and any local storage keys) we can provide these to you in either format documentation (pdf or shared doc), or uat environment preview , allowing your team to inspect everything live before launch if you require any additions or modifications before approval, we can accommodate that as part of onboarding 4\ analytics what we collect & how it works anonymous analytics (default) once osano is installed, we can begin firing analytics events we collect anonymous events such as page views impressions clicks/engagement these help us power monthly mbr reporting and optimize the portal experience enhanced analytics (with user opt in) when a user consents to “analytics” cookies, we incorporate non pii user identifiers (e g , hashed ids or internal user tokens) into our event properties this allows session stitching funnel analysis better understanding of user journeys we do not collect, transmit, or store pii in analytics important we will not activate analytics—anonymous or otherwise—until your team explicitly approves our plan 5\ partner options for consent & analytics you may choose one of the following option a — use our standard setup (recommended) we deploy osano on your portal we fire analytics only after your explicit approval we can report on shopping portal metrics in monthly mbrs no cost and no engineering work for your team option b — use your existing consent management platform if your organization already uses a cmp, we can integrate with it your cmp must support category based consent, and trigger a signal before analytics or marketing scripts load we’ll collaborate with your technical team to configure the appropriate integration \<font color="#6b21a8"> for either option chosen above, clients have the option to use their own marketing/analytics tags \</font> if desired, we can add your gtm container, google analytics, adobe analytics, or other marketing pixels to the portal however, we strongly recommend pairing this with a cmp (either osano or yours) to meet compliance requirements again, responsibility for legal compliance resides with your organization so long as users are subject to your organization’s privacy policy and terms of service 6\ next steps to move forward, please select one of the following approve use of osano + our analytics plan (fastest path to launch) request our browser storage documentation propose integration with your own cmp provide your gtm / analytics tags if preferred once we have your decision, we will configure your environment accordingly and include analytics in your ongoing reporting