What is User Property in Google Analytics 4?

Cody Schneider8 min read

Tracking what users do on your site is one thing, but understanding who those users are is what separates basic analytics from powerful business intelligence. This is exactly what User Properties in Google Analytics 4 are designed for. This article will show you what GA4 user properties are, how to set them up, and how you can use them to better understand your audience.

GraphedGraphed

Still Building Reports Manually?

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

Watch Graphed demo video

What Exactly Is a GA4 User Property?

Think of a User Property as a descriptive label that you attach to a specific user. It describes a characteristic or an attribute of that person that doesn't change often. These are the details about the user themselves, not the actions they take on your site.

For example, you could use a User Property to track:

  • Their subscription level (e.g., 'free_tier', 'premium_plus')
  • Their job industry (e.g., 'tech', 'healthcare', 'retail')
  • Whether they are a new or returning customer
  • The company size they work for (e.g., '1-50', '51-200', '201+')

The key here is that these attributes are "sticky." Once you define a user property for someone - say, you label them as a 'premium_plus' subscriber - that label sticks to them and is associated with every single event they trigger from that point forward, until their subscription status changes.

This allows you to segment your users into meaningful groups to see how different types of customers interact with your website or app. Do premium users engage more? Do users from the tech industry view different pages than users from retail? User properties make answering these questions possible.

GraphedGraphed

Still Building Reports Manually?

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

Watch Graphed demo video

User Properties vs. Event Parameters: What's the Difference?

This is a common point of confusion when first getting started with GA4. The distinction is simple but crucial:

  • User Properties describe the user. They answer the question, "Who is this person?"
  • Event Parameters describe an event or action. They answer questions like, "What did they do?" or "How did they do it?"

Let's use an e-commerce example. A user buys a pair of shoes.

User Property Examples:

  • member_level: 'gold' (This describes who the user is)
  • shoe_size_preference: '10' (This describes a relatively static attribute of the user)

Event Parameter Examples for the 'purchase' event:

  • item_name: 'Running Shoes X-100' (This describes the item in this specific purchase)
  • price: '99.99' (This describes the price for this specific transaction)
  • coupon_used: 'SUMMER20' (This describes a detail specific to this one purchase action)

The user's member_level remains 'gold' for all their actions, while the item_name and price are specific only to that one purchase event. By using User Properties, you start to build a rich profile of your users, which you can use for deeper analysis and targeted marketing.

Automatically Collected User Properties

Before you even set up your own custom properties, Google Analytics 4 automatically gathers a few for you if you enable Google Signals. These include demographic and interest data drawn from users who are signed into their Google accounts and have ads personalization turned on.

These automatically collected properties include:

  • Age: The user's age bracket (e.g., 18-24, 25-34).
  • Gender: The user's gender.
  • Country: The country where the user is located.
  • Interests: The user's interests based on their Google activity (e.g., "Shoppers", "Sports Fans").
  • Language: The language setting of the user's browser.
  • New/Established: Identifies if a user has visited in the last 7 days.

While useful for high-level comparisons, the real power comes from creating your own custom properties that are specific to your business needs.

How to Set Up Custom User Properties in GA4

Creating your own user properties is a two-part process. First, you need to "register" the property within the GA4 interface. Second, you need to actually send the data from your website to GA4. It is essential to remember that just doing the first part won't make any data appear.

Step 1: Register the User Property in the GA4 Interface

Registering the property tells GA4 to expect this data and makes it available for you to use in reports and audience-building. Without this step, GA4 will receive the data but you won't be able to do much with it.

  1. Navigate to your Google Analytics 4 property.
  2. In the bottom-left, click on Admin.
  3. In the Property column, click on Custom definitions.
  4. Select the User properties tab and click the Create user property button.
  5. Fill out the configuration panel:
  6. Click Save.

That's it for part one. GA4 is now ready to listen for your new custom property. Now, let's get you sending it.

GraphedGraphed

Still Building Reports Manually?

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

Watch Graphed demo video

Step 2: Send User Property Data to GA4

You have two primary methods for sending user property data: Google Tag Manager (most common and recommended) or the global site tag (gtag.js) directly on your website.

Method 1: Using Google Tag Manager (GTM)

GTM is the most flexible way to manage your GA4 tracking. You can set up your user properties to fire based on specific events, like a user logging in or viewing a specific page.

Let's imagine you want to set a plan_type user property when someone logs into your service.

  1. Open your GA4 Event Tag: In GTM, navigate to the tag that sends data to your GA4 property. Often this is a "GA4 Configuration" tag or a specific "GA4 Event" tag.
  2. Add a User Property: In the tag configuration, find and expand the User Properties section.
  3. Click "Add Row":
  4. Set a Trigger: Attach a trigger to this tag that fires when the user property should be set. For our example, this could be a 'successful_login' custom event that fires after a user signs in.
  5. Save and Publish: Save your tag, test it using GTM's Preview mode, and then publish your container.

Method 2: Using the Global Site Tag (gtag.js)

If you aren't using GTM, you can set user properties by adding a small piece of JavaScript to your site. This is done with the set command.

To set the same plan_type property, you would add this snippet to your website's code:

<script>
  gtag('set', 'user_properties', {
    'plan_type': 'premium' 
    // You can add more properties here
    // 'customer_industry': 'tech' 
  }),
</script>

This code should be placed on pages where the user's status is known (e.g., after they've logged in). The value ('premium' in this example) should be dynamically populated by your server or front-end framework based on the user's actual plan.

Crucial Considerations for User Properties

Before you go all-in, keep these limitations and behaviors in mind:

  • Limit of 25: You can create a maximum of 25 custom user properties per GA4 property. Choose them wisely to track your most important segments.
  • They Are Not Retroactive: User properties only apply to data collected after they have been implemented. You can't apply them to your historical data.
  • "Stickiness" is Key: The "sticky" nature of user properties is powerful but important to understand. If you set plan_type to 'premium' for a user, every event they trigger afterward - page_view, scroll, click, etc. - will be associated with that property until it's changed.
  • Can You Unset Them? Yes. To remove a user property for a user, you must pass a value of null. For instance, gtag('set', 'user_properties', {'plan_type': null}), would unset it. This is useful for when a user logs out or cancels a subscription.

Using Your New User Properties for Analysis

So, you've set everything up. What's next? This is where the fun begins. With user properties properly configured, you can start segmenting your users and discovering valuable insights.

GraphedGraphed

Still Building Reports Manually?

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

Watch Graphed demo video

Build Audiences for Remarketing

One of the most powerful uses for user properties is building highly specific audiences. You can create an audience of all users where the User Property plan_type exactly matches 'premium' and then use this audience for targeted Google Ads campaigns, offering them exclusive upsells or content.

Create Comparisons in Standard Reports

In most standard GA4 reports (like Pages and screens or Traffic acquisition), you can add a comparison. At the top of the report, click "Add comparison" and you can build a filter based on your new user property. This allows you to easily compare the behavior of two different segments side-by-side, such as 'free' users versus 'premium' users.

Dive Deep with Explore Reports

In GA4's Explore section, you can use your custom user properties as dimensions in more advanced reports like Funnel explorations or Free-form reports. For example, you could build a report showing the value of new user-scoped revenue, broken down by your custom customer_industry property. This helps you identify which industries your most valuable customers come from.

Final Thoughts

User properties in GA4 bridge the gap between anonymous data and a true understanding of your users. They transform your analytics from a simple event log into a collection of user stories, allowing you to segment, compare, and personalize the user experience in powerful ways.

Mastering this part of GA4 can feel complex, but setting everything up and running an analysis is well worth the effort. At Graphed, we streamline this entire process. By connecting all your data sources like Google Analytics, Shopify, and your ad platforms in one click, we enable you to instantly build dashboards and ask questions about your data in plain English - no technical skills or report-building required. You can go from wondering how your different customer segments behave to getting a complete answer in just a few seconds.

Related Articles