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:

1. It keeps you compliant with industry regulations
2. 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):

1. A user lands on the portal hosted on your domain.
2. Osano displays a consent banner with categories (e.g., “Strictly Necessary,” “Analytics”).
3. Osano stores the user’s preferences in a cookie that it manages.
4. 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.

For either option chosen above, Clients have the option to use their Own Marketing/Analytics Tags

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:

1. Approve use of Osano + our analytics plan (fastest path to launch)
2. Request our browser storage documentation
3. Propose integration with your own CMP
4. 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.

Updated 17 Jun 2026