Skip to content
Peekbird

QA and preview

Check an experiment on your live site before your visitors see it: links that turn on QA mode, force a variation, act as if you were in another country or record your visit. QA visits never count in your results.

Preview links

Add these to any page address on your site:

AddWhat it does
?peekbird_qa=1Runs experiments in QA as well as running ones. You're placed in a variation like any visitor, so you may get the control: force a variation to see a particular one.
?peekbird_force=experiment:variationShows you that variation, whatever the experiment's audience and traffic split, on the pages the experiment runs on. Works for experiments in QA and running ones. Force several at once with commas: ?peekbird_force=hero:b,cart:c.
?peekbird_country=DEActs as if you were in that country (a two-letter code), to check location audiences. Only the country: region and city conditions see none. It doesn't change whether your site asks you for consent.
?peekbird_record=1Records your visit whatever the sample rate, if recordings are on for your site. It shows in Sessions marked QA.
?peekbird_debug=1Logs every decision in the browser console: which experiments ran and which variation you got, or why not (such as "URL does not match", "not in audience", "outside traffic allocation"), whether the visit is recorded, and errors in variation code.
  • Each is remembered in a cookie until you close the browser, in every tab, so it follows you from page to page. Set it to 0 to turn it off: ?peekbird_qa=0.
  • A new ?peekbird_force replaces the variations you forced before.
  • The keys are in the experiment's Setup: Experiment key under Basics → Advanced, and each Variation key under Variations. The experiment's Preview & QA tab has a ready link for each variation.
  • To check a location audience on an experiment in QA, combine two: ?peekbird_qa=1&peekbird_country=DE. Forcing a variation would skip the audience.
  • Audiences are checked when you first enter an experiment; after that, you keep your variation. To check one again from the start, use a private window. Closing it also clears the variation you tested, so your later visits don't keep it.
  • If your site waits for your consent, agree in your consent banner first: until then Peekbird doesn't run, and neither do these links.

QA visits

A visit with ?peekbird_qa, ?peekbird_force, ?peekbird_country or ?peekbird_record on, opened in the visual editor, or opened by the install check (below), is a QA visit. ?peekbird_debug alone doesn't make one: it only logs.

QA visits never count in experiment results, Analytics, Heatmaps or your plan's tracked visits. They show marked QA in Live, and in Sessions when they're recorded, and they make up each experiment's QA traffic. Pages you viewed before opening a QA link count as usual.

The QA status

Start in QA, in a draft's Review step once it has a primary goal, puts the experiment on your live site for QA links only: visitors never see it. Each change you save is published at once for testers. When it's ready, Start it, or go Back to draft. Results count from the moment you start it, without the QA visits.

  1. Open the page with ?peekbird_qa=1: the Preview & QA tab has the link.
  2. Complete each goal: visit the thank-you page, click the button, place a test order.
  3. Open Results. While the experiment is in QA, it shows QA traffic: Are the goals firing?, with each goal fired or not yet. Details has the numbers. Then start it.

To check goals on an experiment that's already running, turn on Show QA traffic in results in the site's Testing settings (under A/B testing). Its results pages then have a Visitors / QA traffic switch.

On your servers

The server SDKs honour the same links: ?peekbird_force and ?peekbird_qa on the page's address, or the cookies the snippet keeps for them, force a variation of an "In your code" test or run tests in QA there too. Those visits are QA visits as well.

Testers get the newest version

With ?peekbird_qa or ?peekbird_force on, the snippet first asks Peekbird, uncached, whether your site's file has a newer version than the copy the page has, and loads it if so: you see a change the moment it's saved. The page stays hidden meanwhile, for 3 seconds at most, and if Peekbird doesn't answer within 1.5 seconds, the page's copy runs. Visitors never wait for this.

Everyone else gets changes within about a minute: the file is cached for 60 seconds, and a browser or the CDN may use its older copy once more while it fetches the new one. See Speed, CSP and single-page apps.

The install check

In Install & data, Check installation opens a page of your site with ?peekbird_check= and a one-time code, and shows how Peekbird runs there. Enter the page's address and click Open and check; the results appear in the card once the page has loaded. A code works for 30 minutes. The check runs whatever consent says, and reports how the page loads Peekbird, nothing about you.

  • The snippet: whether the page has this site's snippet, another site's, or the same one more than once.
  • Where it is: in the <head> and loaded before the page shows, as it should be. It warns when it's in the body, loaded asynchronously (as Tag Manager does), behind more than 3 scripts that hold up the page, or when it arrived after the page first appeared: in each case, visitors in a test may see the original page flash.
  • Settings: whether the page has the site's latest settings. Slightly older ones catch up as caches refresh.
  • Running: running, waiting for consent, or declined in this browser. It's on the page but didn't start means something on the page stopped it: look for errors in the browser console.
  • Domain: whether the page's address is one of the site's domains, which you list in Site settings.
  • Shopify: whether the Peekbird app is connected, and when the last checkout order arrived.

No report usually means the snippet isn't on that page, or an ad blocker in your browser stops it. Behind a password page, entering the password drops the code from the address: once you're in, open the page again from the card.

See what your visitors see.

Start free in a few minutes: one snippet, every feature. Move to a bigger plan when you need more tracked visits.