Marketing Strategy & OperationsTemplate3 min readUpdated September 2026

Event Tracking Plan: The Columns, Naming Rules and a Worked Example

An event tracking plan is a spreadsheet that lists every customer action you record, what each one is called, when it fires and what details travel with it. Build one before you add tags, and every downstream report, audience and attribution model gets easier to trust.

The outline below gives you the columns, a naming rule that holds up over time, and a filled-in example for a B2B signup funnel.

Vendors Covered in this Article

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Which columns does a tracking plan need?

Keep the sheet to one row per event and these columns:

  • Event name: the exact string sent to your analytics or data tool.
  • Trigger: the user action or system condition that fires it, in plain language.
  • Properties: the extra fields sent with it, such as plan name, form ID or page category.
  • Where it fires: web, app, server or a partner tool.
  • Destinations: which tools receive it, such as analytics, ad platforms, CRM or email.
  • Owner: the person who answers questions and approves changes.
  • Status: planned, live, needs QA or retired.

Add a notes column for edge cases. The owner column matters more than it looks: unowned events drift, duplicate and break silently.

How should you name events and properties?

Pick one convention and write it at the top of the sheet. A reliable pattern is an object followed by a past-tense action, in title case: Form Submitted, Trial Started, Invoice Paid. Properties use lowercase with underscores: plan_name, form_id, page_category.

Rules that prevent most cleanup work later:

  1. Name the action from the customer's perspective, not the button's label. A button label will change, but the action won't.
  2. Use one event with a property instead of many similar events. One Form Submitted event with a form_id property beats separate events for each form.
  3. Never put a value in the name. Plan_Upgrade_Pro should be Plan Upgraded with plan_name set to pro.
  4. Keep the same property name and format across every event. Don't use both plan and plan_name.

What does a worked example look like for a B2B signup funnel?

Say you sell a software product with a free trial and a sales-assisted upgrade. A first pass of the plan might list these rows:

  1. Page Viewed fires on every page load, with properties page_path and page_category.
  2. Form Submitted fires when a lead form is completed, with form_id, form_type (demo, contact, newsletter) and lead source.
  3. Account Created fires server-side when a workspace is created, with plan_name and signup_method.
  4. Trial Activated fires when the user completes the first key action, such as connecting an integration.
  5. Upgrade Requested fires when someone asks for pricing or sales contact.
  6. Subscription Started fires server-side from your billing system, with plan_name and billing_interval.

Six events can answer most funnel questions. Resist adding more until a decision depends on them.

How do you decide what to track, and what to skip?

Start from the decisions you'll make, not from what's technically possible. For each candidate event, write the question it answers and the action you'd take differently based on the answer. If you can't finish that sentence, leave the event out for now.

Prefer events that mark a step toward revenue: leads created, activation, purchase, renewal. Track clicks and scrolls only when a specific page test needs them. Server-side events, sent from your backend rather than the browser, are more reliable for purchases and signups because ad blockers and closed tabs can't drop them.

How to keep the plan accurate after launch

A plan goes stale fast unless someone checks it against reality. Once a quarter, compare the plan against what your analytics tool actually receives: look for events that fire but aren't listed, listed events that never fire, and properties that arrive empty. If you use a customer data platform such as Segment or RudderStack, its schema and debugging views can flag mismatches, and the CDP comparison explains how they differ.

Tie the plan into your reporting. The attribution report template and account-based metrics dashboard both depend on clean event definitions, so a change to the plan should be announced to whoever builds those reports.

Executive Capability Standard

What Good Looks Like

A good tracking plan names every event in one consistent pattern, lists its trigger, properties and owner, and is checked against live data on a schedule.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Learn the difference between events and properties, and list the funnel steps that lead to revenue.
2. Do Manually:Build the plan in a spreadsheet and check each event by hand in your analytics debugger.
3. Delegate:Give a marketing operations owner approval rights over new events and a quarterly audit.
4. Automate:Enforce the plan with schema validation so events that don't match are flagged before reaching reports.
5. Buy:Adopt a customer data platform once many tools need the same events and manual upkeep costs more than the subscription.

How to Get Started

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Frequently Asked Questions

What is an event tracking plan?

It's a document, usually a spreadsheet, that lists every user action you track, its exact name, when it fires, what properties it carries and who owns it. It keeps analytics data consistent across your team and tools.

How many events should a small company track?

Start with roughly ten to twenty tied to funnel steps and revenue. More events means more upkeep and more chances for errors. Add new ones only when a specific decision needs the data.

Should events be tracked in the browser or on the server?

Use both. Browser events suit page and click behavior, while server events suit signups, purchases and renewals because they aren't lost to ad blockers or closed tabs. Note the source of each event in your plan.

Who should own the tracking plan?

One named person, usually in marketing operations or analytics, should approve changes. Individual events can have their own owners, but a single steward keeps naming and properties consistent.

About the numbers

This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.

Related Guides