Product telemetry is the data a product records about actions and system behavior. Product analytics uses that data to answer questions about how people use the product and where they reach or miss important outcomes. Data can come from the interface, backend services, or both.
What belongs in a tracking plan?
Start with a decision. To learn whether new accounts send their first invoice, identify the events needed to measure that outcome. For each event, document its name, exact trigger, source, required properties, and owner. Choose an identifier and timestamp that let you link related events and count at the right level.
Example of an invoice tracking plan
| Event | Trigger and source | What it tells you |
|---|---|---|
| Account Created | The backend successfully creates an account | When the account enters the signup cohort |
| Invoice Preview Opened | The interface displays the preview | Whether someone saw the preview |
| Invoice Sent | The sending service records a successful send | Whether the account reached the activation milestone |
In this example, the tracking plan uses an account identifier to join signup and sending. The send event includes an invoice ID and a test flag. Use a stable event ID to deduplicate repeated delivery of the same event. In this product, a successful send means the provider accepted the message for delivery. Delivery, payment, and a click on “Send” are separate signals.
How do you check the data before using it?
- Verify the trigger. Run a successful send, a failed send, and a test send. Check that only a qualifying real send counts toward activation.
- Check repeated events. Retry the same operation and check how the event pipeline handles duplicates. For activation, count each eligible account once within the seven-day window.
- Reconcile a sample. Compare the analytics events with the product records and investigate mismatched counts, missing IDs, and delayed events.
- Limit what you collect. Use the properties needed for the analysis. Invoice content and recipient details can stay out of this tracking plan.
A sequence of preview and send events can show how often accounts continue after seeing the preview. To find out why, observe users trying to send an invoice or ask about the decision they made at that step.