> For the complete documentation index, see [llms.txt](https://docs.intelligems.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intelligems.io/analytics/overview/black-friday-live-tracker.md).

# Black Friday Live Tracker

The Intelligems BFCM Tracker gives brands a real time performance view for Q4. It shows revenue, orders, and price levels at the hourly level and benchmarks performance against last year, a typical-day baseline, and the Intelligems Index.

This tool can be found in the [Sitewide Analytics](https://app.intelligems.io/sitewide-analytics/) section, under **Comparison tools** as **Holiday tracker**. It has two tabs. **Your store** shows how your revenue is pacing against last year and against a typical day. **Stores like yours** shows how your holiday bump compares to other stores.

### Holiday Index details

* **Index:** Our Holiday Index is comprised of 2,000+ brands. We normalize each brand's performance relative to a 'typical-day' performance. We then average normalized performance relative to typical day to produce our index measurements
* **Typical-Day performance:** We use average performance from October 1 to October 14, 2026 to establish a typical-day baseline
* **2026 vs. 2025 comparisons:** In our charts, we match based on same day relative to holiday, with Black Friday in the previous year (November 28, 2025) matched to the most recent Black Friday (November 27, 2026)
  * E.g. Monday November 17, 2025 is matched to Monday, November 16, 2026

### **Key Metrics**

1. **Revenue -** "How am I pacing vs. last year?"
   * Hourly: Shows total revenue for the day with a comparison to the same hour last year
   * Q4: Shows total revenue Q4-to-date compared to equivalent dates last year
2. **Revenue (as % of Typical Full Day) -** "How am I pacing vs. a typical day"
   * Hourly: Shows total revenue for the day thus far, divided by revenue for a typical day
     * If you hit a value of 120% by 1 pm, it means you have already exceeded a full normal day of revenue.
   * Q4: Shows average Q4 daily revenue relative to a typical day
     * A value of 120% means that an average Q4 day is +20% above a typical day
3. **Index (as % of Typical Full Day) -** "How is the industry pacing vs. a typical day"
   * Hourly: Shows how total revenue for the day divided by a typical day for our index
     * Note - we do some normalization and adjustments, but easiest to explain as an ‘average’
   * Q4: Shows average Q4 daily revenue relative to a typical day for our index

### **Common comparisons**

To assess Black Friday and Cyber Monday performance, there are a few comparisons that you can do:

1. **Your performance vs. last year -** compare whether you are outperforming last year
2. **Your performance vs. your typical day -** compare the lift you are able to achieve relative to an ordinary day and whether those achieve expected targets
3. **Your % lift vs. Index % lift -** compare whether you generated more lift than observed by the index as a whole
4. **Index vs. last year** - compare whether the market appeared to have larger or smaller than typical levels of lift over the holiday period


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.intelligems.io/analytics/overview/black-friday-live-tracker.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.