> ## Documentation Index
> Fetch the complete documentation index at: https://docs.9pic.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# 9Pic insights definitions

> Exactly what each 9Pic insights number counts, and the moment it is recorded.

## How 9Pic insights records activity

**9Pic insights** is the activity 9Pic measures inside your event gallery. It appears on the **9Pic insights** tab of [Analytics](https://docs.9pic.ai/products/analytics.md) and on the Overview, marked with its own label.

* **Where it records.** Only in your public event gallery, the page participants open from your event link. Activity in the client selection app (9Pic Select) is not recorded.
* **Plans.** Recording is on for Pro, Business, Custom and Enterprise. Trial and Pay As You Go events do not record it.
* **When it appears.** Within about a minute. Each number is recorded at the moment described below.
* **What it misses.** Visitors who block tracking, and actions in a tab that is closed before it can send them. Automated traffic is left out. Treat every number as a close estimate for comparing days and events, not an exact ledger.
* **Actions, not people.** Every number except **Visits** counts actions. One person searching three times counts three times.

## Visits and gallery

| Number | What it counts | Recorded when | Good to know |
| - | - | - | - |
| **Visits** | Separate visits to the gallery. | A device opens the gallery after 30 minutes or more away. | Not unique people: one person on a phone and a laptop is two visits. Counted per day, so a visit that runs past midnight counts on both days. |
| **Gallery opens** | Times the gallery page loaded. | The gallery finishes loading. | Reloading the page counts again. It also counts when your event uses a custom landing page. |

**Visit journey** shows how many visits **searched for themselves** (a selfie, number or name search for photos or videos; results and certificate lookups don't count), **opened a photo full screen**, and **downloaded or went to checkout** (a photo, album file or video download, or a click to checkout). Each step counts a visit once, and the steps can happen in any order.

**Who is visiting** splits visits by device (phone, computer, tablet) and by country. The country comes from the visitor's internet connection, so travellers count where they are, not where they live.

Visits, the journey and these splits are counted from the day they were added; earlier days show only the totals below, and the tab says so.

## Photos

| Number | What it counts | Recorded when | Good to know |
| - | - | - | - |
| **Photos seen** | Photos that appeared on screen while people scrolled. | At least half of a photo is on screen for half a second. | Counted from 1 in 10 visits and multiplied by 10, so small events read roughly. The same photo counts again when it appears in a different set of results. |
| **Opened full screen** | Photos opened in the large viewer. | A photo in the grid is clicked or tapped. | Moving to the next or previous photo inside the viewer does not count. |
| **Photo downloads** | Single photos downloaded to a phone or computer. | The photo finishes downloading. | Photos only: album files and videos are counted separately. A download that fails does not count. |

## Album downloads

People who find their photos by bib or selfie can download them together. Each download is a file of up to 100 photos or 20 MB, so a runner with many photos downloads several files, and **each file counts once**.

| Number | What it counts | Recorded when |
| - | - | - |
| **Album downloads started** | Album files people started to download. | The download button for a file is pressed, including **Retry** and **Download again**. |
| **Album downloads finished** | Album files that reached the device. | The file arrives complete and the browser starts saving it. |
| **Album downloads failed** | Album files that stopped with an error. | The download fails. The tab splits failures by reason, for example the connection dropped or it took longer than 2 minutes. |

## Finding their photos

The gallery's search box has four modes. **Number searches** and **Name searches** both say which mode was used:

| Mode | What the visitor was looking for |
| - | - |
| **Photos** | Their photos. |
| **Results & certificates** | Their race result and certificate. No photos are shown. |
| **Personalised video** | Their personalised highlight video. |
| **Video clips** | Their video clips. |

| Number | What it counts | Recorded when | Good to know |
| - | - | - | - |
| **Number searches** | Searches by bib or result number, in any of the four modes. | **Search** is pressed after typing a bib or result number. | A search that finds nothing still counts. Opening a link that already contains a search does not. |
| **Name searches** | Runners found by typing their name, in any of the four modes. | The visitor picks a runner from the name suggestions, or presses **Search** after a name matched exactly one runner. | Typing a name without finding or picking a runner does not count. |
| **Selfie searches** | Selfies that finished matching. The tab splits them into **Photos**, **Video clips** and **Highlight video** (the selfie used to personalise a highlight video). | The selfie has been processed, not when the button is pressed. | A selfie that matched nothing still counts. Rejected selfies (no face found, or an unsupported photo), failed searches and results reopened from an earlier selfie do not. |

The **Overview** shows a separate **Selfie searches** total from your event records. That total counts every selfie submitted, including ones that matched nothing, those from other apps and from visitors who block tracking, so it is usually higher. See [Event records definitions](https://docs.9pic.ai/products/analytics/event-records-definitions.md#selfie-searches).

## Certificates

| Number | What it counts | Recorded when | Good to know |
| - | - | - | - |
| **Certificates opened** | Times the certificate window was opened. | Someone opens a certificate from **Results & certificates**. | Counted once per runner while the page stays open; opening the same runner's certificate again does not add to it. |
| **Certificates saved** | Certificates downloaded, split by format (PNG, JPG, PDF, and custom designs). | The image or PDF has been created and the browser starts saving it. | Each format saved counts once. |

## Videos

| Number | What it counts | Recorded when | Good to know |
| - | - | - | - |
| **Clips shown** | Video clips that loaded and were at least half on screen. | A clip is ready to play and at least half of it is on screen. | Clips loaded further down a long list count only once they are scrolled into view. |
| **Plays started** | Times someone pressed play. | Playback starts in the clip player or in the personalised highlight video. | Counted once per clip on the page. Plays inside the personalised video template player are not counted. |
| **Video downloads** | Video clips, highlight videos and full race videos downloaded. The tab splits clips from highlight videos. | The download finishes. For videos the browser saves directly, when the download button is pressed. | Photos are counted under **Photo downloads**. |

## Buying photos

| Number | What it counts | Recorded when | Good to know |
| - | - | - | - |
| **Went to checkout** | Times someone left the gallery for checkout, split by how they found their photos (bib, selfie or video clip). | **Purchase photos**, **Continue to purchase**, or a video clip's buy button is pressed. | This is interest, not a payment. Paid orders are on the Analytics **Overview**; revenue is in [Transactions](https://docs.9pic.ai/products/checkout/transactions.md). Pre-booking and claim buttons are not included. |

## Changes to how numbers are counted

On older days, some numbers were counted differently. Keep this in mind when comparing with earlier days or events.

* **Photo downloads** counted when the download started, so failed downloads were included, and it also included video clip and highlight video downloads. **Video downloads** didn't exist yet.
* **Number searches** included name searches; **Name searches** read 0.
* **Selfie searches** were not split into photos, video clips and highlight video.
* **Clips shown** (then **Videos opened**) counted every clip loaded in a results list, even off screen.
* **Plays started** missed plays in the main clip player, so it read low.

## Not recorded

* Activity in the client selection app (9Pic Select).
* Gallery actions in Google Analytics. Google Analytics shows page traffic only; searches, downloads and other gallery actions are counted here.
* Searches that return no results, as a separate number. They are included in the search totals above.
* How long people watched a video.
* Who the visitors were. 9Pic insights stores no names, emails or bib numbers.

## Related

> [card] [Metric Definitions](https://docs.9pic.ai/products/analytics/definitions.md)
>
> Every Analytics number, its source and where it is defined.

> [card] [Event records definitions](https://docs.9pic.ai/products/analytics/event-records-definitions.md)
>
> Exact counts from your event: searches, orders, photos and credits.

> [card] [Analytics](https://docs.9pic.ai/products/analytics.md)
>
> The Overview, 9Pic insights and Google Analytics tabs.

> [card] [Event Analytics API](https://docs.9pic.ai/api-reference/event-analytics.md)
>
> Read the same estimates from your own systems.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.