1/11/2026
This page is for marketing directors, SEO managers and editorial leads who have inherited goals in Google Analytics set up under Universal Analytics. It shows what each goal becomes in GA4: how to inventory it, translate it into an event and then a key event, and validate collection before reading the results.
The fundamentals of the tool are covered in the guide to Google Analytics for GEO and SEO, and the choice of indicators in Google Analytics KPIs. Here, you start from your existing UA setup to decide what to keep, what to translate and what to drop.
From Universal Analytics goals to GA4 key events: understanding what changed
"Goals" belong to Universal Analytics. UA stopped collecting data on 1 July 2023, then closed access to its data on 1 July 2024. GA4 is built on an event-based model: you no longer configure goals within a view; you collect events, some of which are marked as key events.
What Universal Analytics goals measured: destination, duration, pages/screens and event
In Universal Analytics, a goal measured a specific action (a completed form, a newsletter sign-up, a purchase) and counted it as a conversion. Four types coexisted:
- Destination: a specific page load, typically a thank-you page such as /merci.htm after a form.
- Duration: time spent within the session, useful but prone to false positives.
- Pages/Screens per session: the number of pages viewed during the session.
- Event: a tracked action, for example a click on a "Call us" button.
UA also imposed a structural limit: goals were configured at the view level, with a maximum of 20 goals per view. Many accounts therefore duplicated near-identical goals from one view to another.
What GA4 measures today: events, parameters and marking an event as a key event
GA4 collects events (automatic, enhanced measurement, recommended or custom), enriched with parameters. A key event is an event you mark as a key event: since 2024, GA4 has reserved the word "conversion" for Google Ads. Marking, counting and attributing key events are covered in the article on conversions in Google Analytics.
Why this shift matters for measuring performance and ROI
In UA, you chose a goal type; in GA4, you first check that the event exists, then decide whether it represents an outcome. This approach brings three advantages:
- more granular measurement of micro-conversions (clicks, scroll depth, downloads) and macro-conversions (leads, purchases);
- richer segmentation by landing page, device, source / medium or geography;
- steering focused on post-click quality (engagement, key events, value) rather than raw session volume.
Aligning measurement goals with KPIs without bloating your reporting
A common mistake is recreating every UA goal "just in case". Keep the scope minimal:
- Macro-conversions: one to three (demo request, purchase, booked meeting);
- Micro-conversions: a few signals that accelerate optimisation (CTA click, form start, pricing page view);
- Selection criterion: the goal triggers an SEO or GEO decision (optimise a page, refine intent matching, remove friction).
Migrating goals to GA4 key events: a step-by-step method, mapping and validation
Migrating means translating each UA goal into one or more GA4 events, then deciding which become key events. Discrepancies between the old and new tracking come from a skipped step.
Auditing your goals, funnels, values and priorities (macro and micro-conversions)
Start with a structured inventory, view by view, recording for each goal:
- its name and type (destination, duration, pages/screens, event);
- any funnel definition (steps, pages, match rules);
- the value assigned to it, if you used it for ROI estimation;
- its business priority: macro-conversion (a lead) or micro-conversion (a CTA click);
- the decision: migrate, merge with another goal or drop.
To decide, apply a SMART framework (specific, measurable, achievable, realistic, time-bound): a goal you cannot link to a decision has no reason to survive the migration. Duplicates across views merge into a single event.
Translating a goal into a GA4 event: naming, parameters, conditions and de-duplication
For each goal you keep, define four elements:
- the GA4 event: generate_lead, form_submit, purchase…;
- the parameters useful for analysis: page, CTA location, label, content type;
- the firing conditions: which genuine success triggers the event;
- de-duplication: preventing two sends for the same action (double tagging, duplicate triggers, page reloads).
Adopt a single naming convention, in snake_case verb_object (cta_click, form_submit, file_download), and document it. The following table gives the mapping type by type:
Promoting an event to a key event and aligning terminology
Once the event is collected and validated, mark it as a key event so it feeds the reports. GA4 limits the number of key events per property (30 at the time of writing), where UA capped goals at 20 per view: the selection discipline of the inventory therefore still applies.
Also align language across teams: every business "conversion" must correspond to a specific GA4 key event.
Checking data collection: testing, consistency and tracking governance
Before any SEO or GEO analysis, split the checks by tool:
Excluding internal traffic and checking cross-domain settings are part of the tracking hygiene described in the article on direct traffic in Google Analytics; a misconfigured cross-domain setup also inflates referral traffic through self-referrals. Finally, some interactions escape measurement (ad blockers, declined cookies): knowing how to read GA4 under consent leads you to reason in trends over stable collection.
Key-event configurations that matter for GEO and SEO
In SEO as in GEO, migrated key events must show which content and which sources drive high-value actions. To isolate visits from generative engines, the method (a custom channel group built on source) is detailed in Google Analytics for GEO and SEO.
Building a "content → action → lead" view for your SEO pages (guides, comparisons and landing pages)
A useful SEO view connects four links, each carried by an event:
- the landing page (guide, comparison page, landing page);
- proof interactions (scroll, internal clicks to pricing or customer stories);
- contact actions (CTA, form, meeting booking);
- the final outcome, marked as the primary key event.
This chain prevents a classic mistake: concluding that content "doesn't convert" when it is actually driving upstream micro-conversions that are critical in B2B.
Practical examples of Analytics goals and their GA4 equivalents
Four cases come up in most inventories: forms, duration, e-commerce and content interactions.
Form submission: event design, de-duplication and B2B qualification
UA legacy: a destination goal based on the thank-you page (/merci.htm) was the simplest approach. In GA4, a reliable translation follows four rules:
- trigger generate_lead or form_submit on confirmed success (valid server response or success message displayed);
- prevent a second send when the confirmation page is reloaded;
- populate form_id, form_name, page_location, cta_text, cta_position;
- mark the event as a key event for the "lead" macro-conversion.
In B2B, if you qualify MQL and SQL within your CRM, treat GA4 as a measure of intent and volume. Consent and counting rules create gaps: compare trends.
Duration goals: GA4 engagement-based alternatives to avoid false positives
A duration goal overstates quality: an open tab does not indicate active reading. The following table converts the former goal into engagement thresholds:
An engaged session lasts at least 10 seconds, includes two page views or triggers a key event; the link with bounce is detailed in the article on bounce rate and engagement rate. Set your thresholds by device rather than a single duration goal, as durations differ markedly between mobile and desktop.
E-commerce: purchase, basket, checkout and value (when a goal becomes a journey)
In e-commerce, the "goal" is not a single action but a journey: add to basket, begin checkout, purchase. UA handled it with goals and funnels. GA4 covers it with its e-commerce events:
- add_to_cart for adding to basket;
- begin_checkout for starting checkout;
- purchase for the purchase, with value (revenue) and a transaction ID.
Only purchase becomes the primary key event; the upstream steps reveal drop-offs. Replace any fixed goal value with the actual transaction value.
SEO interactions: tracking CTA clicks, downloads and outbound links
In GA4, enhanced measurement natively covers outbound clicks and downloads; CTA clicks require a custom event. Three interactions demonstrate intent:
- CTA clicks (demo request, contact, pricing);
- downloads of guides or product sheets;
- outbound clicks to partners, when they carry business value.
Contextualise every action (page, position, label); otherwise you end up with a raw click total that cannot inform decisions.
Common pitfalls and best practice for GA4 tracking configuration
Failed migrations stem from vague goals or unstable data collection more than from the tool itself.
Poorly defined goals: "easy" indicators versus actionable indicators
Avoid turning weak signals into key events: a simple scroll or a standalone duration does not prove business intent. Reserve marking for actions that trigger a decision:
- a click on a contact or demo CTA;
- a form start or submission;
- a view of an offer page;
- a purchase.
Attribution issues: self-referrals, redirects, missing parameters and tagging errors
Several attribution errors distort the reading of migrated key events:
- misconfigured cross-domain tracking that turns a journey into noisy referral traffic;
- redirects that lose the referrer or campaign parameters;
- campaign links without UTM tags, which inflate direct traffic;
- events named differently across pages, making comparisons impossible.
At a minimum, check that no campaign link goes out without UTM tags.
Data quality: naming conventions, documentation, test environments and ongoing maintenance
A few best practices protect your data series over time:
- a stable, documented naming convention;
- a test environment and validation in DebugView before deployment;
- a weekly review in alert mode, particularly after a new campaign or site change;
- a dated log of every tracking change.
A change is never retroactive: without a recorded date, a break in trend becomes impossible to interpret.
Depending on your situation
Depending on the question you face after the migration, the reference article changes:
- You want to make use of your key events: counting, value, funnels and attribution are covered in conversions in Google Analytics.
- You tracked clicks as goals: what GA4 counts natively and the parameters to add are in click tracking in Google Analytics.
- Your campaigns land in direct or Unassigned: the naming scheme is set out in UTM tags.
- You are comparing with UA history: the model break and its effect on data series are detailed in Google Analytics 4: acquisition, engagement and key events.
To track key events from the migration page by page and match them against organic visibility, the Incremys Performance Reporting module integrates with GA4 and Search Console via API.
FAQ on Google Analytics goals, GA4 key events and conversions
How do you set up goals in Google Analytics?
In GA4, a goal is defined as an event marked as a key event. Start with the business action you want to measure, such as a form submission, instrument the corresponding event with useful parameters (page, CTA, form), validate it in DebugView, then mark it as a key event so it feeds the reports.
Do goals still exist in GA4?
No, goals in the Universal Analytics sense no longer exist in GA4. The feature has been replaced by an event-based model: the operational equivalent of a goal is an event that you choose to mark as a key event. The cap of 20 goals per view gives way to a cap on key events per property.
What is the difference between an event, a conversion and a key event in GA4?
An event is a measured interaction; a key event is an event you mark as important to your business. Since 2024, GA4 has reserved the term "conversion" for Google Ads conversions. On the business side, the conversion remains the intended outcome, which GA4 counts through the corresponding key event.
How do you migrate a Universal Analytics destination goal to GA4?
A destination goal migrates into an event triggered on confirmed submission rather than on the mere display of the thank-you page. Add parameters (form ID, originating page), check in DebugView that it fires only once, then mark it as a key event.
How do you track form submissions reliably without duplicates?
A reliable submission is measured on confirmed success: server-side validation or a success message displayed. Block double firing caused by reloads, double tags or duplicate listeners, and check in DebugView that one submission produces a single event. Then segment by landing page and by source / medium.
How do you set up a duration or engagement goal without biasing your analysis?
A duration goal should not become a key event as it stands. Replace it with engagement signals: engaged session, scroll, table-of-contents click, video play, or engagement time combined with an action. Set these thresholds by device, as durations differ markedly between mobile and desktop.
How do you measure an e-commerce goal in GA4 (purchase, basket, checkout)?
An e-commerce goal is measured as a sequence of events: add_to_cart, begin_checkout, then purchase, the latter marked as the primary key event. Pass the actual transaction value and analyse drop-offs between steps to spot friction in the journey.
.png)
%2520-%2520blue.jpeg)

.jpeg)
.jpeg)
.avif)