← Back to selected work

03 / MEASURE · CROSS-PROJECT ANALYTICS DELIVERY

GA4 / GTM
implementation.

Events checked from the website interaction through to reporting.

01 / CHECK THE EVENT

One enquiry.
Counted correctly.

A successful form submission should be counted once, with the context needed to understand it. These are reconstructed examples, not client data.

Customer actionA visitor submits one enquiry form.

Duplicate event

Problem example

2 events

Two events for the same submission would count one enquiry twice.

Expected result

1 event

One event represents this one successful submission.

How I check itInspect overlapping tags and triggers in GTM Preview, then check the event in GA4 DebugView.

I configured and validated events, triggers and parameters, and contributed to GA4/GSC reporting within the WhooshPro team.

20+

CLIENT WEBSITES

GA4 / GTM implementation
40+

MAINTENANCE WEBSITES

Separate GA4 / GSC reporting framework

Showing anonymised process reconstructions. Reports use Google sample data.

View sample reports ↓

02 / FROM THE WEBSITE TO GA4

How a form submission
reaches GA4.

The same enquiry passes through these five steps. Each step has a different job; checking the whole path helps locate missing or duplicate data.

  1. Website

    The visitor submits a form

    Start with the successful interaction that should count as an enquiry.

  2. Data layer

    Pass the event details

    Provide the event name and the form context required by the measurement plan.

  3. Google Tag Manager

    Send the right event

    Use the intended trigger. In GTM Preview, check that the tag fires once.

  4. Google Analytics 4

    Confirm it arrived

    Use GA4 DebugView to check the event and its required parameters.

  5. Reporting

    Use the checked data

    Confirm definitions, filters and dates before comparing totals.

03 / MAKE THE DATA USEFUL

A report you
can interpret.

Reporting was a separate scope: a GA4/GSC framework covering 40+ maintenance websites.

  1. Agree on the sources

    Use the agreed GA4 and GSC sources, date ranges and filters.

  2. Define each measure

    A button click and a submitted enquiry are different actions. Agree on what each number represents.

  3. Make the report reviewable

    Apply those definitions in a recurring Looker Studio report. Keep source and date context visible.

RECONSTRUCTION · SYNTHETIC DATA

Reading a sample report.

How much of this sample traffic led to an order?

Sessions
1,600
Orders
32
Sample purchase rate
2.00%

32 orders ÷ 1,600 sessions = 2.00%. These figures demonstrate how to read the report; they are not client performance results.

Explore the reporting dashboard →

04 / TRACKING IN PRACTICE

Two tracking
examples.

Selected tracking work delivered as part of the WhooshPro team. Choose an example to see the event path and contribution scope.

Process illustration · Not a live player or form

  1. Video starts
  2. Progress
  3. Completion

Anonymised reconstruction · Team contribution. No client screenshots or data.

Beyond
pressing play.

I worked on media event tracking and validation with GTM Preview and GA4 DebugView.

Tracking covered: play, progress, completion, downloads and CTA clicks.

Read the tracking field note →

NEXT CONVERSATION

Have a tracking question?

Describe the intended interaction, your current setup and what you are seeing.

Let’s talk

TRACE

Capture stopped

Local only · clears on refresh

Earlier records remain until cleared or refreshed.

0 interactions recorded

Capture stopped. Turn TRACE on to record approved interactions.