Skip to main content
DannyPancratz
VIP ⭐️⭐️⭐️⭐️⭐️
September 22, 2025
Solved

I can't URL or Query Parameter based Audience rules to work for PX (engagement, segments, Audience Explorer)

  • September 22, 2025
  • 3 replies
  • 86 views

What might I be doing wrong? 

First I thought it might be related to using wild cards in the URL or the px-auto-resolve token. 

But I’ve been testing going to the exact URL, no wild cards, no tokens. 

  • My engagement isn’t triggering (even with throttling turned off and the qualification rule to be once per session)
  • My page views are not matching segments that use those rules
  • Audience Explorer filters by that URL and/or the query parameter don’t return any users

I’ve tried the query parameter rules (Audience criteria for Engagement, Segment rules) using IS, CONTAINS, and STARTS WITH. Nothing works. 

What’s the trick to this? 

    Best answer by Alistair FIeld

    I have had to laugh at myself in the past for making silly oversights.

    1. am I working in the correct PX product (i.e. not building it in SANDBOX and expecting it to be in product)
    2. Did I set the date right in the engagement (I got lost last week where the date was a month early and thus not triggering)
    3. Is the domain name correct and has the javascript loaded. ( when we merged education into the community, passing from the community domain into the education based pages left behind the header of community and therefore the javascript. so I have a second script for the education pages.)

    I assume you have had them working before and this is a once off? 

    3 replies

    Alistair FIeld
    Expert ⭐️
    September 22, 2025

    I have had to laugh at myself in the past for making silly oversights.

    1. am I working in the correct PX product (i.e. not building it in SANDBOX and expecting it to be in product)
    2. Did I set the date right in the engagement (I got lost last week where the date was a month early and thus not triggering)
    3. Is the domain name correct and has the javascript loaded. ( when we merged education into the community, passing from the community domain into the education based pages left behind the header of community and therefore the javascript. so I have a second script for the education pages.)

    I assume you have had them working before and this is a once off? 

    The needs of the many, outweigh the needs of the few. 🖖
    DannyPancratz
    VIP ⭐️⭐️⭐️⭐️⭐️
    September 22, 2025

    OMG ​@Alistair FIeld #2 was it. THANK YOU!!!
     

    PX auto set a 12am “tomorrow” end time. And thanks to UTC, it was blocking this from working.

     

    Now why I’m not seeing my testing in segments or Audience Explorer… ¯\_(ツ)_/¯

    FYI: I am no longer active in this community
    Alistair FIeld
    Expert ⭐️
    September 22, 2025

    Glad to help. 

    Anytime you want to hash out ideas or a sounding board I would be happy to talk. I think we are going through much of the same as we add PX string to bow. 🏹🎯

    The needs of the many, outweigh the needs of the few. 🖖