Trace · an alternative to Trackingplan, ObservePoint and Tag Inspector

Your tracking.
Worth trusting.

SiteOS Trace catches broken tracking requests, missing events and unexpected changes, with browser signals, consent and Google reports together for your team to investigate. This page compares SiteOS Trace with Trackingplan, ObservePoint and Tag Inspector on real-traffic monitoring, tag and cookie inventories, consent and Google Analytics checks, mobile apps and price.

Tracking quality
Consent & coverage
GA4 & GTM context

Start for free Read the guide

Free, with monthly credits. Monitoring, Google connections and alerts included.

Compare

SiteOS vs Trackingplan, ObservePoint & Tag Inspector

Compare how each tool finds tracking problems, explains the evidence and helps your team follow through.

SiteOS Trace, Trackingplan, ObservePoint and Tag Inspector: tracking monitoring, consent checks, evidence and the plans covering the features shown. Reviewed September 30, 2026.
Capability	SiteOS	Trackingplan	ObservePoint	Tag Inspector
Free plan	Yes	Partly	Partly	Partly
Price of the compared plan	Free	$249 / mo	Usage-based	Contact sales
Real-traffic monitoring	Yes	Yes	No	No
Tag inventory	Yes	Yes	Yes	Yes
Cookie inventory	Yes	Yes	Yes	Yes
Consent checks	Yes	Yes	Yes	Yes
Google Analytics checks	Yes	Yes	Yes	Yes
Mobile app tracking checks	No	Yes	Partly	Not verified
MCP for AI agents	Yes	Yes	Yes	Partly
Data export	Yes	Yes	Yes	Yes
One workspace with other website tools	Yes	No	No	No

YesPartly, with the condition in the notesNot offered or not documentedNot verified in the vendor’s official pages

SiteOS Trace is free, with monthly credits, and subject to sampling and evidence retention. It runs deep checks for Google Analytics, Google Ads, Meta Pixel, HubSpot and SiteOS Analytics and recognizes more than 2,000 other vendors by the hosts they load from. Its service map joins the connected GTM container, real traffic, SiteOS Cookie scans and the banner in the same Project; the Trace observer never reads cookies. With SiteOS Pulse, browser checks on pull request previews add an advisory Tracking section.

Trackingplan’s $249 / mo plan is billed annually and has a 14-day trial. Consent and cookie monitoring need its separately quoted Compliance add-on.

ObservePoint includes 100 page scans and 25 journey runs a year for free; further usage is billed annually. ObservePoint and Tag Inspector run synthetic scans, not real-traffic monitoring.

Tag Inspector is priced by custom quote and offers a free audit of up to 100 pages. Its data access needs the API Access add-on; no MCP or agent integration is documented.

Trackingplan lists MCP among its integrations on its homepage (checked 6 Oct 2026); its pricing page does not say which plan includes it.

The mobile app row was checked against each vendor’s official pages on 13 Oct 2026. ObservePoint validates apps through manual LiveConnect sessions within your contract scope; Tag Inspector’s pages do not say, so its cell is marked as not verified.

Sources · reviewed 30 Sep 2026

TrackingplanPlans Monitoring Consent AI & data MCP Mobile apps
ObservePointPlans Validation Consent Exports MCP Mobile app validation
Tag InspectorPlans Auditing Free audit

How it works

From a signal
to a verified fix.

Start with the evidence you need. Add expectations for important actions and check the result after a change.

01
Connect your evidence.
Connect GA4 or GTM for reports and configuration history. Add the browser observer for supported requests, consent signals and event diagnostics.
Choose your starting point
02
Find what needs attention.
Start with the Overview, open a grouped issue and follow its evidence. Review automatic findings and publish rules for your website’s real expectations.
Understand issues and rules
03
Close the loop.
Investigate with your agent, review the proposed fix and check fresh evidence. Route alerts and verified recoveries to your team.
Work with your team and agent

FAQ

Questions
about Trace.

Trace is free, including supported browser monitoring, GA4 and GTM connections, consent checks, rules and notifications. Sampling, evidence retention and provider coverage still apply; free access does not mean every request or integration can be observed.

Only for browser observation. GA4 reports, report-based drop monitoring and GTM configuration history work through Google connections. You can use either path independently or combine them. Request diagnostics, consent timelines and browser-versus-report comparisons need the matching observer evidence.

Deep checks cover Google Analytics, Google Ads, Meta Pixel, HubSpot and SiteOS Analytics: event names, property types and consent state per request. The observer also recognizes more than 2,000 other vendors, such as Hotjar, LinkedIn Insight, Microsoft Clarity or ZoomInfo, from the SiteOS vendor registry and the open third-party-web dataset, and shows them on one service map with your GTM tags, Cookie scans and banner. For a service it cannot recognize, Trace stores only the registrable domain, never the address it called. Data-layer events are source evidence, not proof that a destination received them.

The observer does not store raw event payloads, property values, cookies or persistent visitor IDs. New installations use strict collection with approved event names, field names and route templates. Extended and older configurations have different limits; review the collection settings for your installation. Optional personal data and ecommerce value checks read values in the browser only while a visitor allows analytics and send only the kind and place of a problem. Raw observations are deleted after seven days, and Trace can wait for analytics consent before it starts. Cookie-free observation alone is not a legal exemption.

By default the observer starts immediately, so it can see what loads before a visitor chooses and after a rejection. It sets no cookies, keeps no visitor IDs or values, and raw observations are deleted after seven days. If your policy requires consent, set Start collecting to After analytics consent: Trace then sends nothing until your consent source grants analytics. With the SiteOS Cookie banner, Trace can be listed under Analytics, so visitors see it among the services their choice covers. Whether it may run before consent is your assessment.

Trace observes consent and tracking health; your CMP still controls consent and tags. Connected GA4 and SiteOS Analytics views keep their report counts separate from browser observations. A sent request, a successful response and a counted conversion are different facts.

Trace looks for the fresh evidence required by that issue: successful request results, a healthy comparable observation window or later eligible Google reports. Resolving or snoozing an issue manually records your decision; it does not verify recovery. Low traffic, missing coverage and incomplete reports can leave the result inconclusive.

Follow every signal.
Trust the evidence.

Tracking, analytics, consent and your AI agent. One shared website workspace.

Start for free Talk to our team

Your tracking.Worth trusting.

SiteOS vs Trackingplan, ObservePoint & Tag Inspector

From a signalto a verified fix.

Connect your evidence.

Find what needs attention.

Close the loop.

Questionsabout Trace.

Is Trace free?

Do we need to install a script?

Which tracking services can it observe?

Does Trace collect event values or identify visitors?

Does Trace need a cookie banner?

Does Trace replace a cookie banner or analytics tool?

How do we know an issue is fixed?

Follow every signal.Trust the evidence.

Your tracking.
Worth trusting.

From a signal
to a verified fix.

Questions
about Trace.

Follow every signal.
Trust the evidence.