What is the best method for segmenting out inflated data?

[Yohan_khan00]

I have discovered an instance where two metrics have inflated numbers. I have verified this using "Custom Link Instance" which shows the correct numbers for the traffic. 

I want the inflated metrics to show the values we have for the "Custom Link Instance" metric.  How should I go on about creating this segment to filter out the inflated data and update the metrics to the correct values? 

I have tried to use calculated metrics where the difference between [Custom Link Instances - Metric X] is greater than 0 but that filters out the data. 

Any help would be appreciated. 

[Jennifer_Dungan · Accepted solution]

When you say inflated data, can you elaborate?

Are you setting an eVar on your action? I am willing to bet that eVar is set to Visit level expiry, which means that once it's set, that value is maintained on all hits (page views and actions) until the end of the visit or the eVar is set with a new value....

First and foremost, you should evaluate what you are using your eVars for, and what the expiry should be...

To borrow from a friend:

• eVars are like chewing gum on the sidewalk, once you step on it, it sticks to your shoe and follows you around until it's dislodged
• props are like a banana peel, you step on it with immediate action, then it's gone and you continue on forgetting about it

Now, since you have that issue, each eVar also has an "Instance" metric of itself... These will be colour coded green like other metrics, and will show your eVarX name followed by "Instance"... (eg. eVarX is called "colour", the the instance will be called "colour instance")

So in this scenario:

• Page 1
  • eVar not set yet
• Action A
  • eVarX is set with "value"
  • Instance of eVarX is incremented
  • Custom Link Instance is also incremented
• Page 2
  • eVarX maintains "value" (since the value is set to expire at the end of the visit)
  • No Instance of eVarX (since the value is not directly set)
• Action B
  • eVarX is set with "someothervalue"
  • Instance of eVarX is incremented
  • Custom Link Instance is also incremented

so eVarX has "value" for both Action A and Page 2, and "someothervalue" for Action B and all hits after that until the end of the visit or the next action to set an eVarX value

You can create a "global" segment this way:

HIT level

           eVarX exists

           AND

           eVarX Instance exists

This will show any value captured in eVarX, but only where the instance of the eVar also exists.