Skip to main content
Level 2
March 11, 2026
Solved

Targeting Pages with query and without query

I need to target the homepage for an activity, but I'm running into an issue with URL matching.

 

The activity fires correctly when users visit https://example.com/, but it doesn't trigger when users land on https://example.com/?utm_source=source or https://example.com/?abcdefjkl (any URL with query parameters).

I've tried several different configurations, but none of them are working.

I've attached screenshots showing my current setup.

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Gokul_Agiwal
Gokul_AgiwalAccepted solution
Community Advisor
March 16, 2026

Hi ​@m_aadil_naina 

You can use below options 

Use operator “starts with” 

This ensures your activity qualifies whether the user hits:

So as long as the URL begins with  example.com .. it will match regardless of query strings. 

2.  Use query 

For specific to query string param - you can use like below. 

Or you can combine domain + query together 

 

Please check which options useful based on your use case. if you still facing issues then please post it here. 

Hope above helps. 

Thanks

Thanks, Gokul

4 replies

Gokul_Agiwal
Community Advisor
Gokul_AgiwalCommunity AdvisorAccepted solution
Community Advisor
March 16, 2026

Hi ​@m_aadil_naina 

You can use below options 

Use operator “starts with” 

This ensures your activity qualifies whether the user hits:

So as long as the URL begins with  example.com .. it will match regardless of query strings. 

2.  Use query 

For specific to query string param - you can use like below. 

Or you can combine domain + query together 

 

Please check which options useful based on your use case. if you still facing issues then please post it here. 

Hope above helps. 

Thanks

Translate
Thanks, Gokul
Gokul_Agiwal
Community Advisor
Community Advisor
March 24, 2026

HI ​@m_aadil_naina Did you get a chance to implement above and are you able to solve your use case? 

Translate
Thanks, Gokul
Level 2
April 1, 2026

​@Gokul_Agiwal 

Method 1: When visitors accessed https://example.com/path1 or https://example.com/path2, the activity is present there (for any URL starting with https://example.com/). This resulted in unintended tracking across all site visitors.

Method 2: This approach only functioned correctly for specific query parameters, such as https://example.com/?utm_source=source. It failed to capture activity for URLs with arbitrary query parameters like https://example.com/?anythinghere.

Resolution: I successfully resolved the issue by implementing page name-based targeting instead.

Translate