Target use case for Entry page - need help | Community
Skip to main content
K
kob1
January 25, 2021
Solved

Target use case for Entry page - need help

  • January 25, 2021
  • 1 reply
  • 850 views

Running into trouble setting up Target to meet the following use case: [If Incoming traffic is from google organic search and it's going to land on Page A, redirect to Page B. (But if Page A is requested otherwise during the visit, allow A to be shown)]

 

The trouble is that we can redirect the incoming traffic to Page B as landing page--- But if the person navigates to Page A later in their visit (through site menu or otherwise), they are again redirected to Page B. 

 

How would you recommend constructing a Target activity to achieve the first-page-of-visit redirect from Page A to Page B, but not interfere with subsequent requests for Page A in the visit?

    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 josejr19

    I would add an additional parameter to Page A if the user lands on it organically to pass into the global mbox a parameter like "notReferred=true" then in the experience set the condition to be referred from Google and notReferred is not present. This means you need to have logic on the page that passes the notReferred value. 

    1 reply

    J
    josejr19Accepted solution
    Level 5
    January 26, 2021

    I would add an additional parameter to Page A if the user lands on it organically to pass into the global mbox a parameter like "notReferred=true" then in the experience set the condition to be referred from Google and notReferred is not present. This means you need to have logic on the page that passes the notReferred value. 

      Terms & ConditionsAccessibility statement

      Loading footer...