Add Source Documents to a Campaign

Overview

Campaign source documents are files attached at the campaign level—not generic company context uploads—indexed for retrieval during strategy generation and plan/brief generation. Supported formats include PDF and DOCX. After upload, CntX extracts text, stores files in the company SSOT storage path, tracks hash and processing status, and syncs eligible content to the OpenAI vector store used for file search during generation.

This separation matters: workspace context captures products, audiences, and brand platform; campaign documents capture initiative-specific inputs—launch decks, messaging frameworks, research summaries, competitive battlecards, or creative briefs from clients. The generation contract treats document retrieval as part of provenance: briefs should reflect sourced claims where evidence coverage exists, and reviewers can trust angles tied to uploaded material rather than model improvisation alone.

Documents belong to the campaign container, so all targeted workspaces benefit from the same source bundle while child strategies still adapt channels and destinations locally. Removing or replacing documents after generation may invalidate strategy or plan freshness—regenerate when source material changes materially.

When to use

Add source documents when:

• You create a campaign grounded in client or leadership-approved copy not yet modeled in workspace context.
• Messaging includes specific claims, offers, or compliance language that must not drift during AI generation.
• Research PDFs or Word briefs already exist—uploading beats retyping into strategy fields.
• Generate strategy or Generate plan produced generic output and you suspect missing source retrieval.

Skip campaign documents only for lightweight internal campaigns where workspace context and key messages typed manually are sufficient.

Before you start

• Campaign shell created with targets defined—you attach documents from campaign detail, not from workspace context screens.
• Files are PDF or DOCX within platform size limits; scan for password-protected PDFs that block extraction.
• Stakeholders delivered final or near-final versions; versioning upstream reduces regenerate churn.
• You understand indexing latency: large files may show processing status before they are retrieval-ready.
• Company SSOT and vector sync paths are healthy in your environment—failures surface as document status errors on the campaign.

Steps

1. Open Campaigns → [campaign name] and go to the Documents step or Source documents panel on campaign detail.
2. Choose Upload document or drag files into the drop zone. Select one or more PDF/DOCX files from your machine.
3. Wait for upload to complete. Each file shows a row with name, format, upload time, and processing status (pending, indexed, failed).
4. If status stays failed, open error details when available—common causes include corrupt PDFs, empty documents, or unsupported encoding. Re-export from source and upload again.
5. Confirm indexed or ready state before running strategy or plan generation that should cite the document. Generation started too early may miss retrieval content.
6. Order documents mentally by priority: primary messaging deck first, supporting research second. Some UIs allow reorder or primary flags; when absent, filename clarity helps reviewers.
7. Optionally cross-check company-level Attach Source Documents to Your Context—those feed evergreen planning, not this campaign bundle. Do not duplicate the same file in both places unless you intentionally want dual indexing cost.
8. After strategy exists, upload additional documents only when messaging materially changed. Expect stale plan indicators if briefs already generated—plan regeneration recommended.
9. Proceed to Generate strategy if documents were added before strategy bootstrap, or Regenerate strategy/plan when documents arrive after an initial run.

Expected result

CampaignSourceDocument records linked to the campaign with successful extraction and vector indexing where applicable. Campaign detail lists documents with stable statuses reviewers can trust before approving generation spend.

The next strategy generation pass proposes objectives and key messages informed by document content. Plan generation retrieves passages during brief drafting, improving angle fidelity and enabling evidence display on briefs where the product exposes coverage keys. All targeted workspaces share the same document index for the campaign—no per-target re-upload required.

Tips / common issues

• Upload succeeds but generation ignores content — Document still processing. Wait for indexed status; rerun generation after completion.
• Password-protected PDF — Remove protection or export an open copy; extraction fails silently or with error status otherwise.
• Huge files — Split into logical chapters if limits hit; one deck plus appendix beats a single 200 MB scan.
• DOCX with heavy macros — Save as standard DOCX or export PDF for reliable text extraction.
• Stale briefs after new upload — Old briefs do not auto-refresh. Regenerate plan or edit individual briefs manually for critical fixes.
• Sensitive data — Campaign documents live in company storage and vector indexes. Redact before upload if files contain credentials or personal data not meant for AI retrieval.
• Duplicate uploads — Same hash may dedupe; avoid uploading ten identical copies expecting stronger retrieval.

Next step

Generate and Edit a Campaign Strategy to turn indexed documents and workspace context into a common and per-workspace strategy bundle.