How do I create a tracking plan?

Short answer

Open All-platform analytics › Data › Tracking plan and click New event for each event you intend to collect: name, display name, category, platforms, trigger, properties (with type, required and example), owner, developer and status. Move each row from Proposed to Developing, Accepting and Live as it is built and checked. Turn on Live verification (24 h) to see whether each event is arriving and whether its required properties are filled.

A tracking plan is the agreed list of events and properties before anyone writes tracking code. It keeps names consistent across web, apps and the server and gives developers and analysts one source to check against.

Before you start

1. Start from questions, not events. List the 5–10 questions the team needs to answer (for example "Where do trial users drop off before paying?"), then the events needed to answer them.
2. Agree on naming. Use one style, such as object_action in snake_case: signup_completed, report_exported. Avoid putting values in names (clicked_blue_button); use properties instead.
3. Check what already exists. Autocapture and preset events (pageviews, screens, clicks, app starts) may already cover part of the plan.

Create plan rows

You can also Import a CSV or a previously exported JSON. Rows match on event name, and you choose whether existing rows are overwritten or skipped. In CSV, separate properties with | and mark required ones with *.

If events are already being sent, click Generate from definitions to fill the plan from existing event definitions. It does not overwrite rows that already use the same name.

Track status through delivery

Sync to definitions links plan rows to event definitions that already exist. A row marked Live marks its definition live. Event definitions themselves live on the Definitions tab of Data › Event inbox, together with events that nobody has claimed yet.

Verify events with live verification

Turn on Live verification (24 h). Two columns appear: hits in the last 24 hours and the completeness of required properties. Use them before moving a row to Live:

• No hits: the event is not firing, or the name differs from the plan.
• Low completeness: some events arrive without a required property. This is a warning only; events are not blocked.

There is no QR-code check on this page; verification is the 24-hour count. For rules that block or quarantine bad data, see property definitions and Data › Data quality.

Share the plan

Export XLSX to hand the plan to developers or attach it to a ticket. Anyone in the project can view the plan; creating, editing, importing, syncing and deleting need the Analyst role or above. Deleting a plan row does not delete the event definition or any data.

Related

• Event inbox
• Track custom events
• Data taxonomy