Run a 100-Page Privacy Audit to see what’s really on your site.

 

It is clear data protection is a major public concern, but you can’t protect your customer’s data without a complete understanding of the cookies and tags collecting data on your website.

ObservePoint automatically scans your website to:

Identify Data Icon

Inventory all unapproved/approved cookies & technologies

Validate Functionality Icon

Test your user consent preferences and CMP functionality regularly

Reveal Information Icon

Discover what data is being tracked and where it’s being sent

Alert Icon

Ensure your cookie consent banner and privacy policy are on all pages

We will scan 100 pages from the starting URL of your choice to identify data collection technologies on those pages and alert you to some potential privacy risks on your site.

What to expect with your Privacy Audit Report:

Informational

Good

Could Use Improvement

Needs Attention

Cookie Performance & Inventory

Your Cookie Summary

Unique Cookies

1st-Party Cookies

3rd-Party Cookies

Non-Seucre Cookies1

SameSite Empty Cookies2

125

71

54

34

35

Knowing what cookies are on your site and whether or not they are secure is half the battle. ObservePoint audits and reports on this information and more: 

  • How many unique cookies are on your website
  • Whether they’re first or third-party 
  • How many are not secured 
  • Which cookies are not limited to your site

Examples From Your Site

Cookie Name Domain 1st or 3rd-Party Secure
__utmachrome.google.com3rdFalse
__cf_bmmarketo.com3rdTrue
bcookie.linkedin.com3rdtrue
_fbp.observepoint.com1stTrue
__cf_bm.zoominfo.com3rdfalse

Effectively govern cookies on your site and protect your customer data by using ObservePoint to identify and monitor:

  • A comprehensive inventory of all cookies 
  • Domains, locations, and page URLs
  • What information they are collecting 
  • Whether or not they’re secure 

Website Data Collection

Your Data Collection Summary

Unique Tags

AVG Tags/Page

CMP on Pages3

# Transfer Countries4

3rd-Party JavaScript Files5

51

15

72%

3

13

Cookies aren’t the only thing you need to monitor. You have dozens of technologies (tags) or JavaScript files collecting and transferring data from your site, and consent management platforms (CMPs) aren't foolproof. ObservePoint audits and monitors:

  • All data collection tags and JS files
  • What data they are collecting 
  • Where data is being transferred
  • Your CMP implementation

Examples From Your Site

Tag Name 1st or 3rd-Party % Pages with Tag
Google Tag Manager3rd95%
Marketo3rd99%
OneTrust3rd85%
ObservePoint Data1st100%
Google Analytics 43rd45%

You can’t protect customer data without knowing the tags on your site. ObservePoint's comprehensive Audits provide a full inventory of:

  • Data collection technologies (tags)
  • Percent of pages they’re deployed on
  • Domains, locations, and page URLs
  • What data they’re collecting

Ready to see the difference ObservePoint can make for you?

  1. "Non-secure" is referring to cookies where the “secure" attribute is “false” or empty. It is recommended all approved cookies are set to “secure."
  2. If the “SameSite” attribute is blank, this means the cookie is not limited to be read by your website only and can be a privacy liability. It is recommended that this attribute is not left empty.
  3. ObservePoint audits for the most common Consent Management Platforms (CMPs) in the market. This Sample Audit will not identify proprietary consent tools or custom experiences you may have in place, but Rules can be set within ObservePoint to identify and monitor them during Audits. It is recommended (and increasingly required) that any company collecting customer data online has a consent management solution implemented.
  4. Most privacy regulations have requirements regarding the location of customer data. ObservePoint's Audits can show you where in the world the network request is originating from so you can ensure compliance.
  5. Websites rely on JavaScript to function, but accidental or intentional (but unapproved) file changes can be made by anyone with access to your codebase. These unchecked changes put your data at risk and can result in data leakage or theft. It is recommended that you keep track of these files and investigate any new or suspicious activity.