Why is custom size not visible in my report?

Question

This question is related to my previous question: What is the difference between the level of usage of Hit, Session and User in Google Analytics?

So, I tried to set the user size to the user level area, but the data still displays 0. Since the report is not in real time, I waited 2 days, but still the data remained 0. But when I changed it to the session level area, to the next day, data began to appear.

The use case that I want to track should be set to a user level area, but I don't know what is wrong. Is something missing?

Answer 1

Do you really need a user level area? If the user can switch his character type during the session, the user level measurement will not reflect any state of the world.

When using the dimension extension (custom parameters and indicators) there can be several: there is a checklist here:

• Configuration
  • Do you work with universal analytics?
  • Do you have a presentation representation of applications?
  • What is the name of the custom dimension used.
  • Do you use the Google Analytics SDK v2.x or higher
  • Is the user activity state of the dimension set to true (if it is false, you will have the dimension in the reports / segments, but no data).
  • How many measurements are you tracking?
• Collection
  • when you send custom size
  • What does your code snippet look like?
  • - analytics data buffered?
  • Are you sending all analytics data?
  • Did you exceed the meeting limit?
• Treatment
  • Your views have filters that prevent the display of custom dimensions. (IP development / testing is disabled when user data is displayed)
• Reporting
  • Changing the volume of user measurements will not lead to data processing - you will see results that are not accurate. Thus, you will need to limit dates to a period-only period

Finally, in real life, there is also tracking of the user level (cross device) through the useId function with its own configuration / assembly / processing / reporting, which will affect the session scheme, and incorrect configuration will affect the collection of user level data.