Estimate the traffic required for a successful Multivariate Test activity
- Topics:
- Multivariate Tests
Because a multivariate test compares multiple experiences, it is important to know how much traffic is required to provide meaningful results. The Traffic Estimator uses statistics about your page and the number of experiences being tested to estimate the amount of traffic and the test duration needed to make the test successful.
The Traffic Estimator predicts the sample size needed to ensure the following:
- 95% confidence. This statistic means that the chance of reporting a false positive if there is no real lift is 5% (100% - confidence level).
- 80% statistical power. This statistic means that the test has an 80% probability of detecting a true lift of 25% or more.
- 25% minimum reliably detectable lift. Target computes the amount of traffic required to have an 80% chance of detecting a true lift of 25% or more.
The test uses the Bonferroni correction to correct for multiple comparisons. This method is known for being conservative, which is balanced out by enforcing a relatively large minimum reliably detectable lift.
The Traffic Estimator also provides feedback that lets you know whether you have sufficient traffic for the test you designed to succeed.
-
From the Experiences page of the Visual Experience Composer in a Multivariate activity, click the Traffic icon (
The Traffic Estimator opens.
You can click the icon again to hide the Traffic Estimator.
Near the top of the Traffic Estimator, the values you entered are calculated and the results are shown.
-
(Conditional) Provide the typical conversion rate, estimated visitors per day, and test duration.
- Number of Content Combinations: Calculated automatically based on the number of experiences being created as a part of your activity after any exclusions.
- Typical Conversion Rate: The conversion rate is expressed as a percentage, based on your estimation or past data from your analytics system.
- Estimated Visitors Per Day: This is the number of visitors who are likely to view this page based on the targeting criteria. This could be based on your analytics data.
- Test Duration: The number of days you want the activity to run.
The Traffic Estimator uses these statistics to determine what adjustments are needed to run a successful test.
As you change the numbers, the estimate changes. For example, if you are testing many experiences and your conversion rate and impressions are too low, the Traffic Estimator shows how long the test must run to be successful. Or, if your traffic is low, the Traffic Estimator might suggest a lower number of experiences so you can run the test the desired number of days.
If you do not have sufficient traffic, you can do one or both of the following:
- Reduce the number of combinations of offers and the number of locations.
- Increase the duration of the test.
Adjust the numbers until the Traffic Estimator indicates you have sufficient traffic, then design your test accordingly.
Target
- Adobe Target Business Practitioner Guide Home
- Target release notes
- Introduction
- Introduction to Target
- Access Target from the Adobe Experience Cloud
- Target key concepts
- Understand the Target UI
- Adobe Target welcome kit
- Target welcome kit overview
- Chapter 1: Introduction
- Chapter 2: Target at a glance
- Chapter 3: Develop your testing and personalization ideas
- Chapter 4: Tips for using Target
- Chapter 5: Inspiration for testing and personalization activities
- Chapter 6: Easily avoidable pitfalls
- Chapter 7: Create and run your first Target activity
- Chapter 8: Communicate your activity results
- Chapter 9: Next steps and resources
- Glossary
- How Target works
- Training and certification
- Training videos for Target Standard and Premium
- Target optimization and personalization FAQ
- Administer Target
- Implement Target
- Integrate Target with the Experience Cloud
- Adobe Analytics as the reporting source for Target (A4T)
- A4T overview
- Before you implement
- Analytics for Target implementation
- User permission requirements
- Create an activity that uses Analytics as the reporting source
- A4T support for Auto-Allocate and Auto-Target activities
- Use an Analytics tracking server
- A4T reporting
- Troubleshooting the Analytics and Target integration (A4T)
- A4T Frequently Asked Questions
- Expected data variances between Target and Analytics when using and not using A4T
- Integrate Target with Adobe Customer Journey Analytics
- Integrate Target with Adobe Journey Optimizer (AJO)
- Experience Cloud Audiences
- Integrate Target with Adobe Experience Manager (AEM)
- Integrate Target with Adobe Audience Manager (AAM)
- Integrate with Real-time Customer Data Platform
- Integrate Target with Adobe Campaign
- Adobe Analytics as the reporting source for Target (A4T)
- Activities
- Activities overview
- Target activity types
- A/B Test
- Auto-Allocate
- Auto-Target
- Automated Personalization
- Automated Personalization overview
- Random Forest Algorithm
- Create an Automated Personalization activity
- Upload data for the Target personalization algorithms
- Data collection for the Target personalization algorithms
- Estimate the traffic required for success
- Preview experiences for an Automated Personalization test
- Target Automated Personalization offers
- Manage exclusions
- Offer reporting groups in Automated Personalization
- Select the control for your Automated Personalization or Auto-Target activity
- Automated Personalization FAQ
- Troubleshoot Automated Personalization
- Experience Targeting
- Multivariate Test
- Recommendations activity
- Edit an activity or save as draft
- Priority
- Activity settings
- Success metrics
- Activity change log
- Troubleshoot activities
- Activity QA
- Audiences
- Experiences and offers
- Experiences and offers overview
- Visual Experience Composer (VEC)
- Visual Experience Composer overview
- Visual Experience Composer options
- Visual Experience Composer changes
- Include the same experience on similar pages
- Multipage activity
- Activity collisions
- Modifications
- Element selectors used in the Visual Experience Composer
- Mobile viewports for responsive experiences
- Visual Experience Composer best practices and limitations
- Troubleshooting the Visual Experience Composer
- Troubleshooting the Visual Experience Composer overview
- Troubleshooting the Visual Experience Composer and Enhanced Experience Composer
- Troubleshooting the Visual Experience Composer
- Troubleshooting the Enhanced Experience Composer
- Enabling mixed content in your browser
- Page modification scenarios
- Visual Editing Helper extension
- Visual Experience Composer helper extension
- Redirect to a URL
- Creating carousels that work in the Visual Experience Composer
- Form-Based Experience Composer
- Single Page App (SPA) Visual Experience Composer
- Offers
- Reports
- Recommendations
- Recommendations overview
- Introduction to Recommendations
- Plan and implement Recommendations
- Entities
- Criteria
- Criteria overview
- Create criteria
- Create criteria sequences
- Base the recommendation on a recommendation key
- The science behind Target’s recommendations algorithms
- Upload custom criteria
- Dynamic and static inclusion rules
- Use a backup recommendation
- Work with multi-value attributes
- Use Adobe Analytics with Recommendations
- Design
- Activity
- Recommendations as an offer
- Frequently asked questions
- Recommendations Classic documentation
- Troubleshoot Target
- Target APIs
- Resources and contact information