In DTM, when creating a Data element for URL parameter, we can select to remember the value for pageview, session, or visitor.
I then assigned this data element for URL parameter to an eVar which is set to expire on Visit in Adobe analytics. Is this going to contradict the expiration logic since DTM is remembering for "pageview" and Adobe Omniture has it expiration as "Visit".
Let's use a visit for example and say we're using evar1 which is set to visit expiration and last touch allocation. So, I go from Pages A > B > C > D >E Lets's say i set evar1 to X on page B and value Y on page D.
In the Data Here is what it will look like:
So, as you can see the evar is set on hit B and D, but because we persist it serverside (which is what reporting uses) is the post_evar1. So, if you look at the report we'll see evar1 value of x will have 2 page views and 1 visit and 1 instance. y will have 2 page views and 1 instance and 1 visit.
Yes hit would be very similar to page view (the equivalent option) it's just that it would expire after it's set always. Where with the page view paradigm it would mean that if there was a page call (s.t) and a link call s.tl() it would persist for the link call. But in the case with expiration of a hit, it will only be set once always.
Yes, this is what I assumed. However, I want the eVar to persist the value through the pageview and link tracking (since we have multiple links on the site) - so Adobe does not provide a solution to set the eVar to expire on a pageview?
so what happens if the data on client side is collected on pageview where its collecting different value on each page vs having a persistence of the visit in Omniture? Will the value in Analytics be only seen for the most recent (last touch attribution) until the visit expires although there are multiple values collected within a visit?