Skip to main content
Contributor I
October 15, 2026
Question

Sign-up form URL targeting: OR/AND logic, query strings, fragments, and locale paths

Hi Klaviyo Community,

I’m preparing a Spanish-language popup for a Shopify store using a single domain with locale subfolders:

English homepage: https://example.com/
Spanish homepage: https://example.com/es
Spanish pages: https://example.com/es/collections/all

The goal is for both the popup and its teaser to be eligible only on the Spanish storefront. The proposed URL inclusion rules are:

Only show on certain URLs:
1. Exactly matching: https://example.com/es
2. Containing: https://example.com/es/

The editor offers “Containing,” “Exactly matching,” and “Add URL.” Before applying these rules, could someone clarify the following?

1. Multiple URL rules: Are entries under “Only show on certain URLs” combined using OR or AND? Can each entry use a different operator, as in the example above?

2. Exact matching: Does “Exactly matching” compare the entire URL, including query parameters and the fragment? Does it ignore either component or normalize trailing slashes? Evaluating rule 1 on its own, would it match each of these examples?

https://example.com/es?utm_source=newsletter
https://example.com/es#section
https://example.com/es/

3. Containing and locale boundaries: Does “Containing” search the complete URL, including query parameters, or only part of it? Does it compare the literal URL text or a decoded value? For example, could rule 2 mistakenly match either of these English-page URLs because the query contains a Spanish destination?

https://example.com/?return_to=https://example.com/es/collections/all
https://example.com/?return_to=https%3A%2F%2Fexample.com%2Fes%2Fcollections%2Fall

If those two inclusion rules do not reliably cover the Spanish homepage and its subpages while excluding English pages, what is the supported configuration using Klaviyo’s built-in URL targeting, without custom JavaScript or theme changes?

I found the official documentation confirming the two operators, wildcard support, and that teasers respect the form’s targeting settings. The targeting guide explicitly documents AND logic for UTM targeting, but I could not find an explicit OR/AND definition for multiple URL entries. Its note about ignoring query parameters and fragments appears under unique-page counting, not URL matching:

An official reference or a concrete explanation of the matching behavior would be helpful. This question is about preparing the targeting configuration; I have not published these rules or run a new subscription test.

Thank you.

2 replies

Nick
Expert Problem Solver I
Expert Problem Solver I
October 15, 2026

Hi Jen, 

regarding your questions and as far as I know: 

1. Multiple URL rules: The expected behavior for multiple inclusion URLs would be OR logic, meaning the form is eligible when either URL condition matches.

2. Exact matching or containing
I think the official documentation is not entirely specific on those things. What I usually do with my clients: 
For spanish popups and if the domain is something with /es/ I use pages contain = example.com/es (so include the full domain in order to avoid just looking for something with /es in the urls). I did not experience popups not showing if there were url parameter within the urls. So I would assume klaviyo goes mostly on the url path. 
 

Contributor I
October 15, 2026

Hi Nick, thanks for sharing your experience. Before applying the rules, could you clarify whether OR logic between multiple URL entries is confirmed behavior or your expectation?

For “Containing: example.com/es”, would either of these English-page URLs also match?
- https://example.com/?return_to=https://example.com/es/collections/all
- https://example.com/?return_to=https%3A%2F%2Fexample.com%2Fes%2Fcollections%2Fall

Could it also match an unintended path such as /espanol? We need to cover /es and /es/…, including query parameters and fragments, while excluding English pages. Is there a supported built-in configuration or official reference that confirms these boundaries?

Thanks again!