Is my understanding of hit container in segment correct? | Community
Skip to main content
K
kodaio44098824
Level 2
November 12, 2018
Solved

Is my understanding of hit container in segment correct?

  • November 12, 2018
  • 6 replies
  • 3364 views

Hello

I have been making various segment and test them for my deep understanding of segmentation.

But I can't figure out why this number appear using following segment and metrics.

■Segment

・container type:Hit

・internal search Terms 「contains] "Ski"

■Metrics

Revenue

If I use  above segment,

Revenue should be 0.

Because of following reason.

・hit is an image request.

・Revenue will occur in order confirmation page all the time,

・Internal search will occur in search page or somewhere(not sure...

But actual number of revenue is more than 0 like following image.

Why does it happen? My understanding is not incorrect, or data is incorrect?

    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 Urs_Boller

    Do you use an eVar as "internal search term"? if yes, what is expiry?

    If you track the "internal search term" in an eVar with eg. visit exporation, you would see all orders where the user search for the desired string before the order. the reason is that the eVar is valid until expiry, therefore the segment includes more than just a single hit/image request.

    you can see the difference if you add the corresponding instance metric to the segment ("internal search term instances). this way you would only receive hits where the search term is sent to adobe (in image request).

    6 replies

    Urs_Boller
    Community Advisor
    Urs_BollerCommunity AdvisorAccepted solution
    Community Advisor
    November 12, 2018

    Do you use an eVar as "internal search term"? if yes, what is expiry?

    If you track the "internal search term" in an eVar with eg. visit exporation, you would see all orders where the user search for the desired string before the order. the reason is that the eVar is valid until expiry, therefore the segment includes more than just a single hit/image request.

    you can see the difference if you add the corresponding instance metric to the segment ("internal search term instances). this way you would only receive hits where the search term is sent to adobe (in image request).

      K
      kodaio44098824Author
      Level 2
      November 13, 2018

      Thank you for really quick answer.

      Yes I use an eVar and valid during visit.

      I made a document for my deep understanding based on your answer.

      Am I correct..?

      Thank you

      Thank you for really quick answer.

        Urs_Boller
        Community Advisor
        Urs_BollerCommunity Advisor
        Community Advisor
        November 13, 2018

        thats really a great visualization! I would add another hit before the internal search term to see the different result using a hit vs visit container on the evar (the hit container would start at the second hit, not including the first page - since the search is on the second hit...)

        K
        kodaio44098824Author
        Level 2
        November 14, 2018

        I guess you mean the following case,, Am I right?

          Urs_Boller
          Community Advisor
          Urs_BollerCommunity Advisor
          Community Advisor
          November 14, 2018

          hi kodaio44098824​

          looks great, exactly what I meant.

          Remarks:

          1) "Session timeout" is not a "hit", I would skip that ...

          2) if you want, you could add a second picture (only for eVar) to compare visit vs. visitor segment container to get the full picture of segmentation. but this was not the initial question....

          K
          kodaio44098824Author
          Level 2
          November 14, 2018

          Hi

          Thank you so much for great answer.

          Actually, I made a new thread before you suggestion.

          I really appreciate it if you kindly answer the following thread also.

          It's almost same  as the answer of 2).

          Segment Comparison(Hit VS Visit VS Visitor)

          Terms & ConditionsAccessibility statement

          Loading footer...