GA4 implementation
Measure what matters
Give your analysis a reliable starting point with clear tracking and event definitions.
See our approachDOES THIS SOUND FAMILIAR?
Does this sound familiar?
Your site has changed, but your tracking has not. Important actions may never enter the data.
THE JOURNEY BEHIND THE EVENT
They arrived. They looked. What happened next?
Open a moment in the journey to see the question behind it.
1Arrive
＋
How did they find you?
Can sources, channels and campaigns be identified consistently?
2Explore
＋
What made them look closer?
Are meaningful interactions defined beyond a page view?
3Act
＋
Does this count as a meaningful conversion?
How do submission, successful delivery and a qualified lead differ?
Illustrative journey. Actual events depend on your site and goals.
OUR APPROACH
A clear question. A practical approach
- 01
Define events around the customer journey
- 02
Organise GTM deployment and naming
- 03
Validate events, parameters and conversions
WORKING TOGETHER
Useful beyond the handover
These are starting points for scoping. Deliverables and timelines are agreed for each engagement.
Measurement plan and event specifications
Implementation and validation records
Maintenance and handover guidance
SCOPE
What we can take on
GA4
- E-commerce event planning, deployment and testing
- Implementation
- Site analysis after launch
GA360
- Upgrading a specific property
- Implementation planning and support
GTM & BigQuery
- Tracking deployed and maintained in GTM, with fewer site code changes
- Raw GA data exported to BigQuery for deeper analysis
This service at a glance
| Item | Details |
|---|---|
| Typical situation | Your site has changed, but your tracking has not. Important actions may never enter the data. |
| How we work | Define events around the customer journey; Organise GTM deployment and naming; Validate events, parameters and conversions |
| What you receive | Measurement plan and event specifications; Implementation and validation records; Maintenance and handover guidance |
| Before we start | Your site, current GA4/GTM setup and the customer actions you need to measure. |
OFFICIAL REFERENCES
References: Google documentation
Our approach follows Google’s official documentation. When the rules change, the latest official guidance applies.
- Ecommerce eventssupport.google.com
- BigQuery Exportsupport.google.com
- Google Analytics 360 (GA4 properties)support.google.com
- Tag Manager: create an account and containersupport.google.com
BEFORE WE BEGIN
A useful place to start
Your site, current GA4/GTM setup and the customer actions you need to measure.
Discuss your situationCan we start without knowing the root cause?
Yes. Describe the confusing numbers or workflow, and we can discuss whether diagnostics, analysis or another service is the right starting point.
Do we need to change tools first?
We first review the current setup and constraints. A new tool should follow a clear need.
How are scope and timing agreed?
We scope the data, systems, participants and deliverables together before proposing the engagement.
COMMON QUESTIONS
GA4, BigQuery and GA360
How do GA4, BigQuery and Data Studio fit together?
GA4 collects events, BigQuery stores the raw data and Data Studio builds the reports. A standard GA4 property can export 1 million events a day to BigQuery; a 360 property can export up to 20 billion. Sites with high event volume should check the limit first. Order matters: define and validate the event specification, then connect BigQuery, then build dashboards.
When does it make sense to move to GA360?
Three reasons are common:
- event volume exceeds the standard export limit;
- data must be kept longer: event data in 360 can be kept for up to 50 months, compared with 14 months in standard GA4;
- you need the fresh daily export, which only 360 offers.
CloudAD is the only Taiwan-headquartered company among the GA360 sales partners in Taiwan.
What should financial, insurance or retail companies settle first?
Governance before features: which data may enter GA, how access is divided, how long data is kept, and how cross-domain and app tracking connect. These decisions determine whether every later report can be trusted.
How we work
- Audit: check the existing setup for duplicate events, inconsistent naming and missing parameters.
- Plan: define events and parameters around business questions.
- Implement: deploy through GTM; for e-commerce, follow Google's e-commerce specification.
- Validate: check every item against a fixed template and deliver the validation record.
- Analyze: explain what the numbers mean and what to decide next.
Sources for these answers
- Google Analytics Help: Data retention
- Google Analytics Help: Set up cross-domain measurement