Remove unspecified permanently | Community
Skip to main content
J
jane_12
Level 3
April 17, 2023
Solved

Remove unspecified permanently

  • April 17, 2023
  • 1 reply
  • 1804 views

How do we remove unspecified completely from the reports?

Apart from unchecking 'include unspecified' in the report?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by yuhuisg

You "remove" it completely by ensuring that each and every hit has a value for that dimension, whether set in the beacon or persisted from previous beacons.

On the other hand, if you mean that you simply don't want to see it in your report, i.e. hide it, then in your Freeform table, click the filter icon for your dimension, and uncheck the "Show unspecified" checkbox.

1 reply

yuhuisg
Community Advisor
yuhuisgCommunity AdvisorAccepted solution
Community Advisor
April 17, 2023

You "remove" it completely by ensuring that each and every hit has a value for that dimension, whether set in the beacon or persisted from previous beacons.

On the other hand, if you mean that you simply don't want to see it in your report, i.e. hide it, then in your Freeform table, click the filter icon for your dimension, and uncheck the "Show unspecified" checkbox.

J
jane_12Author
Level 3
April 17, 2023

We have made sure that each and every hit has a value for that dimension, whether set in the beacon or persisted from previous beacons. But still we see unspecified and when we break it with custom link it shows the value ADBINTERNAL:Lifecycle

J
jane_12Author
Level 3
April 26, 2023

Ok, you probably won't have either of those on the LifeCycle... that is the very first call upon opening the app, and most of that info is still processing...

 

Also, new app users wouldn't have that data at all... surely even IF your app requires login, you would have page views on a login screen without the screen name/user id....  it's impossible to have every single instance be populated.... (unless you are populating placeholder values like "not logged in")


So we have only two success events and when we use those 2 metrics we don't see unspecified. Unspecified values only appears when visits and unique visitors metrics are used.

Terms & ConditionsAccessibility statement

Loading footer...