Glossary

A plain-English reference for every term TrackingCoder uses across the scanner, the wizard, and TC Pro monitoring. Skim it once and the rest of the docs read faster. Terms are grouped by area; within each group the most-used terms come first.

Core concepts

• Scan — a read-only inspection of a URL that detects what analytics and tools are already present (GA4, GTM, Meta Pixel, Google Ads, LinkedIn, MS Ads, plus 70+ third-party tools), the page's forms, and e-commerce signatures. See Site scanner.
• Scenario — an event type TrackingCoder generates code for: purchase, form_submission, add_to_cart, scroll_depth, video_engagement, phone_click, and so on. One scenario = one thing worth tracking.
• Channel — the destination a scenario's event is sent to: GA4, Meta (Pixel), Google Ads, LinkedIn, or Microsoft Ads (UET). One scenario can fan out to several channels.
• Event — a single firing of a scenario on a channel (e.g. one purchase → GA4). Monitoring counts events; the count is what every Pro metric is built on.
• Discovery wizard — the guided flow that turns a scan into the right code by asking only the questions that matter for the scenarios you picked. See Discovery wizard.
• Output format — how generated code is delivered: a GTM container import, a GTM Custom HTML tag, or a direct <script>. See Output formats.
• ID Vault — an encrypted, per-domain store of your GA4 / Meta / Ads / LinkedIn IDs so you don't re-paste them on every generation. See ID Vault.
• Consent Mode v2 — Google's opt-in consent signalling for GA4 + Google Ads, which the generated code can wire up for you. See Consent Mode v2.
• Advanced parameters — extra per-event fields computed at fire time (hour_of_day, scroll_at_event, time_on_page, traffic_source, device_category, …). See Advanced parameters.

Pro monitoring metrics

• Monitoring — the TC Pro layer that counts every TrackingCoder-generated event firing on a domain, in near real-time (~1 minute), from a per-minute counter the ingest endpoint writes to. See Pro monitoring.
• Monitor container — a small GTM container (one Custom HTML tag + one trigger) you import once per domain. It catches the tc_monitor signal each TC event pushes and POSTs it to ingest.
• Co-ping — the tiny tc_monitor dataLayer signal a TrackingCoder event pushes alongside its normal channel send, so monitoring can count it. Carries only {scenario, channel, eventName} — no parameter values, no PII.
• Install-check ping — a one-off _install_check sent on the first pageview per browser session after you publish the Monitor container. It marks the domain "Verified · receiving events" and is excluded from event counts, top-events, activity, and goals. It is also the basis of the Visits metric (below).
• Visit — TC's own first-party traffic measure: ≈ one unique browser session, derived from the bot-filtered install-check ping (which fires once per session). It is not a GA4 session and is intentionally a separate, simpler number. Bots and headless agents are filtered out of the count.
• Conversion rate — events ÷ visits over the same window, shown only for conversion-type scenarios and only when visits > 0 (otherwise "—"). Engagement scenarios that fire many times per visit are excluded so the rate can't read above 100%.
• Conversion-type scenario — the scenarios counted in conversion rate: purchase, form_submission, hubspot_form_submission, begin_checkout, add_to_cart, phone_click, email_click, file_download.
• Recent fires panel — a per-event inspection modal showing the last 20 fires with a curated, no-PII set of parameter values (pathname, device, source, scroll %, time on page). Opened from the "View details →" link on any event row.
• Activity chart — the detail-page chart showing the events line plus a dimmer grey visits line (toggleable), with modes to view all events combined, split one line per event, or isolate a single event on a shared scale.
• Baseline — a scenario's trailing 14-day average (excluding today and the install-check), used by the anomaly cron to judge drops and spikes. Needs ≥5 days of history before it can fire volume alerts.

Goals & performance scoring

• Goal — a per-scenario target: a count, a period (weekly / monthly / quarterly, calendar-aligned), a type, and a weight. See Event goals.
• Goal type — minimum ("at least N", the common one), target ("exactly N"), or maximum ("at most N", for error/abuse caps).
• Weight — how much a goal counts toward the Performance score. Default 1; raise it to bias the score toward the goals that matter (e.g. purchase over newsletter signup).
• Performance score — a 0–100 weighted average of every goal's completion, per domain and per workspace. Thresholds: 80+ green, 50–79 yellow, under 50 red. Domains without goals are excluded from the workspace average.
• Goal status — the per-goal state shown on each row: On track, Behind, Off pace, Met, or Exceeded, with an on-pace projection for the period.

Alerts & active probes

A nightly cron compares each scenario's last 24h against its baseline and raises typed alerts. See Anomaly alerts.

• volume_drop — fired today but <50% of the 14-day average. Warning.
• volume_spike — >3× the baseline. Info.
• dod_spike — today > 5× yesterday. Info.
• no_activity — an established scenario fired 0 events today. Warning (often a broken selector or bad GTM publish).
• new_scenario — a scenario's first-ever events arrived today. Info (handy for confirming a new install).
• probe_failed — the active probe hit a hard failure 3 runs in a row. Critical.
• goal_achieved — a minimum goal hit its target this period. Info (positive).
• Active probe — a scheduled headless load of your site that checks the Monitor tag + dataLayer are actually present, catching silent breakages even when no events are firing. Three consecutive failures raise a probe_failed alert; a passing run auto-resolves it.
• Alert lifecycle — open → muted (7-day snooze) or resolved. Open alerts don't duplicate (one per org·domain·scenario·channel·type); most auto-resolve when the condition clears.
• Quiet hours — a per-user window during which email alerts are deferred rather than sent. Email is opt-in; in-app is always on.

Credits & regeneration

• Credit — the unit spent to generate tracking code, 1 per event. New accounts get free codes; more come from packs or the monthly Pro allowance. See Credits & pricing.
• Backfill — bringing tracking code that was generated before the Monitor co-ping existed into monitoring, by regenerating it. Listed at /dashboard/monitoring/backfill. See Free regeneration backfill.
• Free regeneration — regenerating a pre-co-ping scenario at zero credit cost (recorded as an amount-0 [Free Regen] transaction). A TC Pro benefit.
• Regeneration waiver — the single-use token that authorises one free regen for one specific scenario/channel. It can't be redirected to a different scenario, replayed, or used across orgs — those all charge normally.
• Re-import — publishing the regenerated container into GTM. The next live event flips the backfill queue row to reimported and the scenario drops off the backfill list.

Workspace, branding & reports

• Workspace (Org) — the team container that owns domains, the shared ID Vault, generated codes, and the monitoring pool. Includes the credit pool and branding. See Workspace & branding.
• Branding / white-label — your brand name, logo, and accent colour, applied to the in-dashboard chrome (co-brand) and to client reports.
• Client report — a print-to-PDF, white-label deliverable per domain: summary stats (events, visits, scenarios, performance score), top events with conversion rate, goal progress, and a daily-volume chart with a visits reference line. See Branded client reports.
• Quota — TC Pro includes 20 monitored domains and 250 scenarios across the workspace.

Account & billing

• 14-day trial — a no-card Pro trial with every feature unlocked; it auto-cancels cleanly if no card is added by day 14. See 14-day free trial.
• Early-adopter price — the discounted Pro price locked in for life if you subscribe before 31 August 2026.
• Affiliate / referral — share an /a/<code> link to earn recurring commission on Pro subscriptions and a percentage of credit-pack purchases from people you refer. See the Partners page.