Junk Data in eVar | Community
Skip to main content
ArlemGabriel
ArlemGabriel
Level 2
March 21, 2022
Solved

Junk Data in eVar

  • March 21, 2022
  • 2 replies
  • 2978 views

Hi everyone! 

Let me explain the issue first, supposed that you have an eVarX which is going to store the UTM parameters in other words it will store campaign data.

 

1. The problem is that sometimes is sending junk data to adobe analytics it seems to be some hardcoded values. This is happening in a new property that I created from scratch and I didn't set that hardcoded variable in the set variables section for the global variables rule. I also checked the processing rules but I don't see anything being set in there. Any thoughts about any other place were evars can be set with default values? (This values were set by another person in the company which is not longer with us, so I don't know what he did and where)

 

2. I decided to use Campaign OOB but sometimes is sending %campaign% as default value. Is there any way to change the default value of variables OOB in adobe?

 

 

 

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

So that's the thing... Since I created the property from scratch I have never set an element called campaign but just to be cautious I searched the element in the property and nope, there isn't any element with that name set on the property. So, where does that data come from? 😅


In that case, you might need to investigate this from the reverse. Starting with your AA report, break down the "%campaign%" Tracking Code values by Page and/or Custom Link (use 2 tables). Do you see any pattern where this "%campaign%" is being set with certain Pages and/or Custom Links only? If so, then that might indicate that with those hits, your Launch property isn't being used, so something else (e.g. an old implementation) is setting this value.

2 replies

Hyder_Ziaee
Adobe Employee
Hyder_ZiaeeAdobe Employee
Adobe Employee
March 22, 2022

Check your Launch implementation. In some environment it is using the data element "campaign" but that has not been published to that environment. If Launch is unable to find the data element, it will read it as a literal value - "%campaign%

 

If you are comfortable, you can share the URL, and can check the launch library 

yuhuisg
Community Advisor
yuhuisgCommunity Advisor
Community Advisor
March 23, 2022

For Q1:

Are you sending data to an existing report suite in AA or a new one? You only mentioned that you had setup a new Launch property, but didn't say about where the data is being collected. If you're sending to an existing report suite, then it could be that some other website is sending data to the same eVar with the so-called hardcoded values.

For Q2:

Have you created a corresponding data element called "campaign" in your Launch property?

ArlemGabriel
ArlemGabrielAuthor
Level 2
March 23, 2022

We have a lot of portals and all the data being collected with Adobe goes to the same report suite and yes, all of those portals are sending that campaign variable to the same report suite. To give you more context of the testing that I did yesterday.

1. eVar1 was storing the campaign data with junk data in Property1.

2. Property2 was created from scratch using Campaign OOB variable to store campaign data avoiding junk data.

3. Removed eVar1 completely from Property1.

4. Created a processing rule to override eVar1 with the values stored in Campaign OOB variable.

 

Results in Property2:

Campaign OOB Variable is showing next values:

Unspecified

%campaign%

UTM Parameters

 

eVar34 is showing next values:

Unspecified

%campaign%

UTM Parameters

||no value||no value

 

Which doesn't make sense to me because we are overriding the eVar1 with Campaign OOB, we should be seeing the same values in both of them and like I said, eVar1 was removed from all places in the property1 and in property2 was never set.

 

Also, I want to point to another thing. We have an eVar in which we are storing the name of the property so if you take ||no value||novalue and you breakdown using the Launch Property evar you'll see that belongs to Property2. Which again it doesn't make sense because eVar1 isn't being populated in that property only Campaign OOB is being set in that property.

yuhuisg
Community Advisor
yuhuisgCommunity Advisor
Community Advisor
March 24, 2022

Using Launch's global search (the search feature at the top of the UI), try searching Property 2 for components that are using eVar1. It could be that eVar1 is being set unexpectedly in another Rule.

(BTW I assume your problematic eVar is "eVar1", not "eVar34". It's probably a typo there. 😀)

In AA, after breaking down eVar1 by the Launch Property eVar, break it down further by Page and/or Custom Link and/or Download Link and/or Exit Link to see if there are any clues there.

Also, just wondering, what do you mean by "Campaign OOB" in Launch? AFAIK there's no such data element or component called that in Launch. A screenshot might help to illustrate this. 😉

Terms & ConditionsAccessibility statement

Loading footer...