Build a campaign from one editable HTML master, derive placement variations, edit any page in Designer, and export production HTML and PNG assets with a manifest.
Where: Flowgen → Add → Editors & Render → Ad Campaign, then open its card/sidebar or promote it to Designer.
Key ideas
- One HTML master, additive variations: The current Ad Campaign engine uses plain editable HTML as the master. Placement pages and copy variations are derived additively, so a revision can preserve existing valid pages instead of rebuilding the campaign through the retired canvas-specific Ad Creator engines.
- A five-stage campaign workflow: Work moves from source and direction through master composition, placement/variation generation, review, and delivery. Image Layers HTML can become a soft source for the master, and configured font sources travel with the campaign.
- Designer is the editing surface: The card can open the campaign in Designer, where master, placements, and variations are page-addressable. Agent tools can read or change a named campaign page rather than flattening every output into one screenshot.
Steps
- Add Ad Campaign and connect or upload the intended brand/product assets. Supply the campaign brief, required placements, copy constraints, and design-system or Brain context.
- Create the master HTML. Inspect real type, image crops, CTA hierarchy, and legal/brand content before deriving sizes.
- Generate placement pages and copy variations from the approved master. Keep semantic elements and stable IDs intact so fixes can propagate predictably.
- Open in Designer for visual edits. Select the exact master or placement page before changing it, and use the page-addressable ad tools for targeted revisions.
- Review representative placements at their real dimensions. Fix overflow, unsafe crop, unreadable copy, and direction drift without discarding correct campaign work.
- Export HTML and/or PNG. Use the generated manifest to match each file to its placement and variation, and retain referenced font/assets beside the export.
Inputs and editable surfaces
- Brief, copy constraints, placements, references, Brain records, and a design system can ground the build.
- The master is ordinary self-contained Designer HTML with stable data-dsn-id identities.
- Image Layers output can seed HTML where the source is a layered image reconstruction; it is not required for a normal campaign.
- Master, placement, and copy-variation pages stay separately addressable in Designer and the assistant.
Delivery
- HTML export preserves editable structure, styles, supported font sources, and referenced assets.
- PNG export renders each selected placement at its delivery size.
- The export manifest records placement/variation identity so files are not guessed from visual appearance.
- Publishing/sharing the Designer project and exporting campaign files are distinct actions.
What was retired
- The legacy Ad Creator orchestration and old competing ad engines are not the current path.
- Old saved ad nodes can be migrated into the HTML campaign shape; creating new work should use Ad Campaign.
- HTML Section and HTML Combine are not required to assemble a campaign master and are not substitutes for this node.
Tips
- Approve the master before producing dozens of variants. A structural mistake multiplied across placements is slower to repair than one master-page correction.
- Keep copy variants semantically equivalent when the legal or product claim must stay fixed.
Limitations and important notes
- Automatic resizing cannot guarantee that every subject crop, long translation, or legal line works at every placement; review each aspect family.
- Exported HTML must still obey the destination ad network’s packaging, script, size, and policy rules.
- A PNG export is flattened; use HTML/Designer when future editable changes are required.
Troubleshooting
A placement still shows older master content.
Confirm the variation is linked to the current master, regenerate or apply the targeted master update, then review the page again before export.
An exported HTML placement loses a font or image.
Check the manifest and asset URLs/font sources. Use stored or packaged assets rather than local-only or expired links.