Is there a limit on the number of user properties?

There is a limit of 25 registered user properties per App+Web property, and a limit of 100 registered user properties per App+ Web 360 property

If you are unsure what user properties are, fret not – we’ve got you covered. Learn about them here.

What are user properties?

User properties are attributes that can be used to describe segments of your user base, such as geographic location etc, pretty much like dimensions, but user-scoped. There are currently a number of default user properties such as age, app version/store, country, device brand/category/model, first open time, gender, interests, language, new/established and OS version. You can also add up to 25 uniquely named user properties per App+Web property.

Here is the full list of default user properties:

One thing you must understand about user properties, is that you need to preset them, and register or create them in the interface before you can use them.

There is also a limit on the number of user properties of 25 registered user properties per App+Web property, and a limit of 100 registered user properties per App+ Web 360 property.

Can user properties names contain spaces?

User Property names can be up to 24 characters long; may only contain alphanumeric characters and underscores (“_”), and must start with an alphabetic character.

On Firebase, Project names can be up to 30 characters long, and may contain letters, numbers, spaces and these characters: -!'”. Spaces are automatically turned into “-“.

Custom metrics and custom dimensions in App + Web

There are no custom metrics nor custom dimensions in App + Web per se, however, there are equivalent called parameters and user properties.

Where it used to be a hit-scoped custom dimension, you will utilise parameters in the App+Web property and for user-scope dimensions, you will utilize user properties. It must be noted that user properties will require a code to be injected into the web/app.

For App + Web, you can send up to 25 custom parameters per hit sent and similar to current Google Analytics set up, custom parameters are not retroactive which means that it will only collect data once the parameter is enabled.

Where can I see custom dimension data / set up?

Currently there doesn’t seem to be the same sort of access to configure parameters like the dimension and metric setup within the ‘Property Settings’ in the UA version. This is possibly due to it not being available yet or Parameters being limited to Hit and User scopes and not requiring setup. See below for User Properties where configuration is possible.

What parameters are configured to send to the property?

To understand what parameters are being set you will need to navigate to your GTM setup and look in there. Under each tag – like in the screenshot for the 404 error event below – you can see which parameters are being set.

Configuration of an event in GTM

User Properties

Though there are user properties that can be configured. These are the same as User Scoped Custom Dimensions that you find in Universal Analytics.

User Properties can be found under the Configure Section in the left hand side panel

Where to find User Properties

There are just two configuration options per User Property – Name and Description.

Configuration Options

Note User Property Names can’t have spaces and descriptions are limited to 150 characters.

Error from attempting to add in User Property with spaces in name
User Property successfully created without using spaces.