Create a redirecting test

In this section, we will explain in detail what Redirect Tests are and how Ptengine implements them. Before reading this section, we highly recommend reviewing the content on A/B Testing.

Quickly Understand Redirect Tests #

When optimizing pages, we often encounter multiple influencing factors. Focusing on a single element may not yield scientifically sound results. In these cases, we strongly recommend using Redirect Tests. By setting up multiple page versions with different URLs (e.g., www.ptengine.com/new-in, www.ptengine.com/new-in-1, www.ptengine.com/new-in-2) using URL rules, we can test whether page modifications have a measurable impact on our GOAL metrics.

Example: Product Listing Page: We currently have multiple product lines with similar target audiences, but with significantly different original prices and themes. We've created multiple listing pages, each featuring different product lines prominently at the top. We want the URLs of these pages to remain distinct, so users don't perceive them as the same page. We can then use Ptengine Redirect Tests to validate which product line resonates most with our users.

How to Configure a Redirect Test Experiment

To conduct a Redirect Test, you will need to prepare at least two page versions: the original version and a test version containing your modifications, each with a distinct URL.

Tip: For the original page being redirected, ensure the Ptengine Basic Tag is installed within the  tag of the page's HTML file.

  1. Prepare the URLs for Testing.
  • Control Group: www.ptengine.com/new-in
  • Test Group: www.ptengine.com/new-in-1
    1. Create a new experience and select Redirect Test.
    2. Enter the original URL to redirect and the test page URL.

      If you want to restrict the page conditions for testing, refer to the following example.

Note: If parameters are configured for the URLs mentioned above, please refer to the following parameter passing rules:

Example: Redirecting from "a.com" to "b.com"

  • If b.com has no parameters: Parameters from a.com are fully inherited.

Original page:a.com?utm_source=xxx

Redirect page:b.com

Result:a.com?utm_source=xxx → b.com?utm_source=xxx

  • If a.com and b.com have different parameters: Parameters are merged.

Original Page: a.com?utm_source=xxx

Redirect Target Page: b.com?utm_medium=yyy

Result: a.com?utm_source=xxxb.com?utm_medium=yyy&utm_source=xxx

  • If a.com and b.com have the same parameters: Parameters from a.com will be overwritten by b.com's parameters.

Original Page: a.com?utm_source=xxx

Redirect Target Page: b.com?utm_source=yyy

Result: a.com?utm_source=xxxb.com?utm_source=yyy

Edit Experience, One-Click Publish

Enter the Experience editing interface to configure settings such as "Target Audience," "Experience Goals," and "Publish Time."

Once you have confirmed everything is correct, publish your Experience.

Was this article helpful?

  • Yes, great!
  • Not really

Thanks for your feedback.

  Sorry about that. Do you mind sharing how we can improve?

    Write your feedback here...