Trakkr Docs

PDF Exports

Generating a client report used to live on this page. A modal asked which brand, which time range, which sections, then queued the PDF. Most of that work moved to the Agent, which can take a sentence ("generate a weekly recap for Hoka") and assemble the report, pick the right white-label branding, and surface a chip when it's ready.

What's left here is what you actually need across a portfolio: the archive. Every PDF that's been generated for every brand on your team, with status, dates, file sizes, send status, and the controls to download, retry, or copy a link.

Two pages, two jobs. The Agent makes them; this page tracks them.

The lifecycle of a report

The status column is what you actually read. A row moves through:

StatusWhat it means
QueuedSubmitted, hasn't started yet
GeneratingThe PDF service is building the file. The page auto-polls every 10 seconds while any row is in flight.
ReadyComplete and downloadable
FailedSomething went wrong — hover Retry to see the error message
ExpiredGenerated files live 30 days, then get cleaned up. The row stays. Retry to regenerate from the same configuration.

Generation usually completes in well under a minute. Leave the tab open and watch in-flight rows resolve.

Each row gets one button on the right depending on its state. Ready → Download. Failed or Expired → Retry (which kicks off a fresh generation with the original configuration). Generating → a spinner.

The list isn't editable beyond that. Nothing on the row lets you change which sections were included or who the report was sent to; those choices happened at generation time. If you need a different shape, generate a new one.

Making a new report

The "Ask Agent to generate" button in the page header opens the agent drawer with a prefilled prompt. From there, you describe what you want:

The Agent picks the brand, time range, sections, white-label branding, and any recipients, runs the generation through the same backend, and surfaces a chip when the file is ready. The new row appears in this list automatically.

White-label branding on PDFs

By default, generated reports inherit your team's white-label settings: agency logo, name, primary color, footer text, "Hide Powered by Trakkr" flag. Override per-report by telling the Agent ("use the Acme co-brand for this one"). If white-label isn't enabled on your team, reports render with Trakkr's default branding — the page works either way.

Plan access

PlanPDF Exports
FreeNo access
GrowthNo access
ScaleFull access
EnterpriseFull access, higher limits

Common questions

Why can't I create a new report from this page anymore?

Generation moved to the Agent so you can describe what you want in a sentence rather than fill out a form. The Agent submits to the same backend; the resulting row lands here regardless of where it was kicked off.

How long are the PDFs kept?

30 days. After that the file in storage is cleaned up automatically, but the metadata row stays. Hit Retry to regenerate from the same configuration.

A report keeps failing. What's wrong?

Most failures are transient — a model timed out, the PDF service was warming up — and Retry succeeds on the second pass. If a specific brand fails repeatedly, the brand's data may be incomplete: briefing-style sections need real data to render, so new brands with no reports yet, or no perception runs, can fail before they have enough to work with.

Does the client see this page?

No. PDF Exports is an agency surface; client portal users never see it. Clients receive reports by email (if the Agent was told to send one) or from their portal home, depending on how White-Label Portal is set up.

Can I batch-regenerate everything?

Not from the UI directly — Retry is per-row. If you need a bulk regeneration (e.g. after fixing a template bug), ask the Agent to "regenerate the latest weekly for every active brand" and it'll queue them in sequence.