How to Track Individual Users in Google Analytics

Tracking what a single user does on your website, from their first visit to their final conversion, can feel like you're trying to solve a huge puzzle. Google Analytics 4 gives you the tools to see this individual user journey, helping you understand behavior, troubleshoot issues, and optimize your conversion paths. This article will guide you through the two primary methods for tracking individual users in GA4: using the User ID feature and capturing the Client ID as a custom dimension.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Why (and How) You Can Track Individual Users

Understanding a user's entire journey across multiple sessions and devices gives you incredible insight. You can see which channels bring in your most valuable users, identify friction points in your funnel where people get stuck, and provide better support by understanding what a specific user was doing before they ran into an issue. For example, if a customer complains about a broken checkout page, you could look up their specific journey to see the exact sequence of pages and events that led to the error.

But before we get started, it's absolutely essential to address data privacy. Google's terms of service strictly prohibit sending any Personally Identifiable Information (PII) to Google Analytics. This includes information like:

• Names
• Email addresses
• Phone numbers
• Street addresses
• Usernames that can identify an individual (e.g., john.doe123)

Sending PII can get your GA account suspended. The methods we'll cover respect these rules by using anonymous or pseudonymous identifiers that you generate, which cannot be traced back to an individual by an outside party (like Google).

Graphed

Still Building Reports Manually?

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

Watch the Demo

Method 1: Using the GA4 User ID Feature (The Best Way)

The User ID feature is Google's intended method for tracking signed-in users. It lets you associate your own unique, non-PII identifier with a user. This is the most accurate way to stitch together a user's activity across different browsers and devices, as long as they are logged into their account on your site.

When is this useful? If you have a website or app with a login system (like an e-commerce store, a SaaS platform, or a membership site), this method is for you.

How the User ID Works

The process is straightforward in concept:

1. When a user logs into your website, your system generates or retrieves a unique ID from your database (like CustomerID: 1138 or User_UUID: A4B2-C8D3-E6F7). This ID must be unique, persistent, and not personally identifiable.
2. You then pass this User ID to Google Analytics alongside all their pageviews and events.
3. GA4 uses this ID to unify all activity from that user, regardless of whether they switch from their laptop to their phone.

Step-by-Step Implementation Guide

Implementing this requires a small change to your website's code or Google Tag Manager setup.

1. Generate and Assign a User ID

Your web developer will need to ensure that once a user logs in, a unique, non-PII ID is available to be pushed to the data layer or can be grabbed by JavaScript. A database ID number is a perfect candidate. For example, in a Shopify store, every customer has a unique Customer ID. Avoid using email addresses at all costs.

2. Sending the User ID to GA4

How you send the ID depends on your GA4 installation. Here are the two most common methods:

Using gtag.js (Global Site Tag):

You’ll need to add one line to your existing GA config snippet. This command should be fired after a user has successfully logged in.

gtag('config', '[Your-Measurement-ID]', {
  'user_id': '[USERS_UNIQUE_ID]'
}),

Simply replace [YOUR_MEASUREMENT_ID] with your GA4 Measurement ID (it looks like G-XXXXXXXXXX) and [USERS_UNIQUE_ID] with the variable that holds the user’s ID from your backend.

Using Google Tag Manager (GTM):

GTM is the more flexible and recommended approach.

• Push the ID to the Data Layer: After a user logs in, your developer should add a snippet to push the ID to the data layer, like this:
• Create a Data Layer Variable in GTM: In your GTM workspace, go to Variables > New. Select "Data Layer Variable" as the type. For the "Data Layer Variable Name," enter user_id. Save it as "dlv - user_id".
• Update a configuration or Event Tag: The easiest way is to modify your main Google Tag - GA4 Configuration Tag. Click Shared event settings > 'Set globally for settings used across all events (recommended)':

Graphed

Still Building Reports Manually?

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

Watch the Demo

3. Configure Your GA4 Reporting Identity

This final step tells GA4 to prioritize the User ID when identifying users.

• In your GA4 property, go to Admin > Data Streams > Reporting Identity.
• Choose the "Observed" option.
• Ensure that "User-ID" is checked and placed first in the sequence.

Method 2: Using the Client ID as a Custom Dimension

What if you don't have a login system? You can still track individual devices or browsers using the Client ID.

The Client ID is a unique, randomly generated identifier that Google Analytics automatically creates and stores in a user's browser cookie. It’s what GA uses by default to distinguish one anonymous user from another. However, if a user clears their cookies or switches devices, a new Client ID will be generated.

By default, you can't see the Client ID in standard GA4 reports. But you can capture it and send it as a custom dimension to make it visible.

Step-by-Step Implementation Guide (GTM)

This is easiest to set up in Google Tag Manager.

1. Capture the Client ID with a GTM Variable

Someone at Google created a simple way to reliably retrieve the Client ID.

• In your GTM Workspace, navigate to Variables > New.
• Choose "Custom JavaScript" as the variable type.
• Paste the following code into the box:
• Name this variable cjs - Client ID and save it.

2. Create a User-Scoped Custom Dimension in GA4

Next, you need to tell GA4 to expect this new piece of data.

• Go to your GA4 property and navigate to Admin > Data Streams > Custom dimensions.
• Click "Create custom dimensions."
• Set the following values:
• Save the dimension. It may take up to 48 hours for data to start populating for this new dimension.

3. Send the Client ID with Every Event

Finally, you need to send the value from your new GTM variable to GA4.

• In GTM, go to your Google Tag - GA4 Configuration Tag.
• Click Shared event settings > Set globally for settings used across all events (recommended).
• Under User properties, click "Add parameter" and add a new row. Set the "Property name" to client_id (must match what you entered in GA4). Set the "Value" to {{cjs - Client ID}}.
• Save and publish your GTM container changes.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Analyzing Individual User Behavior

So, where do you find this data? The best place is in the Explorations section of GA4.

Using the User explorer

GA4 has a built-in technique for this kind of analysis.

1. In your GA4 property, go to Explore in the left-hand navigation.
2. Select the "User explorer" template if available or start from "Blank".
3. If creating blank, in the Exploration tab for "Technique," choose “User explorer". In a column, drag 'event name'. Then you can see each individual event for that user. Scroll down to see additional users. Now you'll see a list of individual App-instance IDs or Stream names, along with every action they took in chronological order.
4. Filtering by your ID: To find a specific user, add a "Filter" at the bottom of the "Tab Settings" column. If you implemented Method 1, create a filter for the "User ID" dimension. If you implemented Method 2, after about 24-48 hours, you'll see "Client ID" in the list of dimensions to filter by. Enter the specific ID you’re searching for.

Once you click into an individual user, you get a full, timestamped event stream. You can see every page_view, click, form-submission-event, begin_checkout, and purchase that user made. This timeline is invaluable for debugging e-commerce funnels, understanding content consumption patterns, and pinpointing where users drop off.

Final Thoughts

Tracking individual users in Google Analytics 4 unlocks a level of analysis that isn't possible with aggregated reports alone. Whether you use the robust User ID feature for logged-in users or the Client ID for anonymous traffic, you can stitch together complete customer journeys, diagnose problems, and find powerful opportunities for optimization - all while fully respecting user privacy.

While looking at GA4 data is powerful, the real insights come when you connect a user’s website behavior to their purchase history in Shopify or their deal stage in HubSpot. Instead of manually pulling data from each platform and trying to match user IDs in a spreadsheet, we built Graphed to automate this entirely. By connecting your sources, you can ask plain-English questions like, "Show me the journey of users from our latest Facebook campaign who purchased a specific product," and get a unified, cross-platform report in seconds. It allows you to see the full picture, not just disconnected pieces.