How to use event, evar and prop adobe launch | Community
Skip to main content
A
AronoeleS
Level 2
September 28, 2021
Solved

How to use event, evar and prop adobe launch

  • September 28, 2021
  • 2 replies
  • 8606 views

I have created a rule to track cta click and set these information:

 

eVar11: [v11] CTA Name

 

prop7: [prop7] CTA Name

 

event19: [e19] All Click CTA

 

if I check in adobe analytics report I don't understand the numbers, e.g:

 

 [v11] CTA Name (dimension) | Occurences |   [v11] CTA Name Instances (metric) |  [e19] All Click CTA (metric)

abcdname                               | 60.000        |   7.000                                                 | 30.000

 

[prop7] CTA Name (dimension) | Occurences |   [v11] CTA Name Instances (metric) |  [e19] All Click CTA (metric)

abcdname                                 | 7.000           |   7.000                                                | 30.000

 

I don't understand when I have to use prop var and event. If I just want to track click cta hit numbers split by cta name, the right setting is to set a prop and then match this prop with occurences, is it right? I really do not understand the aim of events.

    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 Brian_Johnson_

    @aronoeles - I don't know that I answered your final question: 

     

    "If I just want to track click cta hit numbers split by cta name, the right setting is to set a prop and then match this prop with occurences, is it right?"

     

    You can go a lot of ways here. The way you suggest in your question is one, for sure.

     

    Traditional tracking would likely include an eVar (last touch, either hit or visit expiration) to capture the CTA name and a success event (counter, count every time) to track CTA clicks. With the capabilities of Workspace, you could replace the eVar with a prop for the same use. Whether you go with an eVar or a prop, your report would show the CTA Name (prop or eVar) as the dimension and CTA Click (event) as the metric. 

    2 replies

    Pablo_Childe
    Community Advisor
    Pablo_ChildeCommunity Advisor
    Community Advisor
    September 28, 2021

    So Adobe evar , prop and events are tricky so hopefully I can explain it too you in a useful way.

     

    Prop think of it as a variable it will happen once on a pageview hit. So lets say for each pageview you define a prop to see if a person is logged in. Prop populates or it doesn't.

     

    Evar think of it as a variable that can in essence follow the users across multiple pages in a given session. SO if we use logged in reference again. Page one set evar (user logged in), then when user goes to next page evar follows them etc for as many pages they visit in that session. Evars can follow users across pages basically.

     

    Event think of this as a particular action(s) you want to capture like its name sake think of some sort of event or series of actions that could be defined as an event. Lets say you want to capture a user visiting 2 pages in a specific order and on 2nd page they click a particular button call it a sign up event. It happens only after all criteria are met. It will only happen again if the user performs all steps again. they can happen multiple times for users and are not typcially session limited. They are typically count based meaning each time they happen the count increases by 1.

     

    hope this helps 

     

     

      P
      ppatel567
      November 2, 2022

      Hi - 

      Can one prop say prop60 be utilized multiple times with different name on the same page? lets say once to capture the original value and once to capture the final values? 

      Brian_Johnson_
      Brian_Johnson_
      Level 8
      September 28, 2021

      @aronoeles - Metrics can be confusing, no doubt. I'll see if I can clear up the confusion, though:

       

      eVar

      • An instance is counted each and every time the eVar is populated. So, if you see the value in the Analytics call, you will see the instance increase by 1 for that value
      • An occurrence is counted every time the eVar is populated and for each following hit where the value persists. For occurrences, you do not have to see the value in the Analytics call for the metric to increment
      • You do not have control over when or if either instances or occurrences increment

      prop 

      • Props do not have the same concepts of expiration and allocation that eVars have, so both instances and occurrences increment only when the prop is populated. So, if you see the value in the Analytics call, both instances and occurrences will increase by 1 for that value
      • You do not have control over when or if either instances or occurrences increment

      event

      • An event is a custom metric. It only counts/increments when the event is triggered in the Analytics call. You have complete control over when/if a custom event value increments (Unless specified, the default is to increment an event by 1 each time the it is present in the Analytics call)

      Using the sample data from your initial question as a guide, I would assume the following:

      • Out of 60,000 hits... (based on v11 occurrences)
      • "abcdname" was present in the analytics call 7,000 times (based on v11 instances AND prop7 occurrences)...
      • The "[e19] All Click CTA" event was triggered (present in the Analytics call) 30,000 times

       

        A
        AronoeleSAuthor
        Level 2
        September 29, 2021

        thank you for your all kindly replies.

        I try to create a simulation and fill an hypothetical report based on yours definitions. Just to understand all the possibility that Adobe offers and the best way to track a website with Adobe.

         

        hypothetical hits generated by a vistior on my website:

        ActivityServerCallTypeTraffic Var (prop)Conversion VarEventCustom Link
        Visitor lands on the homepages.t()PageName = Homepage   
        Click open pop up modal in homepages.tl()prop2 = popNameevar2 = popNameopenPopEvopenPop
        Click on 'go to SPA' in homepages.tl()prop2 = goNameevar2 = goNamectaClickEvctaClick
        SPA pages -> virtual Page1s.t()prop1 = Page1evar1 = Page1  
        SPA pages -> virtual Page2s.t()prop1 = Page2evar1 = Page2  
        SPA pages -> virtual PageTnks.t()prop1 = PageTnkevar1 = PageTnktnkPage 

         

        the reports that I could create in Adobe analytics

        evar2InstancesOccurencesEvent (openPopEv) Event (ctaClickEv) PageView
        popName11201
        goName12111

         

        evar1InstancesOccurencesEvent (openPopEv) Event (tnkPage) Pageview
        Page111202
        Page212203
        PageTnk13314

         

        Please correct the numebres if wrong.
        Thank you

        Brian_Johnson_
        Brian_Johnson_
        Level 8
        September 29, 2021

        @aronoeles - I think you're close, but I would expect slightly different numbers:

         

         

        In your sample/hypothetical session, you mixed page (s.t()) and link tracking (s.tl()) calls, which has an impact on Page View and Page Event metrics. Think of it as only s.t() calls increment Page Views and s.tl() calls increment Page Events.

         

        As I counted the different values, I made the assumption that your eVars were configured as most recent (last touch) with visit expiration. This makes a big difference in the eVar2="goName" Occurrences number because there are 4 calls that include that value. It first appears on the last s.t() call and persists through the last call of the session. This gives it 1 instance, but 4 total occurrences.

          Terms & ConditionsAccessibility statement

          Loading footer...