Skip to main content
Document usage analytics show you which pieces of content in your knowledge base are actually being used by your AI—and which are sitting unused.

Viewing Document Usage

1

Navigate to your datasets

Go to Data → Datasets
2

Select a dataset

Choose the dataset you want to analyze
3

View document list

Browse the list of documents in your dataset
4

Access detailed usage

Click on any document to see comprehensive usage metrics and analytics

Key Metrics per Document

Understanding these metrics helps you identify which documents are performing well and which need attention.

Retrieval Count

How many times this document was retrieved across all traces.

Unique Queries

How many different queries retrieved this document.
A document with 100 retrievals from only 2 unique queries is less valuable than one with 100 retrievals from 50 unique queries.
Real-world comparison:

Average Relevance Score

Mean relevance score when this document was retrieved.
Red Flag Alert: High retrieval count + low average relevance = your retrieval system is finding this document, but it’s not actually a good match.Consider these fixes:
  • Improve the document content to be more focused
  • Fix or regenerate embeddings
  • Adjust retrieval parameters or similarity thresholds

Last Retrieved

When this document was most recently used.

User Feedback Correlation

How users rated traces that used this document. This metric shows you the quality of your documents from your users’ perspective:

Thumbs Up Count

Traces using this document that received positive feedback

Thumbs Down Count

Traces using this document that received negative feedback

Satisfaction Rate

Percentage of positive feedback overall

Document Details Page

Click on any document to access comprehensive information and insights.

Full Content

The complete text of this document chunk, exactly as stored in your vector database. This lets you see precisely what your AI has access to when this document is retrieved.

Metadata

All fields synced from your vector database provide context about the document:
  • Source — Original file or URL where this content came from
  • Last updated — When the source was last modified
  • Tags — Categories or labels for organization
  • Custom fields — Any other metadata you’ve configured

Usage Timeline

A graph showing document retrievals over time reveals important patterns:

Recent Traces

List of most recent traces that retrieved this document:
  • Trace ID — Link to the full trace for detailed analysis
  • Query — What the user asked
  • Timestamp — When this retrieval happened
  • User feedback — Thumbs up/down if available
Click through to see the full trace and understand exactly how this document was used in context.
Documents that are frequently retrieved alongside this one reveal important relationships:

Sorting and Filtering Documents

Find exactly the documents you need to review with powerful sorting and filtering options.

Sort Options

Filter Options

Use Cases

Here’s how to apply document usage analytics to solve real problems.

Find High-Impact Documents to Update

Goal: Focus your limited time on updating what matters most.
1

Sort by Most Retrieved

Identify your most-used documents
2

Check last updated dates

Review the “Last Updated” date for your top 20 documents
3

Identify outdated high-impact docs

Find old documents with high retrieval counts
4

Update source files

Make improvements to those documents in your original source files
5

Re-sync data source

Sync the updates to your vector database
Result: Maximum impact from your update efforts—you’re improving the documents that matter most.

Remove Unused Documents

Goal: Clean up your vector database for better performance.
1

Filter for zero retrievals

Find documents with zero retrievals in the last 60 days
2

Review each document

Examine the content and metadata
3

Determine the root cause

Ask: “Is this truly irrelevant, or just poorly embedded?”
4

Remove irrelevant docs

Delete truly irrelevant documents from your vector database
5

Re-embed valuable docs

For documents that should be findable, regenerate embeddings
Result: Leaner database, faster retrievals, and better-quality results.

Investigate Low-Quality Documents

Goal: Fix documents that are retrieved but not helpful.
1

Filter for problematic docs

Find documents with high retrieval count + low average relevance (< 0.6)
2

Read the document content

Review what’s actually in the document
3

Check recent traces

Look at traces that recently used this document
4

Diagnose the issue

Determine if the problem is:
  • Content is wrong/outdated → Update the content
  • Content is fine but embeddings are bad → Re-embed the document
  • Retrieval parameters are too loose → Adjust similarity threshold
5

Apply the fix

Make the necessary changes based on your diagnosis
Result: Better retrieval quality and more relevant documents in your results.

Track Content Gaps

Goal: Find topics where you need more documentation.
1

Find traces with poor retrieval

Look at traces with no relevant documents retrieved
2

Group by topic

Organize by topic or query type to find patterns
3

Identify patterns

Example: “All pricing questions have no good docs”
4

Create new content

Write new documentation to fill the identified gaps
5

Verify improvement

Add to vector database and confirm retrieval improves
Result: Comprehensive knowledge base with fewer “I don’t know” responses.

Measure Update Impact

Goal: Verify that updating a document improved performance.
1

Record baseline metrics

Note retrieval metrics before update (count, relevance, feedback)
2

Update the document

Make improvements in your source files
3

Re-sync to Arcbeam

Push the updated document to your vector database
4

Wait for data collection

Allow 1-2 weeks for meaningful data
5

Check new metrics

Review the same metrics again
6

Compare before/after

Analyze the impact of your changes
Result: Data-driven confirmation that your updates actually helped.

Debug Wrong Answers

Goal: Fix AI responses that provide incorrect information.
1

View the trace

When AI gives a wrong answer, view the trace in Arcbeam
2

Check retrieved documents

See which documents were used to generate the response
3

Review document content

Click through to see the full content of each document
4

Diagnose the issue

Determine if:
  • Documents contain incorrect information
  • Correct documents weren’t retrieved
  • Wrong documents were prioritized
5

Fix the root cause

  • If documents are wrong, update the source files
  • If documents are missing, add new content
  • If retrieval is broken, adjust parameters
6

Re-sync and verify

Update your dataset and confirm improved outputs
Result: Trace errors back to source data and fix them systematically.

Compliance and Audit Trail

Goal: Demonstrate data provenance for compliance requirements.
1

Generate trace report

Create a report for the required time period
2

Export document usage

Download data showing which documents were accessed
3

Trace to original files

Use source attribution to link back to original files
4

Document the audit trail

Show complete chain from AI output to source document
5

Record access logs

Document which users accessed which information
Result: Full provenance chain for regulatory compliance and auditing.

Exporting Document Usage Data

Export document metrics for external analysis and reporting.
1

Navigate to datasets

Go to Data → Datasets
2

Select your dataset

Choose the dataset you want to export
3

Click Export

Click Export Usage Data
4

Choose format

Select CSV or JSON format
5

Download

Save the file for analysis

CSV Export Contents

The exported CSV includes all key metrics:
  • Document ID
  • Content (truncated or full based on your selection)
  • Retrieval count
  • Unique queries
  • Average relevance score
  • Last retrieved date
  • User feedback statistics

Common Use Cases for Exports

Setting Up Alerts

Get notified about important changes to stay proactive.

Critical Document Alerts

Monitor your most important documents for issues:
1

Tag critical documents

Mark your essential documents with a “critical” tag
2

Set retrieval drop alerts

Get notified if retrieval count drops suddenly
3

Monitor relevance scores

Alert when relevance score declines below threshold
4

Track negative feedback

Receive alerts on negative user feedback
Example Alert: “Pricing Policy Doc” retrieval count dropped 80% in the last week → investigate potential retrieval issue or content problem.

New Content Alerts

Track newly added documents to ensure they’re working properly:
1

Enable new document alerts

Get notified when a new document is synced
2

Monitor initial usage

Track its first 30 days of usage automatically
3

Verify retrieval

Confirm it’s being retrieved as expected

Best Practices

Follow these practices to get the most value from document usage analytics.

Review Top 20 Documents Monthly

Investigate Zero-Retrieval Documents

Every month, check documents that are never retrieved:

Correlate with User Feedback

When users give thumbs down to AI responses:
1

View the trace

Open the trace with negative feedback
2

Check retrieved documents

See which documents were used in that response
3

Look for patterns

If the same document appears in many negative traces, you’ve found the problem
4

Update immediately

Fix that document as soon as possible

Track Seasonal Patterns

Some documents may have seasonal usage patterns that affect your update planning:
  • Tax documents — Retrieved heavily in April
  • Holiday policy docs — Spike in November-December
  • Budget documents — Active at fiscal year end
Plan your content updates and reviews around these patterns.
When creating new content:

Next Steps

Dataset Analytics

Understand patterns across entire datasets

Track Data Changes

Monitor how your data evolves over time

Find Problematic Traces

Identify and debug issues in your AI responses

Understand Retrieval Quality

Deep dive into retrieval performance metrics