Campaign ID
Unique identifier used across systems (ad server, billing, reporting). Include any agency or brand reference codes to avoid reconciliation errors.
A well‑prepared Display IO reduces disputes, aligns expectations across media, creative, and finance teams, and documents deliverables used for billing and performance measurement. When signed electronically under federal and state e‑signature laws, it creates an auditable agreement suitable for enforcement and recordkeeping under ESIGN (15 U.S.C. §7001) and state UETA frameworks.
Multiple groups collaborate on an IO: commercial, operations, legal, and creative teams coordinate inputs before final approval.
Final signers are usually authorized contract approvers from the advertiser and the publisher; the executed IO becomes the operative document for campaign delivery.
Unique identifier used across systems (ad server, billing, reporting). Include any agency or brand reference codes to avoid reconciliation errors.
Start and end dates with timezone. Include soft/blackout windows and any early-launch / extension rules for schedule changes.
Total budget, daily caps, pacing method (even/accelerated), and spend thresholds that trigger pause or review.
Detailed targeting parameters (geo, device, audience segments), excluded inventory, and allowed placements or site lists.
Exact ad sizes, file types, clickthrough URL rules, tracking pixel requirements, and naming conventions for assets.
Define primary metrics (impressions, CTR, viewability, conversions), reporting cadence, and attribution conventions for reconciliation.
| Field | Configuration |
|---|---|
| Signer Authentication | Email link | Optional SMS code or KBA |
| Template Mapping | Map campaign ID to ad server | Auto-populate fields |
| Attachments | Attach creatives, SOW, and proof of performance | PDF preferred |
| Retention | Store executed IO and audit trail | Exportable PDF/A |
An IO workflow often connects to CRM, billing, and ad platforms to reduce manual steps and preserve audit trails.
Use integrations to automate invoice creation, attach executed IOs to accounting records, and ensure signed copies are archived with campaign metadata.
Typically 5–10 business days before start date for QA and approval.
Confirm insertion order at least 48–72 hours before live date.
Standard terms often Net 30 from invoice date; specify in IO.
Final reconciliation and reporting usually provided within 30 days post flight.
Specify required notice (commonly 3–10 business days) for termination or pause.
| Document Type | Primary Use | |
|---|---|---|
| Insertion Order (IO) | campaign execution | delivery and billing terms |
| Statement of Work (SOW) | project deliverables | scope and milestones |
| Master Services Agreement (MSA) | governance | legal terms and liability |
| Creative Brief | asset specs | messaging and creative direction |
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial (no credit card) | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes (Business Premium) | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| Envelope Cap | No envelope cap | 100 envelopes/user/year | Varies | Varies | Varies |
Export executed IO as a signed PDF (PDF/A recommended) to preserve appearance and audit metadata for long‑term retention.
Keep the original editable file (DOCX) for internal version control and future amendments without losing context.
Include final creative assets with filenames and checksums or hosted URLs so ad ops can validate deployed creatives.
Attach SOWs, rate cards, PO, and any privacy addenda as part of the executed package for full contractual context.
The interface is simple and easy-to-use for our team; more importantly, it is just as easy for our customers.
I can process and execute all of these documents online with 100% compliance and built-in security.