Hits not in Debugger Visible for an eVar Persistent | Community
Skip to main content
skatofiabah
Level 5
August 5, 2024
Question

Hits not in Debugger Visible for an eVar Persistent

  • August 5, 2024
  • 1 reply
  • 1342 views

Hi All,

 

I have an eVar that visibly shows up in the debugger on the landing page from a paid ad. That eVar is set to persist until the end of the visit. I currently have a segment that looks at all hits for a specific tracking code in the eVar. Is the hit segment capturing all hits that persist after my landing page hit, even if the value is persisting and not visibly showing up in a debugger because it "persists" until the end of the visit in the backend?

 

Thanks!

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

1 reply

Isha__Gupta
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
August 6, 2024

Hi @skatofiabah ,

From what I am understanding, you have created a hit level segment with tracking code equals let's say "abc". If you are looking to query visit level data, you would have to change the segment level to visit instead of hit. An eVar although persists for the visit, that typically provides binding of values with other page elements. So if you are looking to look at the value of that eVar with visit level values, you need a visit level segment to expand the scope.

If this doesn't answer your query, can you please provide additional information as to -
1. What report are you trying to build?
2. Segment definition screenshot (if possible)

skatofiabah
Level 5
August 6, 2024

Hi @isha__gupta ,

 

Thanks for reaching out. So what I'm saying is eVar "abc" is a tracking code to identify a particular campaign. It visibly hits in the adobe debugger when a user lands on the homepage from the paid ad. In admin, it is set to persist on a visit, meaning if another tracking code happens in the same visit, the 2nd will overwrite the first. So, if I land on page 1, "abc" eVar1 shows in the debugger, but on subsequent hits, it doesn't show in the debugger, but it persists because of the rule. I think if this was set to the visit, it could capture other tracking codes we don't want. Let's say a user comes from the ad that has tracking code "abc" evar1, but later in the visit, then come from another ad. Adobe will count both in the same visit because Adobe is time bound assuming they happen relatively close to each other. So I think it needs to be on the hit level to make sure it says solely with those evars and tracking codes. Let me know if I'm wrong in my thinking as I read your post thoroughly.

 

Thanks!

Isha__Gupta
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
August 6, 2024

Hi @skatofiabah ,

So what you are saying is, you want your eVar to be populated only if your user is coming through Paid Ad? You don't want the eVar to be overwritten with any other channel tracking value within same visit?

If you have configured Marketing Channels, you can achieve this through below.
1. Use Marketing Channel Processing rules to restrict eVar receiving value when the channel is paid.
2. Use Attribution IQ in Adobe Analytics to look at various attribution models.
3. Prevent default overriding of Channels by any other channels except Paid channels.