Mobile app analytics in 4 clear steps
I implement and fix Google Analytics 4 and Firebase in mobile apps step by step, from diagnosis to handing ready documentation to your developers.
Sound familiar?
GA4 is not implemented correctly
App data is incomplete or inconsistent, or nobody is sure it is being collected correctly.
You are building a new app
You need Firebase analytics designed from scratch, before the app reaches the stores.
You have events, but no documentation
Events and parameters exist, but nobody knows how to use them for marketing.
4 steps to a correct GA4 implementation
A proven process, delivered for apps such as Diet & Training by Ann, Blinkee and Inter Cars.
Getting started
An intro meeting (1 to 4 hours depending on the app’s complexity) where we review the current state of analytics and marketing. Anything that can be fixed straight away gets fixed straight away.
A sheet of events, parameters, user properties and audiences
2.1 Clicking through the app or mock-ups and listing events and parameters following Google’s recommended structure. The sheet becomes your analytics documentation.
2.2 Defining screen parameters (firebase_screen for the screen_view event) for user path analysis.
2.3 Listing suggested app-specific user properties (for example newsletter sign-up, purchase value).
2.4 Listing suggested audiences needed for Google Ads campaigns, with an explanation of how to build them.
Implementation
Refining the sheet with extra events, parameters and naming changes after the meeting, completing the screen descriptions and adding events and parameters for Meta (Facebook) analytics.
Wrap-up
Reviewing the work and handing the tasks to your app developers, with guidelines for website changes where a dataLayer is needed. For websites, I implement the agreed events myself through Google Tag Manager.
What you get
- Event and parameter documentation that does not depend on any contractor
- Ready audiences for Google Ads campaigns
- Correct user path reporting (path exploration) in GA4
- Consistent data between your mobile app and your website
How long it takes
Timing depends on the number of screens and events in your app. Individual meetings take 1 to 4 hours, and the whole process, from kick-off to handing documentation to developers, usually takes 2 to 4 weeks. I give you a fixed quote after the intro call.
Frequently asked questions
Does the process cover the website too?
Yes. If you have a website as well as an app, I implement the agreed events myself through Google Tag Manager.
Do you need access to Figma or Axure?
It helps, but it is not required. I can describe screens based on the existing app or mock-ups you send.
What if we already have events but no documentation?
That is a common starting point. I organise your existing events in the sheet and show what is missing.
Who implements the changes in the app code?
I hand the tasks to your app developers with a precise specification. I am responsible for the measurement design and its verification.
Let’s start with an intro call.
Tell me about your app, and I will suggest the first step.