Enterprise DNA

Instead of Trackingplan

Stop renting Trackingplan. Own your tracking checks.

We bring your Trackingplan definitions across, build your checks around the events you rely on and run them for you. Collection connections are scoped to your systems.

Trackingplan Enterprise starts at €2,000 a month with an annual commitment, equivalent to €24,000 a year before VAT. Your quote depends on volume.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription covers

The bill follows traffic, capacity and the service you choose

Trackingplan combines collection, monitoring and an analyst service. Compare the parts your team uses with the work you want to own and have run for you.

paid

Monthly plans or an annual commitment

Starter begins at €89 a month and Growth at €699. Enterprise starts at €2,000 a month on an annual contract. These are published starting rates before VAT.

monitoring

Sessions across your sites

Tracked sessions are added across the sites and apps in your account. More traffic can mean extra usage charges.

domain

Capacity for sites and apps

The plans differ in the number of sites and apps included. Enterprise has no site-count limit.

chat

Credits for analyst work

Agent conversations, reports and audits use credits. Extra packs of 100 credits cost €100. Monitoring itself does not use those credits.

privacy_tip

Privacy and consent monitoring

The Compliance module costs €249 a month on Growth and is included in Enterprise. It covers personal-data, cookie and consent monitoring.

support_agent

Support and onboarding

Enterprise includes a named customer success manager, onboarding and training. Replacing the service means agreeing who owns that work as well as the records.

Your tracking assurance desk

Definitions, captured evidence and corrections in one place

Definitions

Keep the rules your reports depend on

Bring the exported event definitions into your own database, then review the rules before relying on them.

  • check Events grouped by destination and environment
  • check Property types and required fields brought across
  • check Daily counts and vendor warnings retained from the export
  • check Earlier rule versions kept when you make a change

Checks

Catch a broken checkout in captured evidence

Check the event samples your team supplies against the agreed rules and recorded consent policy.

  • check Missing currency and other required properties
  • check Numbers sent as text or values outside your allowed choices
  • check Unexpected fields and unfamiliar events
  • check Personal-data field names flagged for review

Release review

Know what still blocks the evidence review

Your newest captured batch is checked against the current rules, owners and open corrections.

  • check Every defined event needs a current sample
  • check Changed rules or policies require fresh validation
  • check Old or incomplete captures remain visible
  • check Open corrections keep the review blocked

The week

Put a name beside every correction

Prepare the weekly review and event paperwork from the same records your team uses to investigate problems.

  • check Overdue corrections listed with their owners
  • check Events without a purpose or retention period flagged
  • check Branded event specifications and evidence reviews
  • check Private correction drafts prepared from recorded findings

Make it yours

Design your own Trackingplan replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Trackingplan. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Trackingplan replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Trackingplan data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Three real answers from synthetic demo records: broken fields, missing policies and an overdue correction. Your own records replace these examples.

forum

Tracking Assurance for Claude Code

Connected to your own database

What is wrong with the checkout tracking we captured?

checkout-42

Destination
demo-store
Event_name
purchase
Observed_at
"2026-11-07T21:31:10.188Z"
Code
SCHEMA
Property
/value
Finding
must be number

checkout-42

Destination
demo-store
Event_name
purchase
Observed_at
"2026-11-07T21:31:10.188Z"
Code
SCHEMA
Property
/currency
Finding
required property missing

checkout-42

Destination
demo-store
Event_name
purchase
Observed_at
"2026-11-07T20:31:10.188Z"
Code
CONSENT
Finding
Consent required by local policy

checkout-42

Destination
demo-store
Event_name
purchase
Observed_at
"2026-11-07T20:31:10.188Z"
Code
PERSONAL-FIELD
Property
/email
Finding
Review personal-data field

Ask it anything

Ten questions your own tracking desk answers

These questions run against the included demo. Your records and rules shape the answers. They are not claims that Trackingplan cannot answer them.

chat_bubble Which captured checkout events fail the current property rules?
chat_bubble Which events have no evidence for their current contract revision?
chat_bubble Which captures conflict with our recorded consent policy?
chat_bubble Which property names need a personal-data review?
chat_bubble Which events have gone more than a week without captured evidence?
chat_bubble Which imported daily counts dropped or reached zero?
chat_bubble Who owns overdue tracking corrections?
chat_bubble Which event definitions have no purpose or retention period?
chat_bubble Does the latest release batch cover every current event contract?
chat_bubble Who changed the rules or recorded a correction?

Switching

How to switch from Trackingplan

A move usually means exporting one destination, reviewing its rules and history, then running your existing monitoring alongside supplied captures until the new checks are reconciled.

  1. 1

    Export one destination

    Start with one destination so you can check the move before bringing over more. Use Trackingplan’s documented CSV export or Export API JSON, then include the event definitions, property types, required fields, daily counts and warnings. If those options are not available in your account, check with Trackingplan about what you can export. Warnings or descriptions may contain sensitive information.

  2. 2

    Test the import

    Try the import’s test run before loading records. It lets you see what the import will bring across without changing the database. Check that the destination and exported records look right, and resolve any data problems first. The import accepts one destination at a time, so test each destination separately rather than treating the export as a full account migration.

  3. 3

    Load and review records

    Load the export after the test looks right, then review what the import flags. The imported event contracts require explicit review because exported type labels do not include every validation expression or allowed value from your existing rules. Compare the imported daily counts and warnings with Trackingplan, and decide which rule details need to be recorded before you rely on new checks.

  4. 4

    Run both side by side

    Keep Trackingplan running for a short parallel check while you supply captured event samples to the new desk. Compare its checks with the new desk’s results, and reconcile the events, counts and rules you need to carry forward. The open source base does not collect website traffic automatically, so make sure your capture process supplies evidence and that any required connections are in place.

  5. 5

    Switch off Trackingplan

    Turn off Trackingplan only after you have reconciled the records, rules and checks you need, and confirmed how new captured samples will reach the new desk. Decide who will review findings and maintain the rules and connections. Keep a copy of the original export with your records, since it is retained alongside the imported data and may contain sensitive details.

construction

Where the real effort goes

The main work is usually mapping your own fields and rules, then deciding how much Trackingplan history to bring over. Event definitions, property types, daily counts and warnings can come across, but detailed rule choices need review. Visitor sessions, cookie scans and notification settings need separate mapping or connections. When Enterprise DNA runs it, they map your history, add your rules and connect capture sources.

Not ready for a call?

Get your Trackingplan switch plan by email

We will send you the step-by-step plan for moving your business off Trackingplan, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Do it yourself, have it customised, or have it run for you

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo, then run npm install, npm test and npm run demo
  2. 2 Open it with Claude Code, Codex, OpenCode or Cursor
  3. 3 Export one Trackingplan destination as CSV or Export API JSON, test the import and reconcile counts
  4. 4 Review the rules, supply captured events and generate the branded checks
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your fields, event rules, consent policies and correction process
  • check Your Trackingplan exports mapped and reconciled
  • check Collection and monitoring connections built for your existing systems
  • check A web front end or a different technology stack when your team needs it
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installation, access controls and backup arrangements
  • check Agreed capture connections and checks operated for your business
  • check Weekly evidence reviews and correction drafts prepared
  • check Ongoing changes managed through Omni by Enterprise DNA
Book a 30-minute Trackingplan review

Questions

Instead of Trackingplan, answered

Does the free version watch our website automatically? expand_more

The free version checks captured event samples supplied by your team. Trackingplan also collects traffic and monitors it continuously. We scope and build the capture connections, ongoing checks and notifications your business needs into your version.

What comes across from our Trackingplan export? expand_more

One destination at a time: event definitions, property types, required fields, daily counts and warnings. The original export is kept. Detailed rule choices need review before checking new events. Visitor sessions, cookie scans and notification settings need separate mapping or connections.

Can a passing review prove that our tracking and consent are compliant? expand_more

It shows that the recorded batch met your current rules and had no open corrections. It does not establish what every visitor experienced or decide whether collection is lawful. Your responsible person sets the policy and reviews the evidence.

What does Enterprise DNA charge? expand_more

There is one setup fee, then a retainer for the ongoing work we agree. We scope your data migration, rules, connections and operating responsibilities with you. Hosting and any third-party services are discussed as part of that scope.

Can our team have screens and keep its existing tools? expand_more

Yes. We can build a web front end, connect your current testing and reporting tools, or use another technology stack. Keep your current monitoring running until the required collection and checking work has been reconciled.

Bring your Trackingplan bill and one broken event

Spend 30 minutes with Sam reviewing your annual bill, the events your business relies on and the work your team does to keep them trustworthy. We will map the records and connections your own version needs.

Book a 30-minute Trackingplan review Get the free version

Tracking Assurance for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Trackingplan?

Get your version built