Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Redirect Test

Redirect Test

SUCCESS

What is Redirect Test

Redirect Test is a type of A/B test that significantly contributes to improving user experience and website performance.

Main Features ✨

Suitable for large-scale changes

Enables full-scale creative testing

Effective for identifying elements that impact conversions

Helps identify areas that need improvement

Use Cases 🎯

When making significant changes to a page

When comparing the current page with past versions

When validating the effects of completely different designs or layouts

Benefits of Redirect Test 👍

High flexibility in testing

Multiple elements can be changed simultaneously

Site-wide structural changes can also be validated

Setup Method

Required Setup 📋

Prepare two web pages Original page

Install Ptengine basic tag Location: Inside the <head> tag of the redirect source page

WARNING Be sure to install the Ptengine basic tag on both the redirect source page and the redirect destination page.

Create a Redirect Test Experience

Create a new experience

Select Redirect Test from the experience selection screen

Enter the URL for the redirect source in Original

If you want to redirect only under specific conditions, specify the redirect conditions. Enter the redirect destination URL in "Pattern" You can add up to 5 patterns, and the distribution ratio for each can be specified in a later step.

Set the delivery conditions for the experience After clicking "Save" and proceeding to the delivery condition settings, specify "Target Users", "Goal", and (if necessary) "Schedule".

For information on how to set Target Users and Goal, please refer to this article.

Publish Check the items and click the publish button.

URL Parameter Inheritance Rules in Redirect Test 🔗

When implementing a redirect test, how URL parameters are handled is an important consideration. Below are the parameter inheritance rules for different scenarios.

Scenario 1: When the Redirect Destination Has No Parameters ✅

Parameters from the original URL are fully inherited. Example:

Original URL: a.com?utm_source=xxx

Redirect Destination: b.com

Result: b.com?utm_source=xxx

Scenario 2: When Different Parameters Exist 🔀

Parameters are merged. Example:

Original URL: a.com?utm_source=xxx

Redirect Destination: b.com?utm_medium=yyy

Result: b.com?utm_medium=yyy&utm_source=xxx

Scenario 3: When Same Parameters Exist 🔄

Parameters from the redirect destination take priority and override parameters from the original URL. Example:

Original URL: a.com?utm_source=xxx

Redirect Destination: b.com?utm_source=yyy

Result: b.com?utm_source=yyy

DANGER

Important Notes

Impact on Analytics Parameter changes may impact tracking data.

Campaign Tracking Campaign identifiers such as UTM parameters may be changed, so they need to be properly managed.

User Experience Long URLs or multiple parameters may impact user experience.

✅ By understanding and properly managing these rules, you can enhance the data accuracy of your redirect test and obtain more precise analysis results. When designing your test, take these parameter inheritance rules into consideration and make adjustments as needed.

Anti-Flicker Feature

You can manage the ON/OFF setting of the anti-flicker feature. It is disabled by default.

If you have directly installed the Ptengine basic tag, we recommend enabling this feature.

For details, please refer to the "Anti-Flicker Feature" section in this article.

FAQ

1. If my original page is www.ptengine.com and I enable "Redirect with any parameters", will all links with parameters be redirected?

Yes. With this option enabled, any request to www.ptengine.com/ that carries query parameters (e.g. ?id=123) will be redirected to the corresponding test version according to the redirect rules. After the redirect, the system recognizes the destination page, so no infinite loop occurs.

2. When setting up a redirect test on my homepage with "Redirect with any parameters" enabled, if the test page URL itself contains parameters (e.g. www.ptengine.com?page=v1), could it be misidentified and redirected repeatedly?

No, redirect loops will not occur.

3. If a user enters the homepage with other UTM parameters (e.g. www.ptengine.com?utm=xxx) and is assigned to the test group (e.g. www.ptengine.com?page=v1), how are the parameters merged after the redirect? Could the parameter order trigger another redirect?

After the redirect, the address bar shows www.ptengine.com?page=v1&utm=xxx (the test page parameters come first). The system correctly recognizes that the user is already on the test version, so no second redirect is triggered.

4. If a user is assigned to the test page, navigates to another page (e.g. a product detail page), and then returns by clicking the brand logo or similar, will they see the original homepage or the test version?

They will continue to see the test page. Version assignment is based on the user's unique identifier (UID), so the same user (same UID) is always assigned to the same version.

5. In the redirect test report, can the event data of the two pages (e.g. www.ptengine.com/ and www.ptengine.com?page=v1) be distinguished? Could there be double counting?

Yes, they are fully distinguished. The report tracks event data separately for each page (the original and each test version), with no double counting or data mixing, so you can clearly compare the conversion performance of each version.

6. In the redirect test report, after clicking to view the heatmap, the comparison between the original page and the test page is shown, but the test page has no heatmap data. Why?

You need to enable the "View heatmap as combined page" option. Once enabled, the data will be displayed.

前へSmart Traffic Allocation: Bandit Algorithm次へShopify Theme Test

最終更新