UI Elements
Site-Wide Campaign Announcement Bar A/B Test Example
A temporary site-wide banner can expose the same campaign across more page visits. It takes up space and may attract less attention on repeat visits. Keep assignment consistent across the site and compare the presence of one fixed banner during the actual campaign period.
A/B test scenario. This page is a test plan, not the result of a real experiment.
- UI elements
- Campaign action completion rate
Control vs Variant
Absent on one side, present on the other.
- Changed
- Presence
- Page
- UI elements
- Difference
- added
Hypothesis
If a real time-limited campaign appears in one fixed banner on every page across the site, more visitors may notice it during their visit. More people seeing it could lift the campaign action completion rate, though the banner takes up space and may be overlooked on repeat visits.
Test plan
When to run this test
A time-limited campaign announced only on the home page or the campaign page can leave visitors elsewhere unaware of it; few visits to the campaign page, site searches for the campaign or support tickets from customers who heard about it too late are the warning signs. When the banner does its job, visitors who see it on different pages complete the predefined campaign action more often. Before launch, choose that action, confirm the campaign is real with accurate dates and countdown, and make sure the banner comes down when it ends.
How to measure success
Campaign action completion rate
Choose one campaign action before launch, such as visiting the campaign page or completing an eligible campaign order, and measure it among all assigned visitors. Do not run the test until the action event is defined.
Also track
- Overall purchase conversion rate (CR)Compare purchases or the predefined primary site action among all eligible assigned visitors.
- Announcement bar click-through rateCompare clicks among eligible visitors who see the bar.
- Bar dismissal rateMeasure dismissals; a dismissal alone does not prove irritation.
- Page exit rateCompare exits using the same session window.
How to set it up
- PresenceAdd one fixed announcement bar to the predefined site-wide page scope.
- CoverageKeep page coverage the same; testing selected categories is a separate experiment.
- DismissalUse the same close behavior and respect dismissals on later pages.
- Repeated viewsUse visitor-level exposure history rather than counting every page view as a separate person.
- MobileCheck space taken and access to page content.
What to watch when reading the result
- 1A higher announcement bar click-through rate does not settle the test. The predefined campaign action completion rate is the deciding metric; check that overall purchase conversion and page exit rate do not worsen over the same window. Do not read the bar dismissal rate as proof of irritation on its own.
- 2This test measures only whether the banner is present; if you also change its message, you cannot tell what caused the difference. Read the result by each visitor's exposure history rather than counting every page view as a separate person, and check on mobile that the fixed banner can be dismissed and never permanently covers important content.
- 3If the result is not clear-cut, first check that assignment stayed consistent across the site and that visitors split between the arms as planned (sample ratio mismatch). Because the campaign window is limited, use the sample size calculator before launch to find the visitors per arm needed for the effect you care about, and check that eligible traffic per arm during the campaign can reach it.
Frequently Asked Questions
What must be decided before the test starts?
Choose one campaign goal, such as visiting its page or completing a qualifying order. The setup is incomplete without that decision. Measure it among all eligible assigned visitors.
Are more strip clicks enough?
No. Use completion of the predefined campaign goal while monitoring overall conversion and exits over a common window. The strip also occupies page space.
Do frequent dismissals prove the strip is annoying?
Not by themselves. Allow dismissal and respect it on later pages. Review display history without counting each page view as an independent person.
What should limited-time messaging disclose?
Use genuine dates and countdowns, and remove the strip when the offer expires. Do not change presence and copy together. Check mobile space usage and content access.
More tests in UI Elements
All testsAnnouncement Bar Timing: Immediate or Delayed A/B Test
UI elementsCampaign page visit rate
A campaign bar timing test comparing immediate display with one precisely defined delay rule. Set the delay and target campaign action before launch.
Notification Badge: Number or Dot A/B Test Example
UI elementsVisit rate for the indicated section
An experiment example comparing a numbered notification badge with a plain dot. See both arms, the urgency versus pressure reasoning and the KPI.
Adding a Live Chat Button to the Page: A/B Test Idea
UI elementsPurchase conversion rate (CR)
A live chat button on screen against no button at all, written up as an experiment example with both arms, the space trade-offs and the tracked KPI.
