PDF Usage Tracking ID Reader

Extract embedded tracking ID and page serial values from tracked PDF files

Read hidden tracking information from PDFs generated by usage tracking tools.

Detection order:

PDF metadata (subject/keywords)
Hidden page text serial (e.g. TRACKID-P0001)

Returns JSON with per-page serial detection and inferred global tracking ID.

This tool is designed to read output from pdf-usage-tracking-id.

Example Results

2 examples

Read Auto-generated Tracking ID

Extracts metadata tracking id and page serial list from timestamp-hash tracked PDF

{
  "trackingId": "TRK-4A964CB788141089",
  "metadataTrackingId": "TRK-4A964CB788141089",
  "inferredTrackingId": "TRK-4A964CB788141089",
  "foundSerialPages": 4,
  "detectionSource": "metadata",
  "pageSerials": [
    {
      "page": 1,
      "serial": "TRK-4A964CB788141089-P0001",
      "found": true
    },
    {
      "page": 2,
      "serial": "TRK-4A964CB788141089-P0002",
      "found": true
    }
  ]
}

View input parameters

{ "sourceFile": "/Users/quyue/www/elysia-tools/public/samples/pdf/pdf-usage-tracking-id-example1.pdf" }

Read Custom Distribution ID

Parses custom distribution id and confirms serial suffixes across all pages

{
  "trackingId": "DIST-2026-Q1-ALPHA",
  "metadataTrackingId": "DIST-2026-Q1-ALPHA",
  "inferredTrackingId": "DIST-2026-Q1-ALPHA",
  "foundSerialPages": 4,
  "detectionSource": "metadata",
  "pageSerials": [
    {
      "page": 1,
      "serial": "DIST-2026-Q1-ALPHA-P0001",
      "found": true
    },
    {
      "page": 2,
      "serial": "DIST-2026-Q1-ALPHA-P0002",
      "found": true
    }
  ]
}

View input parameters

{ "sourceFile": "/Users/quyue/www/elysia-tools/public/samples/pdf/pdf-usage-tracking-id-example2.pdf" }

Source PDF File *

Click to upload file or drag and drop file here

Maximum file size: 300MB Supported formats: application/pdf

Key Facts

Category: PDF Tools
Input Types: file
Output Type: json
Sample Coverage: 4
API Ready: Yes

Overview

The PDF Usage Tracking ID Reader is a specialized utility designed to extract hidden tracking identifiers and page-specific serial numbers from PDF documents generated by usage tracking tools.

When to Use

•Verify the authenticity of distributed PDF documents by checking their embedded tracking IDs.
•Audit document usage by extracting page-level serial numbers to identify specific page leaks.
•Extract metadata-based tracking information from PDFs without needing to manually inspect file properties.

How It Works

•Upload your tracked PDF file to the tool.
•The tool scans the document metadata (subject and keywords) for the primary tracking ID.
•It parses the document content to detect hidden page-specific serial strings (e.g., TRACKID-P0001).
•The tool returns a structured JSON object containing the global tracking ID, individual page serials, and the detection source.

Use Cases

Auditing document distribution to ensure files are being tracked correctly.

Identifying the source of leaked documents by matching page-level serials.

Automating the verification of tracking IDs in large batches of generated reports.

Examples

1. Read Auto-generated Tracking ID

Background: A user has a PDF generated with a timestamp-hash tracking ID and needs to verify the metadata.
Problem: Manual inspection of PDF properties is inefficient for verifying the tracking ID and page serials.
How to Use: Upload the PDF file to the tool to automatically parse the metadata and page serials.
Outcome: The tool returns a JSON object confirming the tracking ID 'TRK-4A964CB788141089' and lists the serials for each page.

2. Read Custom Distribution ID

Background: A distribution manager needs to confirm that a custom ID 'DIST-2026-Q1-ALPHA' is correctly embedded in a report.
Problem: Need to ensure the custom ID is present in the metadata and that every page contains the correct serial suffix.
How to Use: Upload the distribution PDF to the tool to validate the embedded identifiers.
Outcome: The tool outputs a JSON confirming the global ID and verifying that all pages contain the expected serial suffix.

Try with Samples

pdf, file

PDF Samples

Generated PDF samples from tools dated 2026-02-01 to 2026-02-10

title token pdf

pdf

Markdown Slide Deck Samples

Remark/Marp style Markdown slide decks for testing PDF export layouts

preferred input family pdf

pdf

Tracking Number Samples

Collection of tracking numbers from major global carriers for validation testing

title token tracking

sample

Sentry Error Tracking Samples

Comprehensive Sentry error tracking and performance monitoring setup with SDK integrations for various platforms

title token tracking

sample

Related Hubs

Pdf Convert Tools

Explore 28 pdf tools for convert workflows and compare closely related utilities quickly.

Pdf Tools

Explore 12 pdf tools for utility workflows and compare closely related utilities quickly.

Pdf Generate Tools

Explore 10 pdf tools for generate workflows and compare closely related utilities quickly.

Json Convert Tools

Explore 100 json tools for convert workflows and compare closely related utilities quickly.

FAQ

What kind of PDFs can this tool read?

This tool is specifically designed to read PDFs generated by the 'pdf-usage-tracking-id' utility.

Where does the tool look for the tracking ID?

It first checks the PDF metadata (subject and keywords) and then scans the document text for hidden page serial patterns.

What is the output format?

The tool provides a structured JSON response containing the tracking ID, page serial list, and detection status.

Can it detect tracking IDs in standard, non-tracked PDFs?

No, it only extracts information from PDFs that have been specifically encoded with tracking metadata or page serials.

Is my file data stored?

No, files are processed in memory and are not stored or retained after the extraction process is complete.

API Documentation

Request Endpoint

POST /en/api/tools/pdf-usage-tracking-id-reader

Request Parameters

Parameter Name	Type	Required	Description
sourceFile	file (Upload required)	Yes	-

File type parameters need to be uploaded first via POST /upload/pdf-usage-tracking-id-reader to get filePath, then pass filePath to the corresponding file field.

Response Format

{
  "key": {...},
  "metadata": {
    "key": "value"
  },
  "error": "Error message (optional)",
  "message": "Notification message (optional)"
}

JSON Data: JSON Data

AI MCP Documentation

Add this tool to your MCP server configuration:

{
  "mcpServers": {
    "elysiatools-pdf-usage-tracking-id-reader": {
      "name": "pdf-usage-tracking-id-reader",
      "description": "Extract embedded tracking ID and page serial values from tracked PDF files",
      "baseUrl": "https://elysiatools.com/mcp/sse?toolId=pdf-usage-tracking-id-reader",
      "command": "",
      "args": [],
      "env": {},
      "isActive": true,
      "type": "sse"
    }
  }
}

You can chain multiple tools, e.g.: `https://elysiatools.com/mcp/sse?toolId=png-to-webp,jpg-to-webp,gif-to-webp`, max 20 tools.

Supports URL file links or Base64 encoding for file parameters.

If you encounter any issues, please contact us at [email protected]

Categories