How to Use Google ADK

Ready to understand what users are actually doing inside your mobile app? By installing the Google Analytics SDK, you can move from guesswork to genuine insights, tracking everything from first-time opens to in-app purchases. This guide will walk you through setting up app tracking step-by-step, explaining the process from creating a data stream in Google Analytics 4 to logging your first custom event.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

What is the Google Analytics SDK?

Before we jump into the setup, let's clear up some terminology. The term "Google Analytics SDK" (Software Development Kit) refers to the official library of code you add to your iOS or Android app. This code pack allows your app to communicate with your Google Analytics account, sending valuable data about user behavior back to you for analysis.

In modern practice, especially with Google Analytics 4, this functionality is bundled within the Google Analytics for Firebase SDK. Firebase is Google's mobile app development platform, and its integration with GA4 is seamless. So, when you hear "Google Analytics SDK" for app tracking today, you should be thinking "Firebase SDK."

Step 1: Create a Google Analytics Property and Data Stream

Before your app can send data, it needs a destination. That destination is a specific "Data Stream" inside your Google Analytics 4 property. If you already have a GA4 property for your website, you can simply add a new data stream for your app. If not, you'll need to create one first.

Think of it like setting up a mailbox for your app. Any letters (data) it sends need an address (your GA4 property) and a specific mail slot (your data stream).

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

How to Set Up Your Data Stream:

1. Navigate to your Google Analytics account and go to the Admin section (look for the gear icon in the bottom-left corner).
2. In the "Property" column, make sure your desired GA4 property is selected, then click on Data Streams.
3. Click the blue Add stream button and choose either iOS app or Android app.
4. You'll be prompted to register your app. For an iOS app, you'll need the Apple App Store ID and a "bundle ID." For an Android app, you'll need your "package name." Your developer will have this information readily available.
5. Give your stream a clear name, like "My Awesome App - iOS."
6. Click Register app.

After registering, Google will provide you with a configuration file - a GoogleService-Info.plist for iOS or a google-services.json for Android. This file contains all the unique identifiers that securely link your app to your analytics property. You'll need to download this file and send it to your developer to add to the app's source code.

Step 2: Install the Firebase SDK in Your App

This is where your developer will take the lead, but it's essential for marketers and project managers to understand the core steps. Adding the SDK is what officially installs Google Analytics tracking into your application's DNA.

The process involves using a package manager like CocoaPods or Swift Package Manager for iOS, or Gradle for Android, to add the necessary Firebase libraries to the project.

A Quick Look at the Process (for context):

• Your developer will add the Firebase SDK for Google Analytics to the app's dependency list.
• They will then add the GoogleService-Info.plist (iOS) or google-services.json (Android) file you downloaded earlier into the primary app directory.
• Finally, they’ll add a few lines of initialization code that runs when the app first launches, effectively activating the Firebase connection and allowing it to start collecting data.

Once this is done, your app will automatically start tracking a suite of essential user events - no additional code required.

Step 3: Understand and Implement Event Tracking

Google Analytics 4 is built around an event-based data model. This means that almost every interaction you track - from a screen view to a button click to a level completion - is recorded as an "event." Getting familiar with the different types of events is the key to unlocking meaningful insights.

Automatically Collected Events

As soon as the SDK is installed, you get a set of powerful events out of the box. You don't have to lift a finger to track these foundational metrics. They provide an immediate baseline of user activity.

A few examples include:

• first_open: Logged the very first time a user launches your app, crucial for measuring new user acquisition.
• session_start: Fires whenever a user brings the app to the forefront, starting a new period of engagement.
• app_update: Logged when a user updates to a new version of your app.
• in_app_purchase: Tracks purchases made through the Apple App Store or Google Play Store.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Recommended Events

For more specific but common actions, Google provides a list of "recommended events." While you technically track these as custom events, using Google's suggested names and parameters is a fantastic best practice. Why? Because GA4 recognizes them and uses the data to populate more detailed, pre-built reports - especially around ecommerce and user growth.

Think of them as structured templates for tracking common interactions. Examples relevant to a variety of apps include:

• login: When a user logs in.
• sign_up: When a user creates a new account.
• share: When a user shares content from your app.
• purchase: When a user completes a purchase (if you aren't using the default in-app-purchase flow).
• select_content: When a user selects a piece of content, like an article or product.

Custom Events: Tracking What Makes Your App Unique

This is where the real power lies. Custom events let you track the interactions that are specific to your application's goals. Do you have a fitness app? You might track a completed_workout event. Running a social media app? A posted_update event might be essential.

To implement one, your developer needs to write a single line of code at the moment the action occurs.

For example, to track that a user just completed a 15-minute meditation session in a wellness app, the code might look something like this:

Analytics.logEvent("meditation_finished", parameters: [
  "type": "guided",
  "duration_minutes": 15
])

Notice the parameters. These are key-value pairs that add rich context to your events. Instead of just knowing that a meditation was finished, you can see if guided ones are more popular than unguided ones, or what session durations your users prefer. This added detail is what turns raw data into actionable insights.

Step 4: Use DebugView to Test Your Setup

How do you confirm your nicely crafted events are firing correctly before you release your app to the world? You use DebugView. This is probably the most underrated feature of GA4 for developers and marketers alike.

DebugView is like an EKG for your app's analytics, showing a live, second-by-second stream of events from any device you have in a special "debug mode". You can see every single event firing, along with all its associated parameters, making it incredibly useful for troubleshooting.

Your developer can enable debug mode on their test device (using Xcode for iOS or the adb command for Android), and the moment they do, they can open the DebugView report in GA4's Admin screen and watch data pour in in real-time.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Step 5: Find Your App Data in Google Analytics Reports

Congratulations! Once the SDK is installed, tested, and your app is launched, you can start seeing the fruits of your efforts. But where do you look?

Data can sometimes take 24-48 hours to fully process in the standard reports. Here are a few key places to start exploring:

• Reports → Realtime: Gives you a live snapshot of what's happening right now.
• Reports → Engagement → Events: This is your bread and butter. Here, you'll find a detailed list of all events you're tracking, counted by event name. You can click into any event to see all its associated parameters and metrics like count and total users.
• Reports → Acquisition → User Acquisition: Discover how users are finding your app in the first place - whether they're coming from organic search, paid campaigns, or referrals.
• Reports → Monetization → In-app Purchases: If you monetize in-app, this report breaks down revenue by product, helping you understand what your users are most willing to pay for.

Final Thoughts

Implementing the Google Analytics SDK involves a setup process - from creating a Data Stream in GA4 to adding the Firebase SDK into your app, defining the custom events that matter to your business, and finally analyzing the resulting data. It's the way to move from "I think this is working" to "I know what's happening" and making smarter product and marketing decisions.

While tracking your app's data is critical, it's only one piece of the puzzle. Often, your app data needs to be seen in context with your website traffic, your ad campaigns, and your CRM data. That's where tools like Graphed come in to help solve a myriad of problems. They provide a platform for connecting all your data sources, including Google Analytics, to give you an integrated language to build live, cross-platform dashboards that keep your entire team instantly answering questions, like "Which Facebook campaign is driving the most in-app sign-ups?" or "What is the LTV of users acquired from organic search compared to others?" It's the simpler way to see the whole picture in your journey without relying on complex processes or waiting for competent data managers.