03 / MEASURE · CROSS-PROJECT ANALYTICS DELIVERY

GA4 / GTM
implementation.

From user action to a checked event.

CLIENT WEBSITES

GA4 / GTM implementation

MAINTENANCE WEBSITES

GA4 / GSC reporting framework

01 / THE TRACKING FLOW

Follow
the signal.

Select a stage to see what happens and what needs checking. Follow the signal from the user action into reporting.

EXPLORE THE TRACKING FLOW · SELECT A STAGE

01

User action

A form submission, CTA click or other intended interaction

CHECKPOINT

Start with the measurement requirement.

STAGE1 / 5

02 / DIAGNOSTIC WORKBENCH

Expected isn’t always
observed.

Choose an example, then compare what was recorded with what should happen.

01

Duplicate firing

Inspect overlapping tags and trigger conditions.

COMPARE THE TWO STATES

OBSERVED STATE

CUSTOMER ACTIONEVENT 01DUPLICATE EVENT

The same event fires more than once for one interaction.

03 / REPORTING

From checked data
to a useful report.

Select a layer to explore how sources, metric definitions and reporting structure fit together.

01 / REPORTING FRAMEWORK

Check sources, filters and date ranges.

Use consistent dates and filters for analytics and search data.

SAMPLE REPORT LAYOUTSOURCES
Explore the reporting dashboard →

04 / PROJECT CONTEXT

The work
in practice.

Selected tracking work delivered as part of the WhooshPro team.

PLAYPROGRESSCOMPLETE

ISCA / MEDIA ENGAGEMENT

Beyond
pressing play.

Play, progress, completion, download and CTA tracking, validated with GTM Preview and GA4 DebugView.

Media eventsDownloadsCTA 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.