Better Gas case studiesWork · Better Gas · Analytics

GA4 — Event, Engagement & Conversion Analysis

I reviewed event definitions and journey signals in GA4 to separate measurable activity from assumptions about qualified leads, purchases and revenue.

Google Analytics 4Event trackingConversion analysis
GA4 — Event, Engagement & Conversion Analysis presentation mockup
ClientBetter Gas Energy Services Limited
SectorLPG retail, cylinder exchange & distribution
GeographyNigeria · Abuja/FCT & surrounding distribution areas
RoleStrategy, implementation, management & analysis where supported
Evidence windowApr 23–29, 2026 snapshot; follow-up exports required
Engagement datesNot independently established
What the client needed

A key event becomes commercially meaningful only when its definition, trigger and downstream business outcome are understood.

This work examined how captured events, key events and purchase signals relate to the actual customer journey—and where additional reconciliation is still required.

Delivery architecture

How the work was structured.

A case-specific operating model rather than a generic service checklist.

01Acquisition
02Page
03Action
04Key event / purchase
What I delivered

Implementation translated into operational value.

01

Defined inquiry, purchase and key-event meanings

Configured and reviewed within the relevant platform context, with QA and evidence boundaries documented.

02

Reviewed event naming and tagging behavior

Configured and reviewed within the relevant platform context, with QA and evidence boundaries documented.

03

Mapped acquisition-to-page-to-action funnels

Configured and reviewed within the relevant platform context, with QA and evidence boundaries documented.

04

Identified consent and measurement gaps

Configured and reviewed within the relevant platform context, with QA and evidence boundaries documented.

05

Separated analytics purchase events from revenue reconciliation

Configured and reviewed within the relevant platform context, with QA and evidence boundaries documented.

06

Created instrumentation recommendations

Configured and reviewed within the relevant platform context, with QA and evidence boundaries documented.

Measurable evidence

What the available reporting actually proves.

110

Active users

Source: Google Analytics 4

Period: Apr 23–29, 2026

Snapshot activity only.
2.4K

Event count

Source: Google Analytics 4

Period: Apr 23–29, 2026

Events are not automatically qualified leads.
443

Key events

Source: Google Analytics 4

Period: Apr 23–29, 2026

A GA4 key event depends on how the event was configured.
7

Purchases shown

Source: Google Analytics 4

Period: Apr 23–29, 2026

These purchases are not reconciled here to WooCommerce revenue.
How it worked

Decision logic, implementation and QA.

  1. 01

    Define event semantics

    Review the platform state, implement the relevant configuration, test the customer/measurement path and document the operational handoff.

  2. 02

    Validate naming and tagging

    Review the platform state, implement the relevant configuration, test the customer/measurement path and document the operational handoff.

  3. 03

    Review acquisition-to-action funnels

    Review the platform state, implement the relevant configuration, test the customer/measurement path and document the operational handoff.

  4. 04

    Inspect measurement gaps

    Review the platform state, implement the relevant configuration, test the customer/measurement path and document the operational handoff.

  5. 05

    Document instrumentation improvements

    Review the platform state, implement the relevant configuration, test the customer/measurement path and document the operational handoff.

Results & interpretation

Commercial significance without overstating causality.

Observed / configuredMarket demand / audience
Observed / configuredDiscovery or click
Configured / measurableBetter Gas web / messaging experience
Configured / measurableMeasurable enquiry
Configured / measurableHuman / automated follow-up
Only where independently evidencedOrder or visit where independently evidenced

The evidence on this page distinguishes observed platform state, configured journeys, forecasts and future measurement requirements. Where purchase attribution is absent, no ROAS or ROI claim is made.

Source evidence gallery

Original evidence is tracked separately from presentation mockups.

Privacy review required

Analytics _ Home (30.04.2026 19_17).png

What this proves: this source is part of the documented evidence set for the case study.

What remains unverified: any metric, identity or operational claim not explicitly described in the evidence panel above.

Raw admin screenshots are not rendered publicly until sensitive data is redacted and approved.
Future optimization

Recommended next measurement and operating improvements.

Recommendation 1

Reconcile GA4 purchases to WooCommerce orders

Recommendation 2

Audit key-event definitions

Recommendation 3

Create funnel reporting by acquisition source

Next project

Need a similar result-oriented setup?

Discuss the business problem, the platform environment and the evidence you need to measure next.

Discuss your project More Better Gas work