Target activity for pages matching certain page path and having query param | Community
Skip to main content
M
m_alcantara
New Participant
February 16, 2024
Solved

Target activity for pages matching certain page path and having query param

  • February 16, 2024
  • 1 reply
  • 813 views

I need to set up an XT activity with the following requirements:

Personalization should be seen in pages matching a certain page path and having a certain term on the query string.

For page path requirement: show personalization on pages in a certain directory. E.g. pages in "/en/path1/"; therefore, /en/path1/thispage.html is a match (show personalization), /en/path1/thatpage.html is a match, etc. Any page under /en/path1/ will match.

Query string requirement: in the querystring, must have certain terms such as "test2" in the params. Therefore, querystring=test1:test2 is a match, querystring=thisstring:test2 is also a match because "test2" is found.

 

Putting both requirements together, this URL & query string would match and the personalization should be shown: https://www.mysite.com/en/path1/mypage.html?querystring=test1:test2

 

I set up an XT activity this way.

Activity Location: https://www.mysite.com/en
AND where path contains /en/path1/
AND query parameter querystring contains :test2

(changed the actual info for privacy but it looks like this)

 

Audience: All visitors

 

I made a modification to a common element found throughout the site. I made sure the element code, structure and css looks exactly the same in all pages. The exact component I modified is re-used throughout the site.

 

I tested the activity and the personalization is not showing. Please advise.

    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 alexbishop

    Typically this would be caused by one of two problems:
    i) You're not qualifying for the activity
    ii) You're qualifying for the activity but the modifications aren't being applied (i.e., selectors aren't valid)

    So it would help to narrow things down by working out which one of those two it is. Can you check what response you get from the request to Target, either via the Network Tab in browser developer tools or through the Experience Cloud debugger extension?

    1 reply

    alexbishop
    alexbishopAccepted solution
    Employee
    February 19, 2024

    Typically this would be caused by one of two problems:
    i) You're not qualifying for the activity
    ii) You're qualifying for the activity but the modifications aren't being applied (i.e., selectors aren't valid)

    So it would help to narrow things down by working out which one of those two it is. Can you check what response you get from the request to Target, either via the Network Tab in browser developer tools or through the Experience Cloud debugger extension?

      M
      m_alcantaraAuthor
      New Participant
      February 22, 2024

      @alexbishop I wasn't qualifying.

      I made a change in the Delivery. This is the new setup.

      Activity Location:   https://www.mysite.com/en/path1 
      OR

      url starts with https://www.mysite.com/en/path1 /

      AND query parameter querystring contains :test2

       

      This works.

       

      I suspect using the AND in the previous setup was not qualifying me because it interprets it as such:

      Deliver the activity here: https://www.mysite.com/en AND if these conditions are true: path contains /en/path1/
      AND query parameter querystring contains :test2.

       

      It could it be that having a specific URL (https://www.mysite.com/en) and, in addition, path must contain /en/path1/ is being evaluated as false. It's as though it's checking if the current page's URL is exactly https://www.mysite.com/en and also that the path of the current page contains /en/path1/. No matter what URL I'm in, both of those conditions in combination will not return true. OR seems to make more sense. Either this exact URL OR the path and cid I set up match.

        Terms & ConditionsAccessibility statement

        Loading footer...