Prompt Almanac

Create intermediate Works with: ChatGPT, Gemini, Claude

Google Analytics Measurement Plan and Event Naming Convention

Table output Needs web browsing Has example

Decide what to measure before configuring tags.

Open in ChatGPTOpen in Claude

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.

Rate this prompt

Loading ratings…

Create a measurement plan for Google Analytics. Business goals: [BUSINESS_GOALS]. Website or app and key user actions: [KEY_ACTIONS]. Existing set-up: [EXISTING_SETUP]. Consent and privacy approach: [CONSENT_APPROACH].

For each goal define the metric, the event to track, its parameters, the naming (lowercase with underscores, verb_object), when it fires, whether it is a key event [VERIFY terminology in the current version], and who uses the report. Provide a convention document and an event table (event name, trigger, parameters, key event yes or no, owner, report), with ten examples for a small business site such as submit_contact_form and click_phone_number, saying which are worth marking as key events and why. Fewer, well-defined events beat many unclear ones.

Rules for parameters: no names, email addresses or other personal data, consistent value formats, and a cap on custom definitions. Include an example for a contact form and a purchase, a testing protocol (real-time or debug view [VERIFY]) with a sign-off record, and a quarterly review of events no one uses. Tracking should follow user choices and local rules [VERIFY].

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into ChatGPT, Gemini, Claude or another assistant.

See an example result (fictional data)
Invented event table. submit_contact_form: fires after validation passes, parameters form_name and page_path, key event yes. click_phone_number: fires on tap of the number, key event yes (intention, not a call). download_guide: parameter guide_name, key event no. view_pricing: fires on page load, key event no.
Convention: lowercase with underscores, verb_object. No names, emails or phone numbers in parameters. Test: perform each action once and confirm exactly one event in real time [VERIFY]. Quarterly: retire events nobody uses. Review the table every quarter: any event with no report using it is removed, and any key event is reconciled with CRM leads.

Illustrative only, made-up data. Your results will differ and must be reviewed.

Related prompts