Skip to main content

Analytics codebook

Objective

Understanding the metrics available within the PuzzleMe analytics dashboard

Loads

Total Loads

Number of times a PuzzleMe iframe is requested from our server.

Verified Loads

This is the measure used for billing.

If a picker is being used, the number of times the picker has been displayed in a user's browser, plus the number of puzzles loaded through the end modal streak that is shown upon completion, if enabled. Here are some examples to understand it better.

  1. When a user accesses the puzzle picker, selects a puzzle to play: 1st verified load
  2. User accesses the puzzle picker, plays a puzzle, then navigates back to the picker by clicking "All puzzles" in the hamburger menu to select another puzzle: 2nd verified load
  3. User accesses the puzzle picker, completes a puzzle, then selects a different puzzle from the end modal streak picker: 2nd verified load

If a picker is not being used, the number of times a puzzle has been displayed in a user’s browser.

note

This covers both web browsers and apps. This is counted only when Javascript has been executed in a user’s browser and successfully posted back to the PuzzleMe server to tell the database that the row should be initialized.

Ads Invoked

Number of times a pre-roll has been invoked from the iframe. This metric is only relevant for sites that use a pre-roll.

Plays

Unique Plays

Each user has one unique play for a specific puzzle. Note that a user loading the same puzzle twice would count as one unique play. However, the two loads would count as two verified loads.

Unique Users

Number of unique users who loaded at least one puzzle.

Average Play Time

Across all the unique plays, the average time that is clocked on the timer. This is measured in seconds (not hours, minutes). This time is tracked even when a user chooses the setting not to display the timer. Time when the iframe is not in focus (e.g. when a user navigates to a different tab) or when the focus is outside the iframe is not counted.

note

The average play time is under-reported compared to other tools that measure time-on-page because

  1. Based on the setting, the timer may start ticking when a user enters the first letter on a grid. So the time after the page loads but before a user enters the first letter is not included.
  2. A user may pause the timer at any time and still be on the page. However, once a user enters a letter, the timer is un-paused.
  3. The timer stops when a puzzle is completely filled. However, users may spend more time on the page, which is not included in our stat.
  4. The time on the picker page is not included in this metric.

Plays Completed

Of all the unique plays, the number of plays where the puzzle was completely solved online. Note: This number does not include those who print and solve the puzzle offline. So the actual number of people who solve the puzzle completely is higher.

Plays Completed Correctly

Of all the unique plays, the number of plays where the puzzle is completed correctly.

Prints

Number of unique plays where a user printed at least once using any of the print options: black / filled letters / solution.

Segmentation

Browser Type

This is tracked for each verified load.

note

Browser Type is parsed using the User Agent string of the browser. Browser type is classified into one of the following categories: Chrome, Safari, Edge, IE, Firefox, WebView, Other browsers.

Device Type

This is tracked for each verified load.

note

Device Type is parsed using the User Agent string of the browser. Device type is classified into one of the following categories: Desktop, Tablet, Mobile

OS Type

This is tracked for each verified load.

note

OS type is parsed using the User Agent string of the browser. OS Type is classified into one of the following categories: Mac OS, Windows, Android, iOS, Other OS.