Cold IndexTracking you can trust again. Start with a $400 Diagnostic.
A written review of your events: duplicate and drifting names, broken properties, and tags that double-count or miss. We cover Amplitude, Mixpanel, PostHog, Heap and Segment, plus GA4, GTM and Meta Pixel/CAPI on Shopify, WooCommerce and custom stores. You get a ranked fix list with evidence and a clear answer on whether a bigger audit is worth it. Invoiced after delivery, so you only pay once you've read it.
- Send read-only access or an export: a viewer seat, or a file of event and property names. Nothing is changed in your tools.
- Get a written report in 10 business days: ranked fix list with evidence, and a clear yes/no on a bigger audit.
- Invoice after delivery: for the $400 Diagnostic you pay once you have read it (due in 14 days). NDA on request.
Tools we check: Amplitude · Mixpanel · PostHog · Heap · Segment · GA4 · GTM · Meta Pixel/CAPI · Shopify · WooCommerce
Sound familiar?
Tracking problems pile up quietly: a new SDK, a rename nobody finished, a theme update that duplicated the purchase tag. Then a dashboard disagrees with itself, or with your ad platform.
"Which sign-up event is the real one?"
Sign Up, signup_completed and user_signed_up all fire, and every chart picks a different one.
"We just migrated"
You moved to Amplitude, Mixpanel or PostHog and carried the old mess across, or the old names still fire next to the new ones.
"Nobody owns the tracking plan"
The spreadsheet stopped matching production months ago, and analysts spend their week cleaning data instead of answering questions.
What the audit checks
Every distinct event name in scope, its properties and the values they carry, plus the tags that send them. Read-only throughout.
Duplicates and drift
- The same action under several spellings or casings
- Near-matches that should stay separate
- Renames that left the old name still firing
Keys and types
- One key under two spellings (
plan_type/planType) - Type conflicts: numbers sent as strings, booleans as text
- Required fields missing on key events
Value hygiene
- One value under many spellings (
US·U.S.·us) - Free text and IDs leaking into fields meant for categories
- Personal data in event properties that shouldn't be there
Dead and noisy events
- Events nobody has queried, or that stopped firing
- High-volume noise crowding out what matters
- Gaps in key funnels: sign-up, activation, upgrade
Tool setup
- Merged, hidden or blocked events and how they skew charts
- Identity: anonymous vs known users, duplicate profiles
- Client vs server sources sending the same event twice
Tracking plan vs reality
- What your plan or schema says compared with what actually arrives
- A naming convention that fits how your team works
- Old-to-new mapping so history stays usable
GA4, GTM and Meta
- Ecommerce events (view_item, add_to_cart, purchase) firing once, with the right values
- Meta Pixel and CAPI event IDs deduplicating
- GTM tags, triggers and consent mode behaving as intended
What you get
A ranked fix list
Every finding has a severity, the evidence, why it matters to your numbers, and a specific fix. High-impact items come first so engineering knows where to start.
A clean tracking plan
Proposed event and property names, with every old spelling mapped to its new name, as a spreadsheet your team can adopt and maintain.
A plain-English summary
A short write-up for product, marketing and leadership: what's broken, which reports it affects, and what changes after the fixes ship.
Audit only, by design
We don't change anything in your tools or code. Your team ships the fixes, with written answers to one round of questions.
Worked examples
Public teardowns of the method on demo data, so you can see the kind of finding and fix you'd get before you book.
The basic naming pass
Collapsing duplicate event names into one convention, with an old-to-new map.
Renaming with an effective date
How to rename events without breaking historical charts.
Required fields
Catching events that arrive without the properties that make them usable.
Want to look first on your own? Taxon is a free tool that groups duplicate event names from an export, right in your browser. The audit goes further: properties, values, platform setup and a tracking plan your team can keep.
Price
For GA4/Meta sites, count the distinct events your tags send. Most people start with the Diagnostic. Bigger setups move to an Audit or Estate, fixed by the number of distinct event names in scope. Nothing hourly, and the scope is confirmed in writing before work starts.
Diagnostic
Up to 40 distinct event names
- Names, properties and values for up to 40 events: a small product's whole taxonomy, or your 40 most important events
- Ranked fix list with evidence
- Clear recommendation on whether a full audit is worth it
- $400 credited toward an Audit or Estate booked within 30 days
Audit
41–150 distinct event names
- Everything on this page, across all events in scope
- Ranked fix list and plain-English summary
- Clean tracking plan with old-to-new mapping
- Naming guide your team can follow going forward
- Decision log explaining why each event was merged, renamed or kept
- One round of written questions
Estate
151–400 distinct event names
- Everything in the Audit, including the naming guide and decision log
- Findings grouped by product area or team
- Phased cleanup order for the tracking plan
- dbt/SQL mapping from old event names to new ones for your warehouse
- Written re-check 30 days after your team implements the fixes
- One round of written questions
More than 400 event names, or two or more analytics platforms? Email us for a fixed quote. All tiers are delivered within 10 business days and invoiced by email.
Payment terms. Diagnostic: invoiced after delivery, due in 14 days. Audit and Estate: 50% invoiced upfront to book your slot, 50% on delivery, each due in 14 days.
Also available
Consent tracking check
One site, fixed price, invoiced after delivery
- Whether your cookie banner actually controls your GA4, Google Ads and Meta tags
- Whether Google Consent Mode v2 signals (ad_storage, analytics_storage, ad_user_data, ad_personalization) are set by default and update when a visitor accepts or rejects
- Whether any tags fire before consent
- Whether visitors who reject still send data
- One written report with each finding and the specific fix, plus one round of written questions
- Delivered within 10 business days; extras are $75/hr, and the $750 Fix package can be added
This is a technical check, not legal advice.
Email to bookLaunch tracking check
One site, fixed price, invoiced after delivery
- Before a redesign or platform move goes live, we check on staging that your conversions still fire correctly
- Whether your ad pixels (such as the Meta Pixel and Google Ads) and analytics events still fire
- Whether consent behaviour still works as before
- One written pass/fail list, written only and no calls
- Delivered within 10 business days
Book at least two weeks before launch; needs staging access.
Email to bookFix package
Fixed price, after any audit
- We implement the top fixes your report finds
- You give us edit access to the tool involved (your analytics platform, GA4, GTM or ad pixel)
- One round of written fixes after you review the changes
- No ongoing support and no calls; anything beyond the agreed fixes is $75/hr
Monthly tracking check
Cancel anytime
- Once a month we re-run the audit checks
- A written report of what broke or drifted, delivered within a 5-business-day window
- Includes up to 1 hour of written fixes; extras are $75/hr
- No response-time promise and no calls
How it works
- Email to bookTell us which platform you use (or your site URL for GA4/Meta), roughly how many event names you have, and what's prompting the audit. We confirm scope and price in writing.
- Read-only accessA viewer seat on the project or GA4 property, read access to GTM, or an export of your event and property list if you'd rather not grant access.
- AuditWithin 10 business days you get the fix list, the summary and the tracking plan.
- QuestionsSend questions after you've read it and we answer them in writing.
Questions
How do I count distinct event names?
Most tools list them under events or data management. A rough number is fine; we confirm the exact count before quoting, and you're never moved up a tier without agreeing to it first.
How does the Diagnostic credit work?
If you book an Audit or Estate within 30 days of receiving the Diagnostic, the $400 comes off the price.
Which platforms do you cover?
Amplitude, Mixpanel, PostHog, Heap and Segment, plus event tables in a warehouse. On the web side: GA4, Google Tag Manager, and the Meta Pixel and Conversions API, on Shopify, WooCommerce or custom sites. If you use something else, ask before booking.
Do you fix the tracking too?
The audit itself is audit only. Each finding comes with a specific fix and the tracking plan your engineers can implement, and the Estate's dbt/SQL mapping is a file your team runs in your own warehouse. If you'd rather we make the changes, add the $750 Fix package after any audit: you give us edit access and we implement the top fixes from your report, with one round of written fixes. Without it, nobody outside your team touches your tools or code.
What about our data and confidentiality?
We work read-only, or from an export of names and properties without user-level data. NDA on request. We'll sign yours, and we don't name clients anywhere.
How does payment work?
You'll get an invoice by email for the fixed price. The $400 Diagnostic, the $400 Consent tracking check and the $400 Launch tracking check are invoiced after delivery. The $2,000 Audit and $4,500 Estate are invoiced 50% upfront to book your slot and 50% on delivery. The $750 Fix package is fixed price and the Monthly tracking check is a flat $300/month; only work beyond the agreed scope is billed, at $75/hr. All prices are in US dollars (USD). See the terms.
What does the Consent tracking check cover?
For one site, we load it as a new visitor, accept, and reject, and record what your GA4, Google Ads and Meta tags send in each case. We check that Google Consent Mode v2 defaults are set before any tag fires and update on the visitor's choice, and that the Meta Pixel waits for consent. With Google's advanced consent mode, some cookieless pings after a reject are expected; we flag them separately from tags that ignore the banner. This is a technical check, not legal advice.
When do the 10 business days start?
When access is granted or the export arrives. We confirm the delivery date in writing at that point.
Start with the Diagnostic
Email hello@coldindex.net with your platform, a rough event count and what's bothering you about the data. We reply with confirmed scope and next steps.