A campaign report can show an enquiry number without explaining what caused it. Was the event triggered when someone clicked a button, when the form passed validation, or when the team actually received the request? Agree that definition before using the number to assess sports, casino or poker content activity.
This guide proposes acceptance tests for the measurement handover. It is separate from choosing campaign-link names: UTM conventions describe incoming links, while the tests below describe the actions recorded after a visitor arrives.
Write the business meaning in plain language
Begin with a sentence such as “The enquiry event represents a successfully accepted shortlist request.” Ask the developer and sales owner what “accepted” means in this particular system. A request stored in the enquiry system may still have a delivery problem in the notification email, so record those two checks separately.
Use a distinct description for opening an email link or starting a chat. Those interactions may be useful, but they do not prove that a person sent a message or that a salesperson received it. A report should retain the distinction instead of adding unlike actions into an unexplained total.
Agree the event design with the implementer
Google's event documentation describes events as measurements of interactions and provides recommended and custom event routes. It also identifies Realtime and DebugView as places to inspect events and their parameters. Ask the implementer which event fits the requirement rather than inventing a new name without checking the existing setup.
List any necessary parameters, such as an approved form identifier or enquiry route. Keep private form content, email addresses, customer names and article briefs out of this proposed event specification. The report needs a meaningful action definition, not a copy of the prospect's message.
Test failures as well as successes
Prepare cases for an untouched form, a missing required field, a corrected validation error, a successful submission and an accidental double click. Add a case for refreshing or revisiting the confirmation screen. For each case, state the expected event behaviour before testing begins.
Run the test on the relevant mobile and desktop routes. Clearly mark internal enquiries so they are not mistaken for prospects. The reviewer should check the application result, the received enquiry and the analytics observation, then record which of those were actually inspected.
Illustrative example: a button click counted too early
Illustrative example: a buyer clicks “Request shortlist” with the email field empty. The page rejects the form, but an event already fires on the button click. The test fails because the business definition requires a successfully accepted request. The implementer changes the trigger and repeats both the failure and success cases.
This does not establish campaign attribution or sales value by itself. It establishes that the event behaves as specified in the tested journey. Record any untested consent, browser or delivery conditions rather than assuming they work identically.
Include the definition in reporting
Attach a short event dictionary and checked date to the reporting handover. When the form changes, rerun the affected tests. When the business definition changes, annotate the reporting period so a higher count is not automatically presented as better performance.
Bring measurement requirements into the placement brief, select appropriate audiences from the publisher inventory, and define separate enquiry paths for any article promo video activity before reporting the results together.
Sources and further reading
Sources checked 26 October 2026.