How Teacup counts views, starts, finishes and orders

#The short version

Every number in Teacup Quiz’s analytics comes from shoppers taking your live quizzes on your store. Each shopper’s go at a quiz is one run. A run begins when they answer the first question. It holds their answers, their results, what they added to the cart and what they ordered, but no name, email address or IP address.

Finishes are what your plan counts: every counted finish is one completed quiz toward your plan’s monthly limit, across all your quizzes, A/B test versions included. See Plans.

#Views

A view is counted when a shopper can actually see the quiz:

• A quiz on a page (a section or block) counts once at least half of it is on screen. A quiz taller than the screen counts once it fills half the screen.
• A popup counts when it opens, whether from the floating button, a product page button, a #teacup link or by itself.
• Each quiz counts once per page load. A shopper who sees the quiz on three page loads counts three views.

A quiz far down a page that shoppers don’t scroll to gets no views. A low view count next to good store traffic usually means the quiz sits too low on the page, or in a spot shoppers skip.

#Starts and answers

A run starts when the shopper answers the first question. A welcome screen alone doesn’t start one: a shopper who clicks the start button and then leaves counts as viewed, not started.

• A link that opens the quiz with answers already picked (?tq= or ?q1=) starts the run right away. See Links that start with an answer.
• A shopper who reloads the page, or moves to another page in the same tab within an hour, carries on with the same run.
• Retake the quiz on the results starts a new run, which counts as a new start.
• Each question counts as answered once per run, with the answers picked the first time. A question the shopper skips (when you let shoppers skip it) counts as answered too, with no answer picked, so a skip isn’t counted as leaving. Where shoppers leave and the “% answer it” badges in the editor use these counts.

#Finishes

A run finishes when the shopper reaches their results:

• With an email step, after the shopper leaves their email or skips it.
• When results show on a page of your store, once that page shows them.
• When a result sends shoppers straight to its landing page, just before they’re sent there.
• A shopper whose answers match nothing gets your fallback or the no-match message. They’ve reached their results too.

Because finishes are what plans count, Teacup Quiz only counts the ones a real shopper could make:

• A run that reaches its results faster than a person could read and answer the questions isn’t counted.
• When a store suddenly gets far more finishes in one hour than it usually does, the unusual extra ones aren’t counted or billed. This protects you from made-up traffic. A real rush, like a launch or an email campaign, still counts in full: every store can have at least 300 finishes an hour on Free, 2,000 on Starter, 6,000 on Growth and 15,000 on Plus, and more once its busiest hours are busier.
• Many finishes from one device or network within a few minutes, such as a tablet in your shop that many customers use, may not all be counted.

Runs that weren’t counted as finished show a Didn’t finish tag in Responses, like shoppers who left partway.

#Added to cart

A run counts as added to cart the first time quiz products go into the cart, in either of two ways:

• The shopper adds from their results: Add to cart on a product, Add all to cart (Add all · save 10% with a bundle discount), or a close match’s button.
• The shopper adds a product the quiz recommended to them somewhere else in your store, such as on a result’s landing page, within 7 days of seeing their results, in the same browser. When a result has no products of its own, any product counts. This second way works through the Teacup Quiz web pixel, so it needs the shopper to allow analytics.

Later adds in the same run don’t raise the count, so Added to cart means shoppers who added, not products added.

#Orders and sales

The Teacup Quiz web pixel sees each completed checkout on your store and looks for quiz products in it. An order line counts for a quiz when:

• It was added from the quiz’s results. Teacup Quiz marks these lines with a hidden line property, so they count whenever the shopper checks out with that cart.
• Or the product is one the quiz recommended to that shopper, bought within 7 days of seeing their results, in the same browser. When the quiz recommended no products (a result that only links to a page), any product counts.

The order also needs a run Teacup Quiz recorded, started at most 8 days before the order. Each order counts once per quiz, however often the pixel reports it.

#What’s never counted

These don’t count anywhere in your analytics, and don’t count toward your plan:

• Play and the preview in the quiz editor.
• Your theme editor, including the quiz blocks you’re placing.
• Theme previews: any theme other than your live one.
• Visits opened with ?teacup_test, such as Open your store in the setup guide or Try it on your store in Put it on your store. This lasts for the rest of that browser tab.
• Shoppers who say no to analytics in your store’s cookie banner. Teacup Quiz doesn’t record their views, runs, carts or orders.

#Days, ranges and updates

• Every day in Teacup Quiz is a UTC day, whatever your store’s time zone. A shopper who starts at 11 p.m. in New York is counted on the next day.
• The ranges (7 days, 30 days and 90 days, or Last 7 days, Last 30 days and Last 90 days on a quiz’s page) end with today (UTC), which is only partly over. A quiz’s page also has Custom, for the days you pick: both the first and the last day are included, up to 366 days.
• Starts and finishes are each counted on the day they happen, so a run that starts just before midnight UTC can finish on the next day.
• Numbers update as shoppers take your quizzes. Every analytics page reads them fresh when it opens: reload the page to see the latest.

To read each page, see Reading your analytics. When two pages don’t agree, see Why numbers differ.