Redirect Test
Redirect Test
SUCCESS
What is Redirect TestRedirect 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.
最終更新