Skip to main content
jonathand258499
May 31, 2017 2:28 PM UTC
Solved

Is this a good use case for eVars?

Hi Guys,

I have an app where a user can select some number of widgets, and then act on those widgets. I'd like to be able to report on number of widgets people are acting on. Should I set an eVar with the number of widgets selected, and then fire off an event to track the action? Is the event necessary?

Thanks!

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Løjmann
    LøjmannAccepted solution
    Level 5
    Jun 2, 2017 5:06 PM UTC

    Hi,

    You won't need an event to see data populated to en eVar.

    But depending on what you need to see, you have a few different options.

    1) Just a total of all widgets - use en event (eventX=8 for example, if 8 widgets was seen/used at the same time)

    2) A row of 1, 2, 3, 4, 5 etc... use the eVar as you said

    You can of cause also do both

    Hope this makes sense?

    /Løjmann

    View in thread

    3 replies

    Løjmann
    LøjmannAccepted solution
    Level 5
    Jun 2, 2017 5:06 PM UTC

    Hi,

    You won't need an event to see data populated to en eVar.

    But depending on what you need to see, you have a few different options.

    1) Just a total of all widgets - use en event (eventX=8 for example, if 8 widgets was seen/used at the same time)

    2) A row of 1, 2, 3, 4, 5 etc... use the eVar as you said

    You can of cause also do both

    Hope this makes sense?

    /Løjmann

    Translate
      jonathand258499Author
      Jun 2, 2017 7:24 PM UTC

      Thanks Løjmann. Can you confirm that if I set an eVar I I'll need to s.tl() or s.t() for it to be recorded?

      Translate
      Løjmann
      Løjmann
      Level 5
      Jun 2, 2017 8:16 PM UTC

      Yes, the s.tl() function are a link-tracking call (not incrementing page view) and s.t() is a page-view tracking call (incrementing the page view metric).

      /Løjmann

      Translate
      Terms & ConditionsAccessibility statement

      Loading footer...