> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getjurni.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Test a Jurni Page Against an Existing Website Page

> Compare a Jurni page with an existing Shopify or external page in one experiment, understand how experiment parameters are passed through, and validate downstream attribution before launch.

Jurni experiments can compare a Jurni page against an existing Shopify page or another supported external URL. This is useful when your current PDP or landing page should remain the control while a new Jurni experience is the challenger.

## When to use an existing page as the control

Use an existing page when you want the experiment to answer a real business question such as:

* Does the new Jurni page outperform the current PDP?
* Does an advertorial or pre-lander improve performance compared with sending traffic directly to product detail?
* Which of several page concepts performs best against today's baseline?

Keeping the existing page in the same experiment lets Jurni make the traffic assignment from one Smart Link rather than relying on separate campaign URLs to create the split.

## Set up the experiment

<Steps>
  <Step title="Create or choose the Smart Link">
    The Smart Link is the campaign-facing URL that will assign visitors to the experiment variants.
  </Step>

  <Step title="Add the existing page">
    Add your current Shopify page or other public URL as one variant.
  </Step>

  <Step title="Add the Jurni page">
    Add the Jurni experience you want to compare against the control.
  </Step>

  <Step title="Set the traffic weights">
    Configure the percentage of eligible new assignments that should go to each variant. The weights must total 100%.
  </Step>

  <Step title="Add Routing Rules only when intentional">
    If a URL parameter should force a specific audience into a variant, configure a Routing Rule. Otherwise, visitors use the normal weighted assignment.
  </Step>

  <Step title="Start and QA the experiment">
    Open the Smart Link in a clean browser and verify both the redirect behavior and downstream tracking before sending paid traffic.
  </Step>
</Steps>

## What Jurni adds to the destination URL

When the experiment redirects a visitor, Jurni preserves incoming campaign parameters other than Shopify-internal proxy parameters and appends:

* `jurni_ab_test_id`
* `jurni_ab_variant_id`

These parameters carry the experiment and variant context into the destination page.

## Shopify control pages with Jurni Core

If the control is a Shopify page on a store where **Jurni Core is active**, Jurni Core reads the experiment parameters on the destination and can continue the Jurni session/visit and cart attribution flow.

That is materially different from sending traffic to a completely unrelated website with no Jurni tracking installed.

For a Shopify control page, validate:

1. Jurni Core is active on the Shopify storefront.
2. The redirected URL contains the Jurni experiment/variant parameters.
3. Add-to-cart and checkout behavior preserves the Jurni cart/session evidence.
4. A test order is attributed to the expected experiment variant in Jurni.

<Info>
  Jurni's current Shopify attribution uses Jurni visit and cart/checkout evidence. The Shopify **sales channel** is not the attribution rule used to decide which experiment variant owns an order.
</Info>

## External pages without Jurni Core

A public URL can still be used as an experiment destination, but downstream visibility depends on the tracking available on that destination.

If the page does not load Jurni Core or another agreed Jurni tracking implementation, Jurni can make the Smart Link assignment and redirect the visitor, but it cannot automatically observe every interaction or commerce event that happens later on an unrelated site.

For those destinations, decide before launch how conversion data will be compared—for example through the site's own analytics stack or a custom Jurni integration.

## Keep the experiment variable clean

When the purpose is to compare landing-page performance, avoid changing unrelated variables at the same time.

Keep these consistent where possible:

* ad creative
* offer and product pricing
* audience targeting
* campaign parameters
* checkout availability
* measurement setup

The Smart Link should be the common entry point so Jurni, not the ad platform, determines the landing-page variant.

## Validate tracking before launch

Run test sessions through **each** variant and verify:

* the final URL and redirect are correct
* `jurni_ab_test_id` and `jurni_ab_variant_id` are present after assignment
* the correct variant is shown in Jurni
* the expected conversion events are recorded
* a Shopify test order, when applicable, is attributed to the expected experiment
* GA4, Meta, or other external tools fire once rather than through duplicate installations

## Do not use old fixed significance thresholds

Older help-center material recommended fixed session counts and confidence thresholds for declaring a winner. Jurni's statistical-significance feature is not currently a shipped decision layer, so those thresholds should not be treated as product behavior.

Use the current experiment metrics and enough business-relevant volume to make a responsible decision; do not infer a Jurni “winner” state that the product does not currently calculate.

## Related guides

* Create an Experiment
* Traffic Assignment
* Routing Rules
* Attribution Overview
* Activating Jurni Core
* URL Parameters
* Analytics Differences


## Related topics

- [What Are Experiments? A/B Testing in Jurni](/experiments/what-are-experiments.md)
- [How Experiment Traffic Is Assigned](/experiments/traffic-assignment.md)
- [Create and Run an A/B Test in Jurni](/experiments/create-experiment.md)
- [Plan a useful experiment](/experiments/strategic-experiments.md)
- [Strategy: Opportunities and Briefs](/strategy/roadmap.md)
