hellotext · pelcasandra · Aug 2, 2026 · Aug 2, 2026 · Aug 2, 2026 · Aug 2, 2026
diff --git a/_analytics-reporting-attribution/analytics-overview.md b/_analytics-reporting-attribution/analytics-overview.md
@@ -1,5 +1,6 @@
 ---
 languages: ["en", "es"]
+navigation_group: foundations
 
 en:
   title: Analytics, reporting, and attribution overview

diff --git a/_analytics-reporting-attribution/campaign-reporting.md b/_analytics-reporting-attribution/campaign-reporting.md
@@ -1,5 +1,6 @@
 ---
 languages: ["en", "es"]
+navigation_group: source_reporting
 
 en:
   title: Campaign reporting

diff --git a/_analytics-reporting-attribution/dashboard-guide.md b/_analytics-reporting-attribution/dashboard-guide.md
@@ -0,0 +1,20 @@
+---
+languages: ["en", "es"]
+navigation_group: foundations
+
+en:
+  title: Dashboard guide
+  description: Read the 14-day overview, tracked actions, campaign calendar, and detailed business and operations reports from one place.
+es:
+  title: Guía del Dashboard
+  description: Interpreta el resumen de 14 días, las acciones registradas, el calendario de campañas y los reportes detallados de negocio y operaciones.
+
+permalink: dashboard-guide
+permalink_es: guia-dashboard
+
+layout: guide
+topic: analytics-reporting-attribution
+popular: false
+---
+
+{% translate_file analytics-reporting-attribution/dashboard-guide.md %}
diff --git a/_analytics-reporting-attribution/data-completeness-and-reporting-gaps.md b/_analytics-reporting-attribution/data-completeness-and-reporting-gaps.md
@@ -0,0 +1,20 @@
+---
+languages: ["en", "es"]
+navigation_group: measurement_attribution
+
+en:
+  title: Data completeness and reporting gaps
+  description: Diagnose missing metrics and reconcile differences between the Dashboard, detailed reports, customer activity, and external systems.
+es:
+  title: Integridad de datos y diferencias en reportes
+  description: Diagnostica métricas faltantes y concilia diferencias entre el Dashboard, reportes detallados, actividad de clientes y sistemas externos.
+
+permalink: data-completeness-and-reporting-gaps
+permalink_es: integridad-datos-diferencias-reportes
+
+layout: guide
+topic: analytics-reporting-attribution
+popular: false
+---
+
+{% translate_file analytics-reporting-attribution/data-completeness-and-reporting-gaps.md %}
diff --git a/_analytics-reporting-attribution/demand-insights-guide.md b/_analytics-reporting-attribution/demand-insights-guide.md
@@ -0,0 +1,20 @@
+---
+languages: ["en", "es"]
+navigation_group: business_performance
+
+en:
+  title: Demand insights guide
+  description: Understand unfulfilled product requests, estimated missed revenue, affected products, and unfulfilled demand rate.
+es:
+  title: Guía de Insights de demanda
+  description: Entiende solicitudes de producto no satisfechas, ingresos perdidos estimados, productos afectados y tasa de demanda no satisfecha.
+
+permalink: demand-insights-guide
+permalink_es: guia-insights-demanda
+
+layout: guide
+topic: analytics-reporting-attribution
+popular: false
+---
+
+{% translate_file analytics-reporting-attribution/demand-insights-guide.md %}
diff --git a/_analytics-reporting-attribution/performance-report-guide.md b/_analytics-reporting-attribution/performance-report-guide.md
@@ -0,0 +1,20 @@
+---
+languages: ["en", "es"]
+navigation_group: business_performance
+
+en:
+  title: Performance report guide
+  description: Understand conversation conversion, time to conversion, escalation, available breakdowns, and recent results.
+es:
+  title: Guía del Reporte de rendimiento
+  description: Entiende conversión de conversaciones, tiempo de conversión, Derivación, desgloses disponibles y resultados recientes.
+
+permalink: performance-report-guide
+permalink_es: guia-reporte-rendimiento
+
+layout: guide
+topic: analytics-reporting-attribution
+popular: false
+---
+
+{% translate_file analytics-reporting-attribution/performance-report-guide.md %}
diff --git a/_analytics-reporting-attribution/playbook-reporting.md b/_analytics-reporting-attribution/playbook-reporting.md
@@ -1,5 +1,6 @@
 ---
 languages: ["en", "es"]
+navigation_group: source_reporting
 
 en:
   title: Playbook reporting

diff --git a/_analytics-reporting-attribution/revenue-report-guide.md b/_analytics-reporting-attribution/revenue-report-guide.md
@@ -0,0 +1,20 @@
+---
+languages: ["en", "es"]
+navigation_group: business_performance
+
+en:
+  title: Revenue report guide
+  description: Understand total and attributed revenue, the report's purchase-date basis, source breakdowns, and export.
+es:
+  title: Guía del Reporte de ingresos
+  description: Entiende los ingresos totales y atribuidos, la fecha de compra usada por el reporte, sus desgloses y la exportación.
+
+permalink: revenue-report-guide
+permalink_es: guia-reporte-ingresos
+
+layout: guide
+topic: analytics-reporting-attribution
+popular: false
+---
+
+{% translate_file analytics-reporting-attribution/revenue-report-guide.md %}
diff --git a/_analytics-reporting-attribution/sales-attribution.md b/_analytics-reporting-attribution/sales-attribution.md
@@ -1,5 +1,6 @@
 ---
 languages: ["en", "es"]
+navigation_group: measurement_attribution
 
 en:
   title: How we attribute sales

diff --git a/_analytics-reporting-attribution/service-quality-report-guide.md b/_analytics-reporting-attribution/service-quality-report-guide.md
@@ -0,0 +1,20 @@
+---
+languages: ["en", "es"]
+navigation_group: operations_experience
+
+en:
+  title: Service quality report guide
+  description: Understand AI and team resolution, SLA compliance, unresolved conversations, response times, and agent performance.
+es:
+  title: Guía del Reporte de calidad de servicio
+  description: Entiende resolución por IA y equipo, cumplimiento de SLA, conversaciones no resueltas, tiempos de respuesta y rendimiento de agentes.
+
+permalink: service-quality-report-guide
+permalink_es: guia-reporte-calidad-servicio
+
+layout: guide
+topic: analytics-reporting-attribution
+popular: false
+---
+
+{% translate_file analytics-reporting-attribution/service-quality-report-guide.md %}
diff --git a/_analytics-reporting-attribution/tracked-links.md b/_analytics-reporting-attribution/tracked-links.md
@@ -1,5 +1,6 @@
 ---
 languages: ["en", "es"]
+navigation_group: measurement_attribution
 
 en:
   title: Tracked links

diff --git a/_analytics-reporting-attribution/workload-capacity-report-guide.md b/_analytics-reporting-attribution/workload-capacity-report-guide.md
@@ -0,0 +1,20 @@
+---
+languages: ["en", "es"]
+navigation_group: operations_experience
+
+en:
+  title: Workload & capacity report guide
+  description: Understand active load, handled and resolved work, capacity pressure, session efficiency, and the live operational queue.
+es:
+  title: Guía del Reporte de carga y capacidad
+  description: Entiende carga activa, conversaciones manejadas y resueltas, presión de capacidad, eficiencia de sesión y la cola operativa en vivo.
+
+permalink: workload-capacity-report-guide
+permalink_es: guia-reporte-carga-capacidad
+
+layout: guide
+topic: analytics-reporting-attribution
+popular: false
+---
+
+{% translate_file analytics-reporting-attribution/workload-capacity-report-guide.md %}
diff --git a/_config.yml b/_config.yml
@@ -90,6 +90,13 @@ collections:
   analytics-reporting-attribution:
     order:
       - analytics-overview.md
+      - dashboard-guide.md
+      - revenue-report-guide.md
+      - performance-report-guide.md
+      - demand-insights-guide.md
+      - service-quality-report-guide.md
+      - workload-capacity-report-guide.md
+      - data-completeness-and-reporting-gaps.md
       - playbook-reporting.md
       - campaign-reporting.md
       - tracked-links.md

diff --git a/_data/guide_groups.yml b/_data/guide_groups.yml
@@ -34,3 +34,20 @@ captures:
   - key: checkout
     en: Checkout opt-in
     es: Suscripción en checkout
+
+analytics-reporting-attribution:
+  - key: foundations
+    en: Start here
+    es: Primeros pasos
+  - key: business_performance
+    en: Business Performance
+    es: Rendimiento del negocio
+  - key: operations_experience
+    en: Operations & Experience
+    es: Operaciones & Experiencia
+  - key: source_reporting
+    en: Source reporting
+    es: Reportes por fuente
+  - key: measurement_attribution
+    en: Measurement & attribution
+    es: Medición y atribución
diff --git a/_i18n/en/analytics-reporting-attribution/analytics-overview.md b/_i18n/en/analytics-reporting-attribution/analytics-overview.md
@@ -6,6 +6,30 @@ This section connects three related questions:
 - Which customer actions happened after the message?
 - Which revenue was attributed to Hellotext?
 
+## Revenue report
+
+The Revenue report shows purchases completed during the selected period, including total revenue and the portion attributed to eligible Hellotext activity.
+
+Use it when you need to compare revenue attributed to AI or classified as team-managed, inspect credited Campaigns and Playbooks, or reconcile individual attributed purchases.
+
+Keep reading: [Revenue report guide]({% link _analytics-reporting-attribution/revenue-report-guide.md %}).
+
+## Performance report
+
+The Performance report follows conversations from their start through later conversion and escalation outcomes.
+
+Use it when you need to compare conversion rate, time to conversion, escalation rate, and AI-only versus team-managed conversion paths.
+
+Keep reading: [Performance report guide]({% link _analytics-reporting-attribution/performance-report-guide.md %}).
+
+## Demand insights
+
+Demand insights identifies product requests that could not be fulfilled, the products and variants affected, and the estimated value of those missed opportunities.
+
+Use it when you need to prioritize inventory, catalog, availability, or alternative-recommendation problems based on observed customer demand.
+
+Keep reading: [Demand insights guide]({% link _analytics-reporting-attribution/demand-insights-guide.md %}).
+
 ## Campaign reports
 
 Campaign reports help you review delivery, engagement, clicks, conversions, replies, and attributed revenue for a one-time send.
@@ -22,6 +46,22 @@ Use playbook reporting when you need to compare attributed revenue, conversion b
 
 Keep reading: [Playbook reporting]({% link _analytics-reporting-attribution/playbook-reporting.md %}).
 
+## Service quality report
+
+The Service quality report compares AI and team resolution, SLA compliance, unresolved conversations, response-time distribution, and agent performance.
+
+Use it when you need to understand how conversations are being resolved and whether a service problem is concentrated in a channel, team, teammate, AI agent, or resolution path.
+
+Keep reading: [Service quality report guide]({% link _analytics-reporting-attribution/service-quality-report-guide.md %}).
+
+## Workload & capacity report
+
+The Workload & capacity report compares active load, handled and resolved work, concurrency, assignments, transfers, capacity pressure, session efficiency, and the current operational queue.
+
+Use it when you need to understand how Inbox work is distributed during a period and what needs attention right now.
+
+Keep reading: [Workload & capacity report guide]({% link _analytics-reporting-attribution/workload-capacity-report-guide.md %}).
+
 ## Attribution
 
 Attribution explains when Hellotext receives credit for a sale and when it does not.
@@ -57,6 +97,11 @@ If you are reviewing your first launch, start with [Measure success in your firs
 ## Related guides
 
 - [Measure success in your first 7 days]({% link _getting-started/measure-success-first-7-days.md %})
+- [Revenue report guide]({% link _analytics-reporting-attribution/revenue-report-guide.md %})
+- [Performance report guide]({% link _analytics-reporting-attribution/performance-report-guide.md %})
+- [Demand insights guide]({% link _analytics-reporting-attribution/demand-insights-guide.md %})
+- [Service quality report guide]({% link _analytics-reporting-attribution/service-quality-report-guide.md %})
+- [Workload & capacity report guide]({% link _analytics-reporting-attribution/workload-capacity-report-guide.md %})
 - [Playbook reporting]({% link _analytics-reporting-attribution/playbook-reporting.md %})
 - [Create a campaign]({% link _campaigns/creating-a-campaign.md %})
 - [Pricing, billing, and plans overview]({% link _billing/billing-overview.md %})

diff --git a/_i18n/en/analytics-reporting-attribution/campaign-reporting.md b/_i18n/en/analytics-reporting-attribution/campaign-reporting.md
@@ -6,15 +6,19 @@ To open one, go to **Campaigns**, open the delivered campaigns view, and select
 
 The report opens with **First 14 days** selected. You can switch to the first 7 or 30 days, or choose a custom range.
 
-The selected period updates the metrics, chart, funnel, message results, revenue breakdowns, and recent activity together. It filters when those results were recorded; it does not change the attribution window used to decide whether a purchase belongs to the campaign.
+The selected period is based on when campaign messages were delivered. The metrics, chart, funnel, message results, and revenue breakdowns follow the recipient messages delivered during that period. Eligible clicks and purchases can happen later and remain assigned to the original delivery date.
+
+For example: **Delivered April 7 → Purchased April 10 → Counted on April 7 in the campaign report.** The Revenue report counts that same purchase on April 10 because Revenue uses purchase date.
+
+Changing the reporting period does not change the attribution window used to decide whether a purchase belongs to the campaign.
 
 A campaign message can remain listed even when its results fall outside the selected range. In that case, its row can show zero values until you choose a period that includes its activity.
 
 ## Read the campaign summary
 
 The four summary cards answer different questions:
 
-* **Attributed revenue:** how much revenue came from purchases attributed to this campaign during the selected period.
+* **Attributed revenue:** how much revenue came from eligible purchases attributed to campaign messages delivered during the selected period.
 * **Average ROI:** attributed revenue divided by the estimated cost of delivering the campaign messages.
 * **Conversion:** attributed purchases divided by delivered messages.
 * **Revenue/message:** attributed revenue divided by delivered messages.
@@ -47,9 +51,9 @@ This lets you compare the actual messages without mixing click performance with
 
 ## Understand time to conversion
 
-**Time to conversion** shows how long it took attributed sales to happen after the campaign launched, using ranges such as the same day, 1–3 days, 4–7 days, and later periods.
+**Time to conversion** shows how long it took attributed sales to happen after message delivery, using ranges such as the same day, 1–3 days, 4–7 days, and later periods.
 
-The report period filters when the attributed sale was recorded. A sale can therefore appear days after message delivery while still belonging to the campaign under the applicable attribution rules.
+The report period selects the original message deliveries. A sale can happen days later and still be counted with its delivery date when it belongs to the campaign under the applicable attribution rules.
 
 ## Compare revenue by channel and segment
 
@@ -80,7 +84,7 @@ Hellotext evaluates the available evidence and its precedence before assigning a
 
 ## When results are missing or unexpected
 
-First confirm that the selected period includes the campaign activity. Then verify that tracked links and purchase events are available. Supported commerce integrations can send purchase data automatically; custom storefronts can use [Hellotext.js or the API]({% link _developers/tracking-events.md %}).
+First confirm that the selected period includes the eligible message delivery. Then verify that tracked links and purchase events are available. Supported commerce integrations can send purchase data automatically; custom storefronts can use [Hellotext.js or the API]({% link _developers/tracking-events.md %}).
 
 If activity is still missing, follow [Troubleshoot missing signals or activity]({% link _troubleshooting-deliverability/troubleshoot-missing-signals-or-activity.md %}).