Skip to main content
A meaningful event name describes what happened. Choose an action you can verify, and send it at the point that proves the outcome you want to measure.

​
Before adding events

Complete website installation and confirm the first event. Choose the website and test or production environment you intend to inspect. Events are sent only when the visitor has allowed analytics.

​
Track a custom action

  1. Open Websites, select the site, then open Events.
  2. Expand Need to track a new action? and enter a New event name. Use 2–64 lowercase letters, numbers, or underscores, starting with a letter. Use a custom name rather than a reserved system or confirmed-revenue event.
  3. For a button or link, use the supplied Track a button or link instruction. For a successful form submission, use Track a successful form submission in the form’s success callback after the server confirms success.
  4. Give the supplied instruction to your website developer or installation agent, then publish the change.
  5. Allow analytics on the website and perform the action once. Refresh the event report and confirm that the expected name was received in the intended period.
For example, booking_click measures interest in opening the booking flow. It does not prove the visitor completed a booking. A submit-button click similarly does not prove that a lead form succeeded.

​
Goals and revenue

Open Conversion goals in Events to analyze received events. Check that each step describes the same action throughout your report; renaming a click as a lead does not make it a confirmed submission. Confirmed lead outcomes, paid orders, refunds, and subscription outcomes require the supported outcome or commerce source and its proof. Do not emit a reserved paid-revenue event from a browser just to make a chart populate. Open Confirmed revenue in Events and read its source, currency, and coverage.

​
If the event is missing

Check that the code was published, the action actually reached its success point, consent was allowed, and the environment and period match the report. If a name is rejected, use a permitted custom event rather than bypassing the validation. Next: Test event destinations.