Page Targeting

What is Intelligems Page Targeting?

By default, all pages on your site are included in a test. Intelligems page targeting allows you to limit your test to specific pages of your website.

How does Intelligems Page Targeting work?

When you set up page targeting, site visitors will only be included in the test when they navigate to a page whose URL is included in the page targeting criteria. If a site visitor is on a page that is not included in the page targeting, they will be excluded from the test until they navigate to an included page.

Once a site visitor visits a targeted page, they will be assigned to a test group and remain in that test group for the remainder of the test, even if they navigate to pages that are not included in page targeting.

That said, modifications, such as Onsite Edits or Template Redirects, will only execute on the pages specified in your page targeting criteria. Visitors in your test will not see the modifications when they navigate to non-targeted pages.

We match targeting based on the content after your store URL and before any query parameters. For example,

  • https://ovenspring-cookware.myshopify.com/collections

  • https://ovenspring-cookware.com/collections

  • https://ovenspring-cookware.com/collections?utm_source=facebook

will all correctly match the condition:

URL Path equals /collections

Because we match targeting based on the content after your store URL, you cannot set up page targeting for different domains simply using the URL. For example,

  • https://ovenspring-cookware.myshopify.com

  • https://ovenspring-cookware.myshopify.fr

will both correctly match your homepage. It is possible to target different domains using Custom JavaScript targeting.

URLs with trailing slashes: Similar to Shopify's routing rules, Intelligems will not evaluate a trailing slash at the end of a URL, for example:

https://example.com/collections/

will be evaluated the same as

https://example.com/collections (no trailing slash).

What types of tests can I use Intelligems Page Targeting for?

Page targeting is available only for Content Tests that are created using Onsite Edits, as a Template Test or as an Advanced Test. Page Targeting is not available for Theme Tests or for Split URL Tests. Split URL Test analytics already include only visitors who reached one of the redirect pages.

How does Page Targeting impact experiment analytics?

Experiment analytics for experiments that use page targeting show visitors who were exposed to the test (that is, they reached a targeted page while the experiment was live). Any order made by these visitors while the experiment was live (but after the visitor entered it) is attributed to the experiment, even if the visitor did not add to cart on a targeted page.

Examples of Intelligems Page Targeting

Including traffic on a specific product page

You can select a single page to target in your test.

Including traffic on specific product pages

You can select multiple pages to target in your test using OR criteria. When multiple conditions are set, Intelligems will include a user if they meet any of the conditions set.

Including traffic for pages contained inside certain collections

You can set more general inclusion rules by setting a broader URL. In this example, all URLs that start with "collection-a" or "collection-b" will be included, but URLs that start with a different URL, e.g. "collection-c" will not be included.

Targeting the homepage

To target the homepage, simply use /

Page Targeting Tester

Use our Page targeting tester to check whether an example URL matches your configured targeting criteria. Here is an example of testing whether URL visits to certain collections will or will not be included in your test.

In this image, we are testing whether https://ovenspring-cookware.myshopify.com/collection-c matches the configured criteria.

Proposed URL failed to match configured criteria.

In this image, we are testing whether https://ovenspring-cookware.myshopify.com/collection-a matches the configured criteria.

Proposed URL matches configured criteria

Last updated

Was this helpful?