Questions about trackers and the cookie consent box
What loads on a page before a site visitor presses anything, and what happens after.
- Google Tag Manager0.266s
- Facebook pixel0.530s
- Microsoft Clarity0.533s
- ActiveCampaign0.533s
- Cookie consent box0.534s
- Google Ads0.536s
- Google Analytics 40.672s
How TrackGuard Pro works
What is TrackGuard Pro?
An independent third party that checks and records what loads on public pages before a site visitor presses anything on the cookie consent box. Every check is dated and kept as evidence. You decide. We verify.
Who makes the changes on my site?
Your web team, developer or agency. Once they have made a change, we check the page again and record the result with a date. Keeping the check separate from the work is what makes the record worth showing to anyone else.
What can I do about a tracker you find?
Five choices, every time: remove it, gate it behind consent, move it off that page, keep it with a written reason, or accept it as it is. On Proof, each choice is logged with who made it and when, and the next check confirms it.
Does a tracker on my site mean something is wrong?
Not on its own. We flag each tracker for review and list the rules it is commonly raised under. What a finding means for your business is a question for your lawyer.
How do I know a finding is real?
Each check comes from a real page load. It records the page address, the time each tracker loaded to the thousandth of a second, and an evidence digest: a fingerprint of the raw record. Change one character in the record and the digest no longer matches.
Who sees my report?
You do. Your report is private and sent only to you, and each one carries its own date and evidence digest.
How do you confirm I own the site?
One of four ways: an email to an address at your domain, a DNS record, a file uploaded to your site, or a code sent through your own contact form.
Rules that come up
Which rules come up with website trackers?
Commonly raised under: the California Invasion of Privacy Act (Penal Code §631 and §638.51), the California Consumer Privacy Act, and on payment pages, PCI DSS 4.0.1 Requirements 6.4.3 and 11.6.1.
What do PCI DSS 6.4.3 and 11.6.1 ask for on payment pages?
6.4.3 asks for a list of every script on a payment page, with a reason for each and a record that it was authorized. 11.6.1 asks for a way to spot changes to those scripts and the page headers, at least once a week. Both have applied since March 31, 2025. Proof checks payment pages every week and keeps the dated record.
Plans and billing
Can I try it before paying?
Yes. The free check looks at one page, once, with no card. Request a free check.
What is the difference between Watch and Proof?
Watch ($99/mo) checks your key page types every week and runs the After-Reject test. Proof ($499/mo) checks every page type, including payment pages, every week, and adds a screen recording, a dated decision record, and the rule each tracker is commonly raised under.
Why page types and not a page count?
A tracker is usually added once and shows up on every page built from the same template. Checking each type of page, such as product, checkout, form and article pages, catches it where it matters.
Is there a free trial?
Watch and Proof start with 14 days free. The first charge comes on day 15. Cancel before then and nothing is charged.
Can I cancel any time?
Yes. Watch and Proof are month to month.
I have five or more sites.
Enterprise covers five or more sites, checked daily. Email [email protected].