How does Osano price for consent management?

We price consent management based on the number of times the Osano.js script is served up to a device. We call this, "Traffic." Since this script is cached for 24 hours by your device/browser, we use your average daily active users (DAUs) to estimate pricing. You can find your daily active users in Google Analytics and other common web analytics platforms. If you have mobile and web applications, add up your average daily active users across each of the platforms.

We always look at the 3-month rolling average of your traffic. Should the 3-month rolling average exceed your contracted level, we'll bill you the prorated amount.

How does Osano define traffic?

Traffic is calculated as a single visitor requesting the Osano CMP library (the osano.js) from one of our servers per 24-hour period. Traffic is calculated irrespective of whether a new consent dialog is displayed to the end-user.

Prior to implementation, organizations can estimate their traffic in two ways:

• Average Daily Active Users ("DAU"): Most similar to the definition of traffic above

• Unique Monthly Visitors: Not as accurate as DAUs but gives a general ballpark.

Both metrics and the traffic as defined by other analytics tools and trackers such as Google Analytics will differ from the traffic seen in Osano.

What if I see differences in Osano and other applications?

There are a handful of reasons you may see a traffic variance, including but not limited to:

• Differences in the definition of "traffic" between tools. See above for Osano definition.

• Low to medium opt-in rates. When Osano is enabled, there will be certain locations where analytics trackers are turned OFF by default based on privacy laws. Because of this, tracking of those users will not occur in your analytics tools which can cause traffic numbers to appear lower than they do in Osano. Depending on your analytics tool(s) of choice, there may be options available to fill in some of these data gaps (ex. Google consent mode) but note that, due to the nature of compliance, analytics tracking will be affected by opt-out rates.

• The overall Osano account may be managing domains that are not reflected in the applicable Analytics Tool. Total traffic for the Osano account measures traffic from across all managed domains.

• Load testing or unit testing occurred in your production site that inflated your traffic count.

• Bot traffic that may have been excluded from internal reporting may have occurred in your production site that inflated your traffic count.

Are there ways to reduce my Osano traffic counts?

• In some cases, yes, but traffic growth is also a natural result of increased site usage.

• Osano pricing is based on traffic, which is measured by each individual download of the Osano JavaScript and counts visitors rather than sessions. As Osano is typically implemented at the root level of a domain, traffic from all environments where Osano is installed will be included in the traffic count. This includes production, non-production, staging, QA, and automated testing environments. Osano does not differentiate between production and non-production traffic.

If you are seeing unexpectedly high traffic that may impact pricing, there may be opportunities to reduce unnecessary volume:

• Non-production environments

• If Osano is installed on staging, QA, or other pre-production environments that receive significant automated or internal traffic, removing Osano from those environments can reduce overall traffic counts.

• Automated testing

• Automated tests that repeatedly load pages will trigger Osano script downloads and contribute to traffic. Adjusting test configurations or excluding Osano from those environments may help reduce traffic.