Where Can Google Analytics Collect Data From?

When you think of Google Analytics, your mind probably jumps straight to website traffic. While that's its most common use, Google Analytics can collect data from a surprising variety of digital - and even physical - sources. This article will show you how GA gathers data not just from websites, but also from mobile apps, CRMs, and other internet-connected platforms to give you a complete view of your customer journey.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

It Starts with Websites: The Classic Data Source

This is the foundation of Google Analytics and where most businesses start. GA collects data from your website by using a small piece of JavaScript code, often referred to as the "tracking tag" or "GA tag" (specifically gtag.js for Google Analytics 4).

How the Website Tracking Code Works

When you add this tracking code to your website's header, it gets to work every time someone visits a page. The moment a page loads, the script activates and sends a packet of information, known as a "hit" or an "event," to Google's servers. This process happens on every page where the code is present, allowing GA to stitch together a user's entire session.

Out of the box, this tracking tag automatically collects a wealth of crucial data, including:

• Pageviews: It logs every single time a page is viewed.
• Sessions: It groups a user's interactions (pageviews, clicks, etc.) within a specific timeframe into a session.
• User Attributes: It gathers anonymous information about the user, such as their geographic location (country, city), the language their browser is set to, their browser type (Chrome, Safari), device category (desktop, mobile, tablet), and operating system.
• Traffic Source: It identifies how the user arrived on your site, whether through Google search (organic), a paid ad (CPC), social media (social), or by typing your URL directly (direct).

Going Deeper with Custom Events

While automatic data collection is great for a high-level overview, the real power comes from tracking specific interactions that matter to your business. This is where custom events come into play. You can tell Google Analytics to log an event whenever a user performs a specific action.

Common examples include:

• Tracking clicks on a "Request a Demo" button.
• Logging when a user submits a contact form.
• Recording how many times a promotional video is played.
• Noting when someone downloads a PDF guide.

By setting up these custom events, you move beyond just seeing how many people visit your site and start understanding what they actually do once they arrive.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Beyond the Browser: Tracking Mobile Apps

Your users don't just interact with you on a desktop anymore, they're often on your mobile app. Google Analytics 4 is designed from the ground up to track these experiences seamlessly using the Google Analytics for Firebase SDK.

Firebase is Google's platform for building and managing mobile apps. By integrating the Firebase SDK into your iOS or Android app, you can collect robust data about user behavior and send it directly to the same Google Analytics property you use for your website.

What App Data GA Collects Automatically

Just like with websites, the Firebase SDK collects a set of events automatically, requiring no extra coding. These are essential for understanding app engagement and stability.

• first_open: Logged the first time a user launches your app after installing or reinstalling it.
• screen_view: Automatically tracks every time a user views a different screen in your app (the equivalent of a pageview on a website).
• session_start: Identifies when a user engages with the app in the foreground.
• app_update: Fired when the app is updated to a new version.
• in_app_purchase: Automatically records purchases made through the Apple App Store or Google Play Store.

These events provide a baseline understanding of app installation trends, user retention, and basic navigation patterns.

Recommended and Custom App Events

To understand how users interact with your app's unique features, Firebase and GA4 provide a list of recommended events for different app categories (like e-commerce, gaming, and travel). For example:

• For an e-commerce app: add_to_cart, begin_checkout, purchase.
• For a gaming app: level_up, post_score, unlock_achievement.
• For any app: login, share, sign_up.

If none of the automatic or recommended events fit your needs, you can create your own custom events, just like you would for a website. This flexibility allows you to measure any action that defines success inside your app.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Connecting Offline Worlds: POS Systems and CRMs

What about actions that happen completely outside of your digital properties? Many businesses, particularly in retail and B2B, close deals offline. A customer might buy something in a physical store after seeing an ad online, or a lead generated from your website might convert a month later after several calls with a sales rep. Google Analytics can capture this data, too, using a powerful tool called the Measurement Protocol.

In simple terms, the Measurement Protocol allows you to send data directly to Google Analytics servers from any internet-connected device or platform - no browser or mobile app necessary. This opens the door to tracking offline conversions.

Example: Tracking In-Store Purchases with a POS System

Imagine a customer in your loyalty program clicks a Google Ad, browses your e-commerce site, but doesn't buy anything. A week later, they visit your physical store and make a purchase, using their loyalty card (or email) at checkout. Here's how you could track that:

1. Your POS system recognizes the customer's email or loyalty ID.
2. Upon purchase, your backend system sends a "hit" to Google Analytics using the Measurement Protocol.
3. This hit contains the purchase event data (e.g., event_name = 'purchase', value = 150.00, currency = 'USD') and links it to the original online user identifier.

The result? You can now see in GA4 that the Google Ad campaign didn't just lead to website visits, it directly influenced an in-store sale. This helps you calculate a much more accurate return on investment (ROI) for your marketing spend.

Example: Tracking Closed Deals from a CRM

For B2B companies, a website's goal is often to generate leads. These leads enter a CRM like Salesforce or HubSpot, where the sales team nurtures them. The final "conversion" - the closed deal - happens inside the CRM, often weeks or months after the initial web visit.

Using the Measurement Protocol, you can configure your CRM to send an event to GA4 when a deal's status changes to "Closed-Won." This event can include the deal value and can be associated with the unique user ID captured when the person first filled out the lead form on your site. This allows you to directly attribute revenue generated offline back to the marketing channels that initially brought the lead in.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Unifying it All with Data Streams in GA4

One of the most significant changes from Universal Analytics to GA4 is the data model. GA4 is built around the idea of a unified customer journey and uses Data Streams to make this possible.

A Data Stream is simply a source of data within your GA4 property. You can have multiple data streams funneling into the same property. For example, a single property could have:

• A Web stream (for your website)
• An iOS stream (for your iPhone app)
• An Android stream (for your Android app)

Because GA4's measurement model is event-based for all platforms (a page_view on a website and a screen_view in an app are treated similarly), you can analyze user behavior holistically. You're no longer looking at website data in one bucket and app data in another. Instead, you can answer complex, cross-platform questions like:

• "What percentage of users who downloaded our app first discovered us through our blog?"
• "How many users added an item to their cart on the website and later completed the purchase through the mobile app?"
• "What's the total lifetime value of a customer across both in-app purchases and website orders?"

This unified view is incredibly powerful for understanding the true, complex path that customers take when interacting with your business.

Final Thoughts

Google Analytics has evolved far beyond a simple website counter. It's a versatile analytics platform capable of collecting data from your website, mobile apps, CRM, point-of-sale systems, and virtually any other internet-connected device. By pulling these various data sources into a single GA4 property, you can finally map out the complete customer journey, from first click to final conversion, whether it happens online or off.

Pulling all this data together is one thing, but making sense of it is another. Instead of getting tangled up learning GA4's reporting interface, our platform lets you use simple, plain English to create dashboards and reports. We connect to all your marketing and sales sources - including Google Analytics - so you can ask questions like, "Show me the customer journey from our blog to making an in-app purchase" and get a clear, visual answer in seconds. With Graphed , you get all the insights from your cross-platform data without the complexity.