Custom event analytics for product actions

Tracwell custom events record actions your application chooses to measure, such as a completed signup or created checkout. Properties add context for filtering and breakdowns without turning each property into a separate event.

Name the action and capture useful context

Use stable names such as signup_completed or checkout_started. Include a small set of relevant properties, such as a plan code or signup method. Do not send passwords, secrets, or unnecessary personal information.

Use the source that can confirm the outcome

Browser events work for frontend interactions. Use authenticated server events for backend-confirmed actions. Purchases and refunds use the server revenue API; a checkout button click is not proof that a payment succeeded.

Measure use of a new product action

Example workflow

  1. Choose a stable event name and define when the action has succeeded.
  2. Send the event once at that success boundary with relevant properties.
  3. Inspect the event and its properties in Tracwell.
  4. Use the event in a goal or funnel when you want to measure an outcome or sequence.
Install custom event tracking

What to keep in mind

Only instrumented actions appear as custom events. Automatic page views do not infer form completion or purchases. Consent, Do Not Track, origin validation, and payload limits can prevent collection; inspect delivery results when verifying installation.

Do properties multiply the billable event count?

No. Properties add context to an event. Billing counts events successfully persisted, and retrying the same stable event ID does not create an additional billable event.

Explore the connected reports

Start with your website

Connect Tracwell and verify your first event before building reports around it.