Remove unspecified permanently | Community
Skip to main content
jane_12
Level 3
Apr 17, 2023 7:33 AM UTC
Solved

Remove unspecified permanently

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.
yuhuisg
yuhuisgAccepted solution
New Participant
Apr 17, 2023 11:48 AM UTC

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.

View reply

10 replies

yuhuisg
yuhuisgAccepted solution
New Participant
Apr 17, 2023 11:48 AM UTC

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.

Translate
jane_12Author
Level 3
Apr 17, 2023 12:54 PM UTC

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

Translate
Jennifer_Dungan
Jennifer_Dungan
Level 2
Apr 17, 2023 1:35 PM UTC

What is your eVar tracking? Is it something that makes sense in the context of your Mobile App Lifecycle Metrics? You could in theory add a processing rule to add a value to your eVar on your lifecycle calls. But ONLY if this makes sense... Lifecycle is a special action that tracks information such as Launches, Upgrades, Crashes, Days Since Last Visits, Days Since Last Upgrade, etc.

 

ADBINTERNAL:Lifecycle should always correspond with "Launches" metrics (other metrics will also pair with this event, but launches should be completely 1 to 1 (you can confirm this by looking at ADBINTERNAL:Lifecycle with a column for Occurrences and Launches (they should match)

 

So IF adding an eVar value to your lifecycle is what you want... you can create a Processing rule with the condition:

 

a.launchevent is set

 

OR, you just do what @yuhuisg suggested, and uncheck the "Show unspecified" checkbox.

Translate
Terms & ConditionsAccessibility statement

Loading footer...