Unspecified value using a specific eVar when using "Visit" as metric | Community
Skip to main content
J
jaishal
Level 4
July 4, 2024
Question

Unspecified value using a specific eVar when using "Visit" as metric

  • July 4, 2024
  • 3 replies
  • 1001 views

I am seeing a lot of numbers going into "unspecified" when using visit as metric. But for an example, if i am using v72(App Referring tracking code)  against e72(instances), the data does not go into unspecified. But when, using against, metric, i see a lot of data into unspecified. 

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

3 replies

ezhil_raja
ezhil_raja
Level 4
July 4, 2024

The instances metric indicates how many times an eVar was explicitly defined in an image request, meaning you won't see any "Unspecified" for v72 instances. If you're using Visits as a metric in the eVar report and notice "Unspecified" values, it means that the eVar values were not set during those hits.

    J
    jaishalAuthor
    Level 4
    July 4, 2024

    Okay, so this is a visit based eVar. Does it mean, it is implemented/set  incorrectly so the value goes into unspecified?

     

    bjoern__koth
    Community Advisor and Adobe Champion
    bjoern__kothCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    July 5, 2024

    Hi @jaishal 

    any chance you add a screenshot?

    Cheers from Switzerland!
    Ankit_Chaudhary
    Community Advisor
    Ankit_ChaudharyCommunity Advisor
    Community Advisor
    July 5, 2024

    Hi @jaishal 

    Unspecified are expected in reports if an event trigger without an eVar you can check this article for more detail.

    however, instances will provide the number of times a value explicitly set in an eVar that's why you won't find unspecified while checking V72 against instances of V72.

    In simple terms there are visits when there is no value has been set in V72 that's why you are getting unspecified when checking V72 against visits.

    Terms & ConditionsAccessibility statement

    Loading footer...