Build 03 / AI-Assisted Campaign Delivery
Campaign Copilot
An AI-assisted campaign delivery system for enterprise marketing operations. It turns fragmented requests into governed intake, asset naming, creative handoff, tracking links, Workfront prompts, GitHub template assembly, and Eloqua build assets.
Greg's take
I decided to attack myself.
Not the client. Not the tools. I looked at the delivery chain and admitted the weak link was the way marketing work entered the system: loose briefs, inconsistent naming, guessed tracking, and build teams forced to infer intent.
A rushed intake becomes an unclear brief. An unclear brief becomes a bad asset name. A bad asset name becomes a broken report. Then the developer gets blamed for a system that was already unstable.
So I attacked the system from inside. Every failure point becomes a question, a dropdown, a required decision, a generated name, a tracking link, a DAM placeholder, a build prompt, a QA gate, or an evidence trail.
The idea is simple: remove the places where campaign delivery fails before the campaign reaches production, and protect the people who have been carrying the failure manually.
Build milestones
Product maturity checkpoints.
Campaign Intake Structure
The intake flow turns fragmented campaign requests into structured decisions.
Asset Naming Logic
Naming rules now generate consistent downstream asset instructions.
Playwright QA Path
The active path is browser-level verification of campaign build flows.
In-Flight Change Control
The next layer controls revisions when campaign details move mid-build.
Client-Specific Delivery Profiles
Future profiles will adapt intake, naming, and handoff rules per client.
The problem
Some campaign delivery environments are fragmented by design.
Requests arrive in pieces
Landing page needs, form type, copy, image direction, email selection, tracking, deadlines, and stakeholder notes arrive across calls, documents, chats, and agency briefs.
Naming conventions are fragile
Asset names depend on humans remembering the right structure. One missed market, campaign code, date, offer type, or channel value creates downstream confusion.
Creative and MA handoff split apart
The design agency needs clear image instructions and upload locations. The MA developer needs build instructions, template choices, tracking links, and final asset names.
Tracking is too manual
Links need Clarevine tracking appended consistently across email and landing page journeys. Manual append work creates avoidable mistakes close to launch.
What it does
A guided campaign intake and build automation layer.
Campaign Copilot forces the campaign request into a governed path. The marketer answers structured questions. The system generates compliant asset names, campaign instructions, agency briefs, DAM placeholders, tracking links, and MA build packets. The developer still approves the build, but no longer starts from a messy brief.
Guided dropdown intake
Client-specific dropdowns capture region, business unit, campaign type, product family, audience, language, channel, offer, form type, landing page layout, and email selection.
Asset naming convention engine
The selected values create approved names for landing pages, forms, emails, image folders, Workfront requests, DAM destinations, and Eloqua assets.
Form and landing page selection
The user chooses Demo, Sample, or Gated form, then selects the landing page template and supplies URL, title, description, body copy, and image instructions.
Email packet creation
The user selects required emails, adds copy and image direction, and the system prepares each email with the correct module choices, links, naming, and tracking requirements.
Agency and DAM handoff
On submit, the system sends a design request to the agency and creates placeholder DAM upload links so creative files land in the correct destination.
Clarevine, GitHub, Eloqua, Workfront
The system generates Clarevine tracking links, prepares a Workfront build prompt, pulls from GitHub templates and modules, and creates Eloqua assets with placeholder DAM links.
System view
From messy request to Eloqua build package.
Campaign Copilot sits between the client request, creative agency, DAM, Clarevine, Workfront, GitHub templates, and Eloqua. It controls the order of operations and turns every selection into a downstream build artifact.
01 Intake
Dropdown decisions
Structured questions replace open-ended briefing chaos.
02 Name
Asset names
All names are created under the agreed convention.
03 Creative
Agency brief
Image instructions and DAM upload locations are sent out.
04 Track
Clarevine links
Tracking links are generated and appended to email links.
05 Build
MA queue
Workfront prompt enters the developer queue for approval.
06 Create
Eloqua assets
Templates assemble assets with placeholders and tracked links.
Design workflow
The design agency gets a complete creative request, not a vague brief.
Campaign Copilot captures the same instructions the marketer would normally send to the design agency, but forces them into a usable format before the request leaves the system.
Landing page design brief
The client chooses the landing page layout from approved templates, enters the destination URL, title, meta description, page copy, CTA, and the image direction required for the selected layout.
Email design brief
The client selects which emails are needed, enters copy and link destinations, then provides image instructions for each email module instead of sending loose notes later.
Image instruction capture
Hero image, body image, thumbnail, banner, product visual, and social crop instructions are captured against the exact asset and module they belong to.
DAM upload destinations
The system generates placeholder DAM locations and gives the agency a clean upload map: which graphic goes where, under what name, and which Eloqua asset will consume it.
Agency request package
On submit, the design agency receives one structured request containing asset names, template choices, image requirements, copy context, deadlines, and DAM upload links.
Build-safe placeholders
The MA build can start before final graphics are uploaded because the Eloqua assets are created with the correct placeholder DAM links already wired into the templates.
How it works
The guided request becomes the build instruction.
Answer structured campaign questions
The client chooses controlled dropdown values instead of writing a vague brief. Required fields force decisions before the request can be submitted.
Generate all asset names
Campaign Copilot uses the agreed naming convention to generate names for landing pages, forms, emails, Workfront requests, DAM locations, and Eloqua assets.
Choose form type and page layout
The user selects Demo, Sample, or Gated form, chooses the landing page template, then supplies URL, title, description, body content, and image instructions.
Prepare email and creative instructions
The user chooses the email assets, enters copy, target links, and image direction for each email module. The system creates the agency request package and the DAM upload placeholders.
Generate Clarevine tracking
The Clarevine API generates the correct tracking links and Campaign Copilot appends them to the relevant links inside the selected emails.
Send the MA developer a build prompt
A structured Workfront prompt enters the MA developer queue. The developer reviews the request and clicks submit when ready to generate the build.
Create assets from GitHub templates
The approved prompt selects the correct templates and modules from GitHub, creates the assets with placeholder DAM links and Clarevine tracking links, then creates them in Eloqua automatically.
Integration model
Campaign Copilot does not replace the stack. It controls it.
The value is not another disconnected AI tool. The value is a control layer that knows how the client already delivers campaigns and turns that messy process into a repeatable workflow.
Workfront
Developer queue and approval
The generated build prompt becomes the structured MA request. The developer approves before assets are created.
DAM
Placeholder upload links
The design agency receives the creative request with the exact upload destinations for landing page and email graphics.
Clarevine
Tracking link generation
The API creates the required tracking links and the system appends them consistently across the selected email assets.
Eloqua
Automatic asset creation
Approved builds create the landing page, form, and email assets using existing modules and templates.
Evidence / Governance
The system removes the places where campaign delivery fails.
This is not AI content generation dressed up as automation. It is campaign operations surgery. Every repeatable decision becomes structured. Every naming rule becomes generated. Every handoff becomes a packet. Every link becomes tracked. Every template selection becomes controlled.
Less interpretation
The MA developer receives a complete build prompt instead of a pile of partial notes.
Cleaner creative handoff
The agency gets the image brief and the correct DAM upload destinations at the same time.
Fewer tracking mistakes
Clarevine tracking is generated and applied before the email build reaches QA.
More controlled automation
The build can be automated from templates, but approval stays with the MA developer before Eloqua assets are created.
Next evolution
Capabilities shown by this build.
Campaign operations
- Client-specific intake design for fragmented delivery environments
- Asset naming convention automation
- Landing page, form, email, and creative handoff orchestration
Integration thinking
- Workfront queue prompts for MA developer approval
- DAM placeholder link generation for agency uploads
- Clarevine tracking link generation and application
Eloqua build automation
- GitHub template and module assembly
- Automatic creation of landing pages, forms, and emails in Eloqua
- Placeholder creative links and final tracked URLs inserted at build time
Control model
- AI-assisted, not blind autonomous delivery
- Developer approval before build execution
- Evidence trail from request to asset creation
Want to remove the weak points from campaign delivery?
Campaign Copilot is designed for enterprise marketing teams that need cleaner intake, naming discipline, creative handoff, tracking control, and Eloqua build automation without surrendering human approval.