Prompt
How do I set up a traffic and order management system for insertion orders, creative approvals, and campaign status tracking?
Latest observation
To set up a traffic and order management system for insertion orders, creative approvals, and campaign status tracking, build it around one source of truth, a defined workflow, and clear ownership at each stage.
1) Define the core workflow
Map the lifecycle from start to finish:
-
Order intake
- Receive insertion order or campaign request
- Capture client, brand, dates, budget, targeting, placements, rates, and contacts
-
Validation / trafficking
- Check inventory, pricing, specs, and feasibility
- Assign campaign or order ID
- Confirm pacing and delivery requirements
-
Creative submission
- Request assets and specifications from client or agency
- Track creative version, format, size, deadlines, and approval status
-
Creative review and approval
- Review against policy, specs, and brand requirements
- Approve, reject, or request revisions
- Log comments and timestamps
-
Launch / activation
- Push approved creatives and campaign details into ad servers or delivery platforms
- Record go-live date and trafficking confirmation
-
Ongoing status tracking
- Monitor delivery, pacing, pauses, QA issues, and changes
- Track billing status, makegoods, and end dates
-
Closeout
- Confirm delivery, final creative status, and billing completion
- Archive order and supporting documents
2) Create a central system of record
Use a CRM, project management tool, or custom database to store all campaign/order data. It should include:
- Order ID / IO number
- Client / agency
- Campaign name
- Flight dates
- Budget and rate card info
- Placement / product details
- Creative IDs and file links
- Approval status
- Campaign status
- Owner / account manager / trafficker / approver
- Notes, comments, and audit trail
Good options:
- No-code: Airtable, Smartsheet, Monday.com
- Project tracking: Asana, Jira, Trello
- Operational CRM: Salesforce, HubSpot
- Custom: SQL database + internal dashboard
3) Build status stages and ownership
Standardize the statuses so everyone uses the same language. Example:
Order status
- New
- In review
- Pending IO
- Confirmed
- Trafficking
- Live
- Completed
- Cancelled
Creative status
- Requested
- Received
- In review
- Revision requested
- Approved
- Rejected
- Loaded
- QA complete
Campaign status
- Scheduled
- Live
- On hold
- Under delivery issue
- Completed
- Closed
Assign an owner for each status transition:
- Sales / Account: intake and client communication
- Traffic / Ad Ops: validation, trafficking, QA, launch
- Creative ops / compliance: approval
- Finance: billing and reconciliation
- Manager: escalation and exceptions
4) Standardize intake forms
Use structured forms instead of email threads for new orders and creative requests.
Order intake form fields
- Client / agency
- Campaign name
- IO number
- Flight dates
- Budget
- KPI / objective
- Products / placements
- Targeting requirements
- Billing contact
- Campaign owner
- Special instructions
Creative intake form fields
- Creative type
- File format
- Dimensions
- Click-through URL
- Landing page
- Tracking tags
- Due date
- Approval contact
- Brand compliance requirements
This reduces back-and-forth and missing information.
5) Add approval and notification automation
Automate reminders and handoffs where possible.
Examples:
- Notify traffic when an IO is approved
- Alert creative team when assets are missing
- Send automatic reminders 48 hours before creative deadline
- Flag campaigns that are nearing launch without approval
- Trigger status changes when an approver signs off
You can do this in tools like:
- Airtable Automations
- Monday automations
- Zapier / Make
- Salesforce workflows
- Slack/email integrations
6) Track documents and version control
Creative and IOs often fail because multiple versions exist.
Best practices:
- Store files in a shared repository with links in the record
- Use naming conventions like:
Client_Campaign_CreativeSize_Version_Date
- Keep version history and approval timestamps
- Never overwrite old assets
- Record who approved which version
7) Build a dashboard for status tracking
Create a dashboard for quick visibility into:
- Orders pending approval
- Creative missing or overdue
- Campaigns launching in next 7 days
- Live campaigns with pacing issues
- Campaigns at risk of underdelivery
- IOs pending signature
- Closed campaigns awaiting billing
Include filters by:
- Client
- Campaign owner
- Status
- Date range
- Priority
- Platform/product
8) Define SLAs and escalation paths
Set clear service levels:
- Creative review within 1 business day
- IO confirmation within 24 hours
- Launch QA completed within 2 hours of trafficking
- Escalate if assets missing within 48 hours of launch
Create escalation rules:
- First alert to assigned owner
- Second alert to manager after threshold
- Final escalation to leadership or client contact
9) Integrate with ad servers and billing systems
If possible, connect your system to:
- Ad server
- Order management / billing platform
- CRM
- Creative review tool
- Reporting/analytics tool
That lets you:
- Reduce duplicate data entry
- Sync live status and delivery metrics
- Improve invoice reconciliation
- Support automated closeout
10) Start simple, then scale
If you’re just starting:
- Use Airtable or Monday.com as the master tracker
- Build intake forms
- Create standardized statuses
- Set notifications and reminders
- Add a dashboard
- Integrate with other tools later
Recommended minimum fields
For every order/campaign, track:
- Order ID
- Client name
- Campaign name
- Start/end dates
- Budget
- Owner
- Creative status
- Campaign status
- Approval status
- Launch date
- Notes / blockers
- Last updated date
If you want, I can also give you:
- a sample workflow diagram,
- a database/table schema, or
- a ready-to-use Airtable/Monday setup for this system.
Observation history
Unlock observation history
Create a free Obsurfable account to unlock historical responses, model comparisons, and deeper brand intelligence.
How did Obsurfable measure this prompt?
Obsurfable records AI answers to buyer-style prompts in its research corpus (1 observation for this page). Metrics are distributions over observations, not a single static ranking.
Which AI systems does Obsurfable collect answers from?
OpenAI, ChatGPT, Google, Gemini, Google AI Mode, Anthropic, Claude, Perplexity, Grok, DeepSeek, Mistral, Copilot, and Meta AI.