How to Track User ID in Google Analytics 4

Tracking users accurately across multiple devices and sessions in Google Analytics can feel like trying to solve a puzzle with missing pieces. You know someone browsed your products on their phone during a lunch break and later purchased on their laptop, but GA4 often sees them as two different people. This is where the User-ID feature comes in. This article will walk you through exactly how to implement User-ID tracking in Google Analytics 4 to get a unified, more accurate view of your customer's journey.

Graphed

Still Building Reports Manually?

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

Watch the Demo

What’s Wrong with Default GA4 User Tracking?

By default, Google Analytics 4 identifies users in a few ways, primarily through a Device ID (also called a Client ID) and Google Signals. The Device ID is a unique, random identifier stored in a user's browser cookie. This works well enough for tracking a single user's actions during one session on one device.

The problem arises when that user’s context changes:

• They switch devices: A person browsing on their mobile phone and later on a desktop computer will get two different Device IDs. GA4, out of the box, will count them as two separate users.
• They use a different browser: Each browser on the same device will have a unique Device ID.
• They clear their cookies: When a user clears their browser cookies, the old Device ID is deleted. The next time they visit your site, a new one is generated, and they look like a brand new user.

While Google Signals (which uses data from users logged into their Google accounts) helps stitch some of this together, it only works for a subset of your users and doesn't solve the core problem completely. Relying on default tracking methods leads to inflated user counts and a fragmented understanding of how people interact with your business over time.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Understanding the GA4 User-ID Feature

The User-ID feature is Google's solution to this cross-device tracking problem. It allows you to assign your own stable, non-personally identifiable ID to a user once they authenticate, typically by logging into their account on your website or app.

Here’s what makes it so powerful:

This ID is generated and controlled by you. It’s usually the unique ID you already assign to users in your own customer database. Because this ID is tied to their account, not their browser or device, it remains constant. A user with the ID "customer12345" will always be "customer12345" whether they log in from their phone, tablet, laptop, or work computer.

A Crucial Note on Privacy: You must not use personally identifiable information (PII) like email addresses, names, or phone numbers as the User-ID. The ID should be an anonymous string of numbers and/or letters that only has meaning within a system you control.

How GA4 Prioritizes Tracking Methods

To really appreciate the value of User-ID, it helps to understand GA4’s identity hierarchy. When trying to identify a user, GA4 checks for available identifiers in a specific order:

1. User-ID: This is the gold standard. If a User-ID is present for an event, GA4 uses it above all else to identify the user who performed the action.
2. Google Signals: If no User-ID is passed, GA4 looks for Google Signals data. This helps connect devices for users who are logged into their Google account and have ad personalization turned on.
3. Device ID (Client ID): If neither of the above is available, GA4 falls back to the standard browser cookie ID.
4. Modeling: For users who don't consent to cookies, GA4 uses behavioral modeling to estimate user and session data.

By implementing User-ID, you ensure that for your most valuable, logged-in users, you’re using the most reliable identification method available.

Step-by-Step Guide to Implementing GA4 User-ID

The most common and flexible way to set up User-ID tracking is through Google Tag Manager (GTM). This process involves collaboration with a developer to push the ID to the website's data layer, followed by a few simple configuration steps inside GTM.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Prerequisite: Generate and Expose the User ID

Before you can do anything in Google Tag Manager, your website needs to be able to do two things:

1. Generate a unique, persistent, and non-PII ID for every user when they create an account.
2. Make this ID available on a page's dataLayer after the user successfully logs in.

This is a task for your web developer. You can ask them to push the User-ID to the data layer using a code snippet like this, which should execute after a user authenticates:

window.dataLayer = window.dataLayer || [],
window.dataLayer.push({
  'event': 'login_success',
  'user_id': '[USER_ID_HERE]'
}),

Make sure they replace [USER_ID_HERE] with the dynamic variable that holds the actual signed-in user's ID.

Step 1: Create a Data Layer Variable in GTM

Once the User-ID is available in the data layer, you need to "catch" it with a variable in GTM so you can use it in your tags.

• In your Google Tag Manager workspace, navigate to Variables from the left-hand menu.
• Under the “User-Defined Variables” section, click New.
• Give your variable a descriptive name, like DLV - User ID.
• Click on Variable Configuration and choose Data Layer Variable as the variable type.
• In the "Data Layer Variable Name" field, enter user_id. This must match the key you used in the data layer push code exactly ('user_id').
• Leave the other settings as default and click Save.

Step 2: Update Your GA4 Configuration Tag

Now, you need to tell your main GA4 tracker tag to send this newly captured User-ID along with all of its data pings to Google Analytics.

• Navigate to Tags in your GTM workspace.
• Find and click on your main Google Tag. This is often named something like “GA4 Configuration.”
• Click on Configuration settings.
• Under the “Configuration parameters” section, click Add parameter.
• For the Row Name, type user_id.
• For the Value, click the lego brick icon and select the Data Layer Variable you created in the previous step: {{DLV - User ID}}.
• Click Save to save the changes to your tag.

Step 3: Test and Publish Your Changes

Before making your changes live, it’s essential to verify everything is working as expected.

• In GTM, click the Preview button in the top right corner.
• Enter your website URL and click Connect. Your site will open in a new tab with the GTM debug panel connected.
• On your website, go through the login process with a test account.
• After you log in, switch back to the GTM Preview tab. Find your GA4 Tag firing on the timeline on the left.
• Click on the tag, and in the details pane, look for the user_id parameter being sent to Google Analytics. You should see its value is the test user's ID.
• You can also check GA4's own DebugView (found under Admin > DebugView) to see the incoming events and verify the user_id user property is correctly associated with them.

Once you’ve confirmed it's working properly, go back to GTM, click Submit, and publish your container.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Using Your New User-ID Data in GA4

So, where can you see the benefits of your hard work? It’s important to know that GA4 will not explicitly show the individual User-ID values in standard reports to protect user privacy. Instead, you'll see the impact in three main ways:

1. More Accurate User Counts: All of your standard reports (like Traffic acquisition, Engagement reports, etc.) will now be based on a de-duplicated user count. You're no longer over-counting every time someone switches devices. This is the biggest, most immediate benefit.
2. Updated Reporting Identity: In your Admin settings under Reporting Identity, you can see the "Observed" method, which now blends User-ID, Google signals, and device data for the best possible user de-duplication.
3. Exploration Reports: The Explorations tool is where you can do deeper analysis. You can build segments and comparisons based on whether a user was signed in. For example, you can create an exploration to compare the conversion rates or average purchase value between logged-in users and anonymous visitors. You simply add the "Signed in with user ID" dimension (which returns 'yes' or 'no') to your report.

For even more granular, user-level analysis — where you can trace the entire event stream for a specific, anonymized user_id value — you need to connect GA4 to BigQuery. This is a more advanced step but unlocks the full potential of your new, cleaner user data.

Final Thoughts

Implementing User-ID tracking is a game-changer for getting reliable data out of Google Analytics 4. It graduates your account from simple session-counting to a genuinely user-centric analysis tool, giving you a full-story view of how people engage with your business across their entire journey, regardless of the device they use.

While GA4's reporting provides the raw materials for analysis, turning that unified data into clear-cut answers can still involve building complex reports in the Explore tab. To bridge that gap, we built Graphed . We simplify the entire process by connecting directly to your Google Analytics account and letting you create dashboards and get insights just by asking questions. Instead of clicking and dragging dimensions, simply ask "compare LTV for logged-in users vs guest users" or "map the funnel for users who visit from both mobile and desktop" and get the visualization built for you, in real-time.