Learning path · Level 5 · Tutorial 1

Plan GA4 Events and Key Events

Create a GA4 measurement plan for a sample business, specifying useful events, key events, access needs, consent safeguards, and feasible no-code setup options without requiring a live website.

  • Level: Intermediate
  • Duration: 20 min
  • 8 steps
Start tutorial Back to the path
Plan GA4 Events and Key Events

What you will go through

  1. Connect Business Actions to Events and Key Events Distinguish Northstar Studio’s business actions, events, parameters, and key-event priority before planning collection. 2 min
  2. Identify the Destination and Required Access Map the GA4 account, property, and web data stream, then identify the least access and responsible owner needed for each planned task. 2 min
  3. Separate Available Signals from Events That Need Setup Classify available GA4 signals and identify when planned business events need setup or verification. 2 min
  4. Specify Names, Parameters, and Exact Triggers Turn Northstar Studio's planned events into precise specifications with necessary parameters, observable triggers, and validation boundaries. 3 min
  5. Add Consent and Data-Minimization Safeguards Remove unnecessary or unsafe data from a GA4 event plan and document the consent-related conditions that must be resolved before activation. 2 min
  6. Choose a Feasible No-Code Collection Route Choose supported no-code routes for Northstar Studio’s planned GA4 signals while documenting dependencies and avoiding unsupported tracking promises. 3 min
  7. Evaluate Initial Evidence in Realtime Use simulated Realtime observations to distinguish an observed GA4 event signal from an unverified tracking claim. 3 min
  8. Complete and Review the Measurement Plan Complete and review an implementation-ready GA4 measurement plan for Northstar Studio, including routes, owners, consent safeguards, and final Realtime evidence. 4 min

What you will learn

  • Map business actions to GA4 events and justify which actions should be marked as key events.
  • Document event names, necessary non-identifying parameters, trigger conditions, and expected validation evidence.
  • Identify the analytics permissions, website access, and supported integrations needed to implement the plan.
  • Identify collection that requires consent or specialist support and remove unnecessary or prohibited personal information.
  • Use text-based Realtime observations to distinguish an expected event signal from an unverified tracking assumption.

Before you start

  • Map a Customer Journey and Marketing Funnel
  • Set Marketing Objectives and Calculate Core KPIs
  • Write a Focused Marketing Strategy Brief

Step 1 of 8

Connect Business Actions to Events and Key Events

Distinguish Northstar Studio’s business actions, events, parameters, and key-event priority before planning collection.

Separate the business actions

Three actions, different meanings

Northstar Studio designs websites. Its measurement objective is to count successfully accepted consultation requests—not every visit, click, or form interaction.

Separate three business actions:

  • A visitor views /consultation.
  • A visitor begins the consultation form.
  • The website accepts a consultation request.

An event is a recorded interaction or occurrence sent to GA4. A website action is not automatically proof that GA4 received an event. Later steps will determine how each signal can be collected and checked.

From visit to accepted request

A three-stage diagram shows a consultation page visit, the start of a form, and an accepted request, with the final stage highlighted as the strongest business outcome.

Earlier actions provide context; an accepted request is the business outcome Northstar Studio wants to prioritize.

Add context and set a priority

Events and parameters

An event answers what happened. A parameter adds useful context to that event.

For this plan, a visit can be represented by page_view, form engagement by form_start, and an accepted request by generate_lead. Context can clarify which form and request type were involved:

  • form_id = "consultation_request"
  • lead_type = "consultation"
  • page_location for the collected page URL

Parameters should help answer a measurement question. They do not turn an interaction into confirmed success.

Choose the business priority

A key event is an event the business designates as especially important. It is a priority label, not a collection method.

For Northstar Studio, generate_lead is the strongest candidate: it represents a successfully accepted consultation request. page_view and form_start are still useful context, but they do not show that a request was accepted.

Marking an event as a key event does not create collection, prove lead quality, or prove a sale.

Example

Example: engagement is not success

Northstar Studio can use form_start to understand form engagement while reserving key-event status for generate_lead. A started form may be abandoned, invalid, or never accepted.

Practice: identify each role

Check the distinctions

Match each item to its correct concept.

Tap an item and then its matching pair.

Apply the priority decision

Justify the key-event choice

In 2–3 sentences, state which Northstar Studio action should be the primary key event. Explain why it is stronger evidence than a form start, and name one thing that this designation still does not prove.

Write at least 120 characters (0/120).

Step 2 of 8

Identify the Destination and Required Access

Map the GA4 account, property, and web data stream, then identify the least access and responsible owner needed for each planned task.

Locate the collection destination

From account to web data stream

GA4 has a destination hierarchy. For this plan:

  1. The account is Northstar Studio.
  2. Inside it, the property is Northstar Studio — Web.
  3. Inside the property, the web data stream is Northstar website.

Website collection is sent to the web data stream. Its measurement ID, shown here as G-XXXXXXXXXX, identifies that destination for web collection.

A measurement ID is not a password, user account, or permission. Knowing it does not let someone view reports, change events, edit the website, or manage users.

GA4 destination hierarchy

A nested diagram showing an analytics account, then a web property, then a website data stream, with an identifier attached to the stream.

The measurement ID identifies the web data stream destination; it does not authorize access.

Match analytics tasks to GA4 roles

Request the smallest suitable GA4 role

Choose access based on the task, not on the highest role available. GA4 roles and website access are separate.

A Viewer can inspect reports. Managing events or key events needs an appropriate GA4 role such as Marketer or higher. Property or web data stream configuration generally needs Editor or Administrator. Only an Administrator can manage GA4 users and permissions.

This tutorial uses text scenarios and illustrative views. You do not need a live website, paid tool, or your own GA4 account to make the plan.

Access guide

Use this task-to-access guide when documenting who must be involved.

GA4 roles do not automatically include website or consent-management rights.
Planned taskAppropriate access or ownerWhy
Inspect existing reportingGA4 ViewerRead report information
Manage events or key eventsGA4 Marketer or higherChange event-related setup
Configure property or web data streamGA4 Editor or AdministratorChange collection destination settings
Manage GA4 usersGA4 AdministratorGrant or remove permissions

Identify the separate owners

Separate analytics access from site ownership

A workable plan records dependencies outside GA4 as well. A person with GA4 access may still be unable to connect an integration, change website settings, publish a change, or control the consent-management tool.

For example, a website owner or administrator may need to approve and publish a site-side integration. The consent owner is responsible for confirming applicable requirements and the intended consent behavior. Do not assume that a GA4 role, a measurement ID, or a connected integration grants either authority.

Before implementation, name the owner and access needed for each dependency. Ask only for the access required for that task.

Dependencies to record

For the Northstar Studio plan, document these dependencies under Owner and access rather than treating them as one permission.

Different systems can require different responsible owners.
DependencyTypical responsible ownerNeeded capability
GA4 reportsAnalytics userViewer access
Event or key-event managementAnalytics implementerMarketer or higher access
Stream configurationAnalytics administratorEditor or Administrator access
Website integration or publishingWebsite owner or administratorSite administration and publishing rights
Consent-management behaviorConsent ownerConsent-management access and approval

Practice: assign the right access

Access responsibility check

Match each planned task to the appropriate access or responsible owner.

Tap an item and then its matching pair.

Step 3 of 8

Separate Available Signals from Events That Need Setup

Classify available GA4 signals and identify when planned business events need setup or verification.

Start with what GA4 can actually receive

Available signals depend on collection

GA4 can record website activity only when collection is working. An action on the site is not automatically proof that GA4 received an event.

Some signals can be collected automatically, such as first_visit and session_start. A standard web setup can collect page_view for visited pages. These signals provide context, but they do not by themselves show that Northstar Studio received an accepted consultation request.

Enhanced measurement can collect supported browser interactions when it is enabled and functioning. Its form-interaction support may provide form_start on compatible forms. Treat this as a capability to verify, not a guarantee for every form.

Website actions and event signals

A diagram separates a consultation page view, form start, and confirmed request, showing that each needs an appropriate event signal.

A business action and a received event are related, but they are not the same thing.

Classify names separately from collection

A recommended name is not automatic collection

Collection category and implementation route are separate decisions.

A recommended event gives a recognized name and meaning for a business action. For example, generate_lead is a suitable recommended name for an accepted consultation request. Recommendation does not make the event appear in GA4 automatically.

Use a custom event only when no suitable recommended event exists. Whether an event is automatic, enhanced-measurement based, or requires an additional configured route is a separate question. In all cases, verify that usable source data can reach the web data stream.

Signal categories at a glance

Use this classification before deciding how each signal will be collected.

Collection still depends on a working setup and should be verified.
Signal or eventCollection categoryPlanning implication
`first_visit` / `session_start`Automatically collectedUseful context when collection works; not request success.
`page_view`Standard web collectionShows visit context; verify important page transitions.
`form_start`Enhanced measurementMay be available for a supported, compatible form; verify it.
`generate_lead`Recommended eventAppropriate meaning, but needs intentional collection setup.
Custom eventFallback categoryUse only when no suitable recommended event exists.

Tip

Check page transitions

Do not assume that every apparent page transition produces the intended page_view. Enhanced measurement can handle supported browser-history changes when enabled, but site behavior still needs verification.

Avoid treating form activity as business success

Match each signal to its evidence strength

For Northstar Studio, separate the strength of each signal:

  • page_view on /consultation provides visit context.
  • form_start indicates engagement with the consultation form when that interaction is actually collected.
  • generate_lead should represent a successfully accepted consultation request—not merely an attempted submission.

The measurement objective is accepted requests. Neither a form start nor a detected form-submit signal proves that the request was accepted, qualified, or sold.

Northstar Studio signal map

This is a planning classification, not proof that these events are already live.

Use the strongest available signal for the stated business action.
Business actionEvent nameWhat the signal supportsWhat remains to verify
Visit `/consultation``page_view`Consultation-page contextWhether the relevant page view arrives as expected
Begin the designated form`form_start`Form engagementCompatibility and actual enhanced-measurement collection
Successfully accepted request`generate_lead`Business-important request signalA collection route tied to accepted success, not just submission

Example

Submission is weaker than acceptance

Example: A visitor can click Submit and still see validation errors, encounter a technical failure, or create an event that does not demonstrate acceptance. Plan generate_lead around a reliable success condition, then verify the signal after setup.

Practice: reject unsupported assumptions

Classify the evidence

Northstar Studio has working base collection. A visitor opens /consultation, begins a compatible form, and submits it. Which planning statement is defensible?

Step 4 of 8

Specify Names, Parameters, and Exact Triggers

Turn Northstar Studio's planned events into precise specifications with necessary parameters, observable triggers, and validation boundaries.

Define the signal, not an assumption

Write a testable event specification

A measurement-plan entry is a testable statement, not just an event name. It connects:

  • Business action — what the visitor actually did
  • Event name — the GA4 signal to collect
  • Parameters — only the context needed for the question
  • Trigger — the observable condition that sends the event
  • Key event? and Rationale — why the signal matters
  • Validation evidence — what should, and should not, happen during a test

For Northstar Studio, write event names in lowercase with underscores. Event names are case-sensitive, so generate_lead and Generate_Lead are different names. Reuse the appropriate recommended name rather than inventing a custom name.

From business action to evidence

Diagram showing a consultation-page visit, a form start, and an accepted request as distinct signals; button clicks, invalid submissions, and reloads are not equivalent to accepted success.

The trigger must identify the green accepted-request state, not a nearby interaction or page state.

Specify the three Northstar Studio events

Three planned signals

This compact plan separates visit context, form engagement, and the outcome Northstar Studio wants to count. page_location identifies the collected page URL. The listed parameter values are planned configuration values; a collection source must actually be able to provide them.

Compact event specifications

Each row connects a business action to a precise intended signal.
Business actionEvent nameParametersTriggerKey event?Rationale
View consultation page`page_view``page_location`A page view is collected for `/consultation`NoVisit context is not a completed request.
Begin designated form`form_start``form_id = "consultation_request"`A detectable start of that form occursNoShows form engagement, not success.
Request is successfully accepted`generate_lead``form_id = "consultation_request"`; `lead_type = "consultation"`The website confirms acceptance of the requestYesCounts the defined consultation-request outcome.

Set boundaries and validation evidence

Protect the success signal

A submit-button click is an attempt, not proof that a request was accepted. An invalid submission is not success. A visitor can also directly open or reload /consultation/thank-you; that page state alone does not prove a new accepted request.

Write the Trigger around the acceptance condition itself. Then make Validation evidence test both boundaries: one accepted request should produce the intended signal once, while a click, an invalid submission, and a confirmation-page reload should not produce an additional success signal.

Example

Example: define the boundary

Strong specification

Trigger: Send generate_lead when the designated consultation request has been successfully accepted by the website.

Validation evidence: One accepted request produces one generate_lead. A submit-button click with an invalid form does not produce it. Opening or reloading /consultation/thank-you does not itself add another generate_lead.

This does not decide how collection will be configured. It states the behavior that any proposed collection route must be able to support.

Tip

Parameter discipline

Use only parameters that answer a measurement question. If the planned source cannot reliably provide a parameter, do not guess or manufacture its value; record the dependency for the collection-route decision.

Complete the missing specification fields

Complete the event name

Complete the missing field in this compact specification.

Business action: Successfully accepted consultation request

Event name: __

Complete the key-event decision

Complete the missing field in this compact specification.

Event name: generate_lead

Key event?: __

Make the success rule defensible

Rewrite the ambiguous success trigger

A draft specification says: “Send generate_lead when a visitor opens or reloads /consultation/thank-you.”

Rewrite its Trigger and Validation evidence in two short lines. Your rewrite must tie the event to an accepted request and make clear that a button click, invalid submission, direct opening, or reload must not create the success signal.

Write at least 120 characters (0/120).

Step 5 of 8

Add Consent and Data-Minimization Safeguards

Remove unnecessary or unsafe data from a GA4 event plan and document the consent-related conditions that must be resolved before activation.

Minimize data across the whole route

Collect context, not identity

Minimize before collecting

A measurement plan should collect only the context needed to answer its business question. This applies to automatically collected surfaces as well as parameters deliberately added to an event.

For Northstar Studio, generate_lead needs business context—not customer identity. The planned values form_id = "consultation_request" and lead_type = "consultation" describe the request without identifying the person who submitted it.

Do not send names, email addresses, phone numbers, or identifying free-text form responses to Google Analytics. Hashing an identifier is not a general workaround. A plan with no direct identifiers is also not automatically anonymous or exempt from applicable privacy requirements.

Check every collection surface

Diagram showing a filter between website collection surfaces and analytics, passing business categories while blocking identifiers and free text.

Review parameters, URLs, page titles, query strings, and form fields—not just the event name.

Set a responsible launch condition

Keep, remove, or inspect

Use the smallest useful set of non-identifying values. A URL can be useful as page_location, but inspect it carefully: query strings or page paths must not expose submitted details.

Example treatments for the Northstar Studio measurement plan.
Collection surfacePlan treatmentWhy
`form_id = "consultation_request"`RetainIdentifies the designated form.
`lead_type = "consultation"`RetainDescribes the request category.
Name, email, or phone parameterRemoveDirect identifying information is prohibited.
Project-notes free-text fieldDo not sendIt can contain identifying or sensitive details.
`page_location` with a query stringInspect and prevent exposureA query value can carry personal information.
Page titleInspect before activationA title can unintentionally reveal a customer detail.

Warning

Consent is a launch condition

Before activation, determine the applicable consent and disclosure requirements. Where consent is required, the responsible owner must verify behavior before consent, after refusal, and after withdrawal.

A GA4 setting, a consent banner, or Consent Mode does not by itself obtain valid consent or prove compliance. If requirements are unclear, data could be sensitive, or collection behavior is advanced, pause and involve qualified privacy or technical support.

Practice classifying safeguards

Choose the safeguard

Match each proposed collection item to the appropriate safeguard.

Tap an item and then its matching pair.

Write the safeguard decision

Audit the proposed collection

Audit this proposed generate_lead plan for Northstar Studio.

It proposes: form_id = "consultation_request", lead_type = "consultation", a submitter email parameter, a project-notes free-text parameter, and page_location from /consultation/thank-you?email={submitted_email}. The team has not yet confirmed applicable consent requirements.

Write a short audit note that states: (1) which business-context parameters to retain, (2) what to remove or prevent from being collected, including any surface to inspect, and (3) the consent-related launch condition and the owner or specialist who must resolve it. Do not assume that a GA4 setting solves the consent question.

Write at least 180 characters (0/180).

Step 6 of 8

Choose a Feasible No-Code Collection Route

Choose supported no-code routes for Northstar Studio’s planned GA4 signals while documenting dependencies and avoiding unsupported tracking promises.

Evaluate documented integration support

Read the capability profile

A GA4 connection is only a destination. Before choosing a route, read what the website or CMS integration is documented to collect.

For Northstar Studio, check five things: basic page collection, support for the specific business event, available non-identifying parameters, how accepted success is detected, and compatibility with the required consent behavior. Do not infer a capability merely because the integration can send data to GA4.

Collection routes depend on source signals

Diagram showing that a native integration can send website signals to GA4, while a derived-event rule can only use signals that already arrived.

Choose a route from documented source signals—not from an assumption that GA4 can see every website action.

Scenario capability profile

This is the scenario capability profile for Northstar Studio. It is a planning input, not a claim about every CMS or integration.

Evaluate each capability before putting it in the measurement plan.
CapabilityDocumented behaviorPlanning implication
Native CMS integrationSends `page_view`, `form_start`, and `generate_lead` after the CMS accepts a consultation requestCan support the three planned signals
ParametersCan send `form_id = "consultation_request"` and `lead_type = "consultation"` with the accepted-request eventUse only these needed business-category details
GA4 connectionIdentifies the destination `Northstar website` with `G-XXXXXXXXXX`Does not by itself prove event support
Consent settingCan follow the site's configured consent behaviorConsent owner must verify required behavior before launch

Avoid gaps and duplicate signals

Assign one route per signal

Use one intentional collection route for each business signal. For this profile, use the native CMS integration for page_view, form_start, and generate_lead. Do not add a derived rule that produces the same generate_lead from a confirmation-page view: two routes for one success signal can double-count it.

A no-code derived-event rule is useful only when GA4 already receives a usable source event and matching condition. It transforms received data; it cannot observe a button, acceptance decision, or form state that never reaches GA4.

Warning

Treat confirmation pages cautiously

A rule based on /consultation/thank-you is only a conditional fallback. It might be considered only if the page is reliably shown after an accepted request and the team has addressed direct visits, reloads, and repeated signals.

In this scenario, the confirmation page can be opened directly and reloaded. A page_view there is therefore not reliable proof that the CMS accepted a request. If no accepted-request signal is available, record generate_lead as Unverified or blocked and escalate to the website owner or a technical specialist rather than promise collection.

Document dependencies

A route is ready only when its responsibilities are explicit.

These fields belong in the implementation-ready measurement plan.
Event nameCollection routeOwner and accessPrivacy and consent
`page_view`Native CMS integrationWebsite owner publishes; GA4 access supports inspectionConsent owner verifies configured behavior
`form_start`Native CMS integrationWebsite owner publishes; appropriate GA4 role inspects configurationNo identifying form text or customer details
`generate_lead`Native CMS accepted-request eventWebsite owner publishes; appropriate GA4 role manages event settingsConsent owner verifies behavior; use only needed parameters

Practice: prevent duplicate collection

Check for route overlap

The native CMS integration already sends generate_lead only after a consultation request is accepted. A teammate also proposes a derived generate_lead whenever /consultation/thank-you receives page_view. What is the best plan?

Apply the capability profile

Make a defensible route decision

Use this planning profile:

  • Northstar website is connected through G-XXXXXXXXXX.
  • The native CMS integration sends page_view, form_start, and generate_lead only when the CMS accepts a consultation request. It can send form_id = "consultation_request" and lead_type = "consultation".
  • A no-code derived-event rule can use only events and parameters already collected.
  • /consultation/thank-you can be opened directly and reloaded.
  • The website owner controls publishing, an appropriate GA4 role manages event settings, and the consent owner controls and verifies consent behavior.

Write a short route decision. State: (1) the route for generate_lead; (2) what a derived-event rule would need before it could work; and (3) what to do if the native accepted-request signal disappeared and only confirmation-page views remained. Include the relevant owner dependency.

Write at least 220 characters (0/220).

Step 7 of 8

Evaluate Initial Evidence in Realtime

Use simulated Realtime observations to distinguish an observed GA4 event signal from an unverified tracking claim.

What Realtime can—and cannot—show

Realtime is a limited initial check

Realtime is an initial receipt check: it can show that GA4 recently received an event for the intended destination. It does not prove that all visitors are counted, that every trigger is accurate, or that collection is compliant.

Keep two checks separate:

  • Was an event signal observed in Realtime?
  • Is the event designated as a key event in the property settings?

Seeing generate_lead in Realtime is useful evidence of recent receipt. It does not prove lead quality, a sale, complete historical reporting, attribution accuracy, or correct downstream reporting behavior.

Receipt and designation are separate

A diagram connecting website actions to a Realtime event panel, with key event status shown in a separate settings card.

Illustrative GA4 view: Realtime shows recently received signals; key-event designation requires a separate check.

Compare actions with before-and-after evidence

Make the test record comparable

Use one controlled action at a time. Before testing, record the intended destination: property Northstar Studio — Web and web data stream Northstar website. Also record the consent state, a baseline observation, the action performed, and the expected change.

Compare counts before and after each action. Inspect parameter details only when they are visible. A missing parameter in the supplied observation is not evidence that it was collected, and a visible event name does not prove the success condition behind its trigger.

Simulated Realtime observations

Simulated Realtime observations from one controlled test. The status records what the observation itself shows, not a final verdict on the implementation.

Simulated Realtime observations — controlled test for `Northstar Studio — Web` / `Northstar website`, with consent granted for the test.
Time and action`generate_lead` countVisible detailStatus
14:05:00 Baseline0No `generate_lead` detailObserved
14:06:00 Successfully accepted consultation request0 to 1`form_id = "consultation_request"`Observed
14:08:00 Invalid submissionRemains 1No new `generate_lead` detailNot observed
14:10:00 Reload `/consultation/thank-you`1 to 2No additional acceptance detailObserved

Separate observation from diagnosis

Use careful language. The accepted-request action coincides with an expected signal in this controlled test. The later increase after a confirmation-page reload is an extra observed signal, not evidence of another accepted request.

A missing signal remains unresolved until timing, collection support, consent state, possible blocking, and the intended property and web data stream have been checked. For an unexpected extra signal, compare the trigger and selected collection route with the controlled action, then retest. Do not make an immediate diagnosis from Realtime alone.

Make an evidence-bounded statement

State only what the evidence supports

Based only on the Simulated Realtime observations, which statement is supported?

Apply the controlled-test evidence

Write an initial Realtime evidence note

Controlled test record for Northstar Studio — Web / Northstar website, with consent granted for the test:

  • 16:00:00 baseline — page_view = 1, form_start = 0, generate_lead = 0
  • 16:02:00 — a visitor begins the form, leaves a required field invalid; form_start = 1 and generate_lead = 0
  • 16:04:00 — a consultation request is successfully accepted; generate_lead = 1 and the visible detail is form_id = "consultation_request"
  • 16:06:00 — /consultation/thank-you is reloaded; generate_lead = 2

Write a short initial evidence note. Compare the actions with the before-and-after observations. Identify one expected signal and one suspicious signal, state what is observed and what remains unverified, then name the next appropriate check. Do not claim that tracking is fully validated.

Write at least 180 characters (0/180).

Step 8 of 8

Complete and Review the Measurement Plan

Complete and review an implementation-ready GA4 measurement plan for Northstar Studio, including routes, owners, consent safeguards, and final Realtime evidence.

Synthesize the event specification

From plan to implementation handoff

A completed measurement plan is a defensible handoff: it states what Northstar Studio intends to collect, under which conditions, and what evidence will be checked. It is not yet proof that collection is live, accurate, or ready to rely on.

The objective remains narrow: count successfully accepted consultation requests. Visits and form engagement provide useful context, but neither is evidence that a request was accepted. The destination is account Northstar Studio, property Northstar Studio — Web, and web data stream Northstar website, represented by measurement ID G-XXXXXXXXXX.

Three-event measurement plan

Use this core specification consistently when assigning collection routes and validation checks.

Northstar Studio measurement-plan summary
Business actionEvent nameParametersTriggerKey event?Rationale
View `/consultation``page_view``page_location`The native CMS integration collects a page view for `/consultation`NoProvides consultation-page context, not request success.
Begin the designated form`form_start``form_id = "consultation_request"`A detectable start of the designated consultation form occursNoShows form engagement, not acceptance.
Successfully accepted consultation request`generate_lead``form_id = "consultation_request"`; `lead_type = "consultation"`The CMS confirms that the designated request was successfully acceptedYesMatches the stated objective: accepted consultation requests.

Add routes, owners, and safeguards

Assign one route, then name the dependencies

Use one intentional collection route per signal. In this scenario, all three signals use the native CMS integration. Its standard page-collection capability sends page_view; its supported form capability sends form_start; and its accepted-request signal sends generate_lead only after CMS acceptance.

Do not add a derived confirmation-page rule for generate_lead alongside this route. A direct visit or reload of /consultation/thank-you can create misleading repeat signals. A completed plan must identify this overlap risk instead of presenting duplicate collection as reliable.

Route, safeguard, validate

Three website signals pass through a CMS integration, while only the accepted-request signal passes an acceptance gate before reaching a key-event marker.

Illustrative GA4 view: the accepted-request signal requires an acceptance condition before it can support the key event.

Route and accountability checklist

These are requirements to implement and test. They are not claims that Northstar Studio has already verified live collection.

Collection, ownership, safeguards, and expected validation evidence
Collection routeOwner and accessPrivacy and consentValidation evidence
Native CMS integration: standard page-collection capability for `page_view`Website owner has site administration and publishing rights; GA4 Viewer can inspect resultsInspect `page_location` and prevent personal information in paths or query strings; consent owner verifies required behaviorA controlled visit to `/consultation` shows the expected `page_view` in Realtime.
Native CMS integration: supported designated-form signal for `form_start`Website owner publishes; analytics implementer has an appropriate GA4 role, such as Marketer or higher, for event-related managementRetain only `form_id = "consultation_request"`; do not send names, emails, phone numbers, or form textA controlled start of the designated form shows `form_start`; compatibility and visible details are checked.
Native CMS integration: CMS accepted-request signal for `generate_lead`Website owner confirms and publishes the acceptance condition; analytics implementer has Marketer or higher access to manage the key eventRetain only `form_id = "consultation_request"` and `lead_type = "consultation"`; consent owner verifies required behavior before consent, after refusal, and after withdrawalOne accepted request produces one signal; invalid submission and confirmation-page reload do not add another success signal.

Review the complete plan against evidence

Final measurement-plan handoff

Write the final Northstar Studio handoff in 6–9 short bullet points. Include:

  1. The three Business action → Event name pairs, each planned Parameters, and each precise Trigger.
  2. Why only one event is a key event.
  3. The selected Collection route for all three signals and the needed Owner and access roles.
  4. Privacy and consent safeguards, including what must not enter analytics.
  5. Your interpretation of these Simulated Realtime observations for generate_lead:
  • 14:05:00 baseline: count 0 — Observed
  • 14:06:00 successfully accepted consultation request: count 1 — Observed
  • 14:08:00 invalid submission: count remains 1 — Not observed
  • 14:10:00 reload /consultation/thank-you: count 2 — Observed
  1. Whether implementation can proceed as reliable collection, plus the evidence or correction still required.

Do not diagnose the source of the repeated signal from these observations alone. State what is observed, what remains Unverified, and the next check.

Write at least 500 characters (0/500).

Close the handoff

Summary

Final review

A robust measurement plan connects the business objective to precise event specifications, intentional collection routes, responsible owners, privacy conditions, and validation evidence.

A completed plan is different from readiness to implement, and both differ from verified live collection. Here, the confirmation-page reload produced an extra success signal. Treat that as an issue to investigate and retest—not as evidence of two accepted consultation requests.

  • Use page_view for consultation-page context, form_start for designated-form engagement, and generate_lead only for an accepted request.
  • Mark generate_lead as the key event because it matches the accepted-request objective; designation does not create or validate collection.
  • Use the native CMS integration as the intentional route for all three signals and avoid a competing confirmation-page rule.
  • Keep only necessary non-identifying parameters and inspect indirect personal-information surfaces such as URLs, query strings, and free text.
  • Realtime is initial evidence: investigate missing or repeated signals before relying on collection.

Tutorial complete

Congratulations! You completed: Plan GA4 Events and Key Events

You completed a defensible GA4 measurement-plan handoff for Northstar Studio. You can now distinguish a completed plan from implementation readiness and verified collection.

Download the App now to have access to + 5000 free courses, exercises, certificates and lots of content without paying anything!

  • 100% free online courses from start to finish

    Thousands of online courses in video, ebooks and audiobooks.

  • More than 60 thousand free exercises

    To test your knowledge during online courses

  • Valid free Digital Certificate with QR Code

    Generated directly from your cell phone's photo gallery and sent to your email

Cursa app on the ebook screen, the video course screen and the course exercises screen, plus the course completion certificate