How to setup a dimension - Entry Page URL? | Community
Skip to main content
Vinay_Chauhan
Vinay_Chauhan
New Participant
Dec 24, 2021 7:09 PM UTC
Solved

How to setup a dimension - Entry Page URL?

How to setup a dimension called Entry page URL, which collects the compete entry/first page URL value.

Evar for this has already been created.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    jgrubbs
    jgrubbsAccepted solution
    Level 3
    Dec 25, 2021 3:21 PM UTC

    I suppose you can configure the eVar for "Original Value (First)" attribution, and have it expire on Visit.

    Then in your processing rules, you can map PageURL to that eVar.

    In theory, the first PageURL value encountered in a visit will be stored and persisted in that eVar until the visit expires

     

    View reply

    6 replies

    yuhuisg
    yuhuisg
    New Participant
    Dec 27, 2021 8:37 AM UTC

    If you want to see a dimension called Entry Page URL (and also Exit Page URL), then you need to setup a prop called "Page URL" and enable Pathing on it. AA will then automatically create the Entry Page URL (and Exit Page URL) dimensions.

    Follow @jgrubbs's instructions to populate the prop's value.

    Translate
      Vinay_Chauhan
      Vinay_ChauhanAuthor
      New Participant
      Dec 27, 2021 9:05 AM UTC

      Thanks for your reply @yuhuisg 

      Translate
        jgrubbs
        jgrubbsAccepted solution
        Level 3
        Dec 25, 2021 3:21 PM UTC

        I suppose you can configure the eVar for "Original Value (First)" attribution, and have it expire on Visit.

        Then in your processing rules, you can map PageURL to that eVar.

        In theory, the first PageURL value encountered in a visit will be stored and persisted in that eVar until the visit expires

         

        Translate
          Vinay_Chauhan
          Vinay_ChauhanAuthor
          New Participant
          Dec 26, 2021 6:12 PM UTC

          Thanks for your reply.

          I have followed the exact same steps.

          But, what should be next steps?
          How to make that eVar as part of the page view beacon?

          Translate
          jgrubbs
          jgrubbs
          Level 3
          Dec 26, 2021 9:11 PM UTC

          Hi @vinay_chauhan that is a nice part about using the Processing Rule I described. You don't have to add the eVar into your front end code. Page URL is automatically sent on every beacon, so you can copy that value into an eVar in a new Processing Rule. Here is an example where an eVar (eVar54) called "Page URL" is populated with the value of "Page URL" under Hit Attributes

           

          Translate
            Terms & ConditionsAccessibility statement

            Loading footer...