# Name the action before you tag the button > Build a simple plan for website analytics events on forms, bookings, purchases, and useful engagement so reports answer business questions. Source: https://scayverstaging.1wp.site/resources/site-operations/analytics-event-naming/ ![A hand rests on a computer mouse placed on a white desk.](https://scayverstaging.1wp.site/wp-content/uploads/2026/09/sg-resources-146862-hero.webp) Website analytics events should describe meaningful behavior that helps your team make a decision, so start with the business question before you name any event. [Talk to a Specialist](https://scayverstaging.1wp.site/talk-to-a-specialist/?form=book) [Every resource](https://scayverstaging.1wp.site/resources/) **Format** [Guide](https://scayverstaging.1wp.site/resources/type/guide/) **In this format** 92 ## Which actions matter to the business? A name such as `button_click_7` says little about whether someone submitted an inquiry or reached a confirmation. Once the question is clear, name the event and its useful context. Identify the primary conversion first. It may be a completed proposal request, paid order, or confirmed booking. Then list the steps that help diagnose where that path breaks. A view of the contact page, a form start, a validation error, and a successful submission tell different stories. Do not mark every click as a conversion. If the site serves several services, decide whether one event name can cover the same action while a parameter identifies the service. This keeps reports comparable without inventing a new event for every page. Google Analytics provides [recommended events](https://developers.google.com/analytics/devguides/collection/ga4/reference/recommended-events) for common actions. Check those before creating custom names in that platform. ## What should website analytics events record? For each event, document the trigger, page or component, parameters, and the question it will answer. A form success event might include the form type and service category, but it should not contain the visitor’s free-text message or personal contact details. Event data should help analysis without copying private submissions into an analytics system. Use one naming convention and keep it in a shared measurement plan. Define what counts as a successful action. A submit-button click may happen even when validation fails. If the business wants to count inquiries, fire the event after the website confirms the request reached its intended system or safe storage. ## How will you avoid duplicate or misleading counts? Test whether the event fires on a page refresh, repeated button press, or back-button visit. For purchases, tie reporting to an authoritative order or payment state and preserve the transaction identifier the platform expects. If a visitor can submit several distinct inquiries, decide whether the report counts submissions, people, or qualified opportunities. Those are not the same metric. Google’s [event setup documentation](https://developers.google.com/analytics/devguides/collection/ga4/events) explains the mechanics of recommended and custom events. The implementation still needs your definitions. A technically valid tag can report the wrong business event. ## Who will use the report? Assign each metric a reader and a decision. A marketing lead may compare landing pages. A sales owner may need to know whether requests reach the CRM. A site maintainer may watch errors. If no one will act on an event, reconsider collecting it. A shorter measurement plan is easier to validate and maintain. Review events when forms, navigation, checkout, or consent behavior changes. A redesigned button may move while the old tag keeps firing in an unexpected place. Keep the plan tied to the current website, not an old implementation note. ## Write success conditions before tag names. List one primary conversion and three supporting actions. Write their success conditions in plain language before choosing tag names. [Analytics dashboards](https://scayverstaging.1wp.site/services/optimization/analytics-dashboards/) can connect validated events to decision-ready reporting. [Talk to a Specialist](https://scayverstaging.1wp.site/talk-to-a-specialist/) to build a measurement plan around what your team actually needs to know. [Explore the site-operations guides](https://scayverstaging.1wp.site/resources/site-operations/). Guides ## Guides beside Name the action before you tag the button. 1. ### [Define the website before you price the build](https://scayverstaging.1wp.site/resources/site-operations/website-requirements-checklist/) Site operations · 4 min read 2. ### [Choose a CMS around the work your team does](https://scayverstaging.1wp.site/resources/site-operations/choosing-a-cms/) Site operations · 3 min read 3. ### [Use the smallest build that solves the real problem](https://scayverstaging.1wp.site/resources/site-operations/plugin-vs-custom-development/) 4. ### [Map the handoff between tools before you automate it](https://scayverstaging.1wp.site/resources/site-operations/integration-data-map/) 5. ### [Check the dependency before it becomes invisible](https://scayverstaging.1wp.site/resources/site-operations/api-vendor-due-diligence/) 6. ### [Plan checkout as a business process, not a button](https://scayverstaging.1wp.site/resources/site-operations/checkout-flow-planning/) 7. ### [Give the product catalog a structure that can grow](https://scayverstaging.1wp.site/resources/site-operations/ecommerce-catalog-structure/) 8. ### [Decide the order rules before you configure checkout](https://scayverstaging.1wp.site/resources/site-operations/shipping-and-tax-workflow/) 9. ### [Make the return path clear before someone needs it](https://scayverstaging.1wp.site/resources/site-operations/returns-content-structure/) 10. ### [Define access rules before the member dashboard](https://scayverstaging.1wp.site/resources/site-operations/membership-access-model/) 11. ### [Design the learning workflow before choosing the LMS](https://scayverstaging.1wp.site/resources/site-operations/lms-delivery-requirements/) 12. ### [Ask for what the appointment actually needs](https://scayverstaging.1wp.site/resources/site-operations/appointment-booking-fields/) 13. ### [Make website leads usable inside the CRM](https://scayverstaging.1wp.site/resources/site-operations/crm-field-mapping/) 14. ### [Stop form spam without punishing real visitors](https://scayverstaging.1wp.site/resources/site-operations/form-spam-and-privacy/) 15. ### [Every automation needs an owner when it stops](https://scayverstaging.1wp.site/resources/site-operations/automation-failure-handling/) 16. ### [Give the chatbot a smaller, trustworthy job](https://scayverstaging.1wp.site/resources/site-operations/ai-chatbot-knowledge-boundaries/) 17. ### [The handoff is part of the answer](https://scayverstaging.1wp.site/resources/site-operations/ai-human-handoff/) 18. ### [Test the conversion, not just the dashboard](https://scayverstaging.1wp.site/resources/site-operations/conversion-event-validation/) 19. ### [Make measurement follow the choice a visitor makes](https://scayverstaging.1wp.site/resources/site-operations/consent-and-analytics-planning/) 20. ### [Spend page weight on things visitors can use](https://scayverstaging.1wp.site/resources/site-operations/website-performance-budget/) 21. ### [Accessibility continues every time someone publishes](https://scayverstaging.1wp.site/resources/site-operations/accessibility-content-operations/) 22. ### [Test the backup before you need it](https://scayverstaging.1wp.site/resources/site-operations/backup-restore-drill/) 23. ### [Update the plugin, then prove the journey still works](https://scayverstaging.1wp.site/resources/site-operations/plugin-update-staging/) 24. ### [An alert needs a person and a next action](https://scayverstaging.1wp.site/resources/site-operations/monitoring-ownership/) 25. ### [Know what ongoing website care actually covers](https://scayverstaging.1wp.site/resources/site-operations/website-care-scope/) 26. ### [Keep the domain and its connected services in view](https://scayverstaging.1wp.site/resources/site-operations/domain-dns-transfer/) 27. ### [Decide what to carry before you rebuild](https://scayverstaging.1wp.site/resources/site-operations/content-migration-inventory/) 28. ### [Give each old link a sensible destination](https://scayverstaging.1wp.site/resources/site-operations/redirect-mapping/) 29. ### [Decide how to reverse a bad launch before launch day](https://scayverstaging.1wp.site/resources/site-operations/website-launch-rollback/) No other guides in this group yet. Keep reading ## Read after Name the action before you tag the button. The rest of the resources, newest first. - [2 July 2026 Customer Persona Worksheet](https://scayverstaging.1wp.site/resources/customer-persona-worksheet/) - [2 July 2026 The Social Content Sprint Playbook](https://scayverstaging.1wp.site/resources/the-social-content-sprint-playbook/) - [2 July 2026 AI Prompt Pack for Blog Post Outlines](https://scayverstaging.1wp.site/resources/ai-prompt-pack-for-blog-post-outlines/) - [2 July 2026 Email Welcome Sequence Template](https://scayverstaging.1wp.site/resources/email-welcome-sequence-template/) - [2 July 2026 Website Pre Handoff QA Checklist](https://scayverstaging.1wp.site/resources/website-pre-handoff-qa-checklist/) - [2 July 2026 The SEO Content Audit Guide](https://scayverstaging.1wp.site/resources/the-seo-content-audit-guide/) - [2 July 2026 Positioning Statement Worksheet](https://scayverstaging.1wp.site/resources/positioning-statement-worksheet/) - [2 July 2026 The Client Onboarding Playbook](https://scayverstaging.1wp.site/resources/the-client-onboarding-playbook/) - [2 July 2026 AI Prompt Pack for Ad Headline Variations](https://scayverstaging.1wp.site/resources/ai-prompt-pack-for-ad-headline-variations/) - [2 July 2026 The One Page Creative Brief Template](https://scayverstaging.1wp.site/resources/the-one-page-creative-brief-template/) - [2 July 2026 Brand Launch Readiness Checklist](https://scayverstaging.1wp.site/resources/brand-launch-readiness-checklist/) - [2 July 2026 The Landing Page Teardown Guide](https://scayverstaging.1wp.site/resources/the-landing-page-teardown-guide/)