Skip to main content
New Idea

Product Map Feature Not Tracking Events. Resolved with URL Rule issue but needs warning.

Related products:PX Product Mapper

Ashton
  • Contributor ⭐️⭐️⭐️⭐️

I have a resolved issue with Support that might be of help to others in the future so I am posting this here. 

We had a feature that was not tracking events yet everything seemed to be configured properly. After much trouble shooting we identified that Feature URL rules have a specific flaw that will make it fail to capture the events. 

You may not use a wildcard (*) before a period (.) at the start of the URL (untested in the middle)

Example: *.company.com/page*    will not work as it has a (*.) at the beginning

Example solution: *company.com/page*   by removing the period (.) we have resolved the issue and the feature now tracks the events. 

 

The reason for posting this as an Idea, is because a warning message would be useful to tell users that the (*.) configuration is invalid. A simple popup warning or a block from saving that explains the invalid nature of the configuration. Alternately, a patch that makes the (*.) a viable configuration would also resolve this as a defect.

I hope that this idea is short lived, but wanted to save someone the troubleshooting in the meantime if they run into this issue. 

link_black
Forum|alt.badge.img+2
  • Gainsight Employee ⭐️⭐️
  • July 12, 2023

Thanks for posting @Ashton!  This looks more like a bug to me, so thank you for calling this out here and for providing the workaround.


rschlette
Forum|alt.badge.img+2
  • Gainsight Employee ⭐️⭐️
  • August 24, 2023

There is actually a much more narrow case here, so I’ll add some additional details.

In general, using a wildcard followed by a dot is a fine way to wildcard a subdomain. If my url scheme is accountName.domain.com, I can write a universal rule for that by using *.domain.com No issues with that at all; the *. at the beginning of the rule works just fine.

The issue you encounter was in the specific and limited case of www.domain.com . PX strip www. out of all urls so that www.domain.comn and domain.com are auto resolved. So whether your url is  www.domain.comn and domain.com, PX consumes doimain.com. If www. is treated like a subdomain in a rule, like (*.domain.com), the rule will fail because the dot is stripped. Basically you can always ignore www. in a url, because PX will strip it out. No need to address it.

Again, any other subdomain is unaffected here so subdom.domain.com can be matched to *.domain.com.

Hopefully that clarifies the scope a bit


rschlette
Forum|alt.badge.img+2
  • Gainsight Employee ⭐️⭐️
  • August 24, 2023

now with fewer typos: 

The issue you encountered was in the specific and limited case of www.domain.com . PX strips www. out of all urls so that www.domain.com and domain.com are auto resolved. So whether your url is  www.domain.com or domain.com, PX consumes domain.com. If www. is treated like a subdomain in a rule, like (*.domain.com), the rule will fail because the dot is stripped. Basically you can always ignore www. in a url, because PX will strip it out of both the incoming event and the rule. No need to address it.



Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings