Turn an approved plan into a paused campaign, check for existing work, and verify what was created before any launch.
What this does
This is stage two of the campaign workflow. After the client has approved the proposal, it asks your AI assistant to resolve remaining settings, check for an existing or partial build, and create only the approved campaign in a paused state.
Unlike the research prompt, this prompt authorises account changes within the approved build scope once you have answered the outstanding questions. It does not authorise changes to existing campaigns or shared assets, or the launch of the new campaign.
When to use this
The client has approved the campaign plan and you are ready to create it.
You have the final approved version, not an earlier proposal with unresolved client decisions.
You want a paused build that can be reviewed separately before launch.
Before you start
Have the following ready:
The exact target Adpulse account name and account ID.
The complete approved plan, including ads, keywords, negatives, final URLs, budget and any agreed assets. Paste the approved content rather than referring only to a previous conversation.
Answers or an owner for outstanding location, language, device, bidding, network, conversion-goal, schedule and URL-tracking decisions.
An authorised Adpulse connection with the tools and permissions needed for the approved build.
Details of any previous build attempt, including names or identifiers, so the assistant can check for partial work.
Support varies by platform, connection and action. The assistant must flag settings or assets it cannot create or verify, rather than replace them with a different setting or describe them as complete.
Confirm that the approved scope is sufficient to build without changing an existing campaign or shared asset. Those changes need separate approval.
How to use this
Enable the Adpulse connection in your conversation. If needed, follow the MCP connection setup guide.
Copy the entire prompt below, paste the final approved plan, and replace [account] with the exact account name and ID.
Answer the assistant’s questions about unresolved settings. Resolve any conflict with the approved plan before allowing the build to continue.
Require a check for existing or partially built versions before creating anything. If there was a previous attempt, provide its details.
Review the read-back report. Check that the campaign is paused, all required settings are verified, and missing or unsupported items are clearly listed.
Keep the campaign paused while you review it. Launching it is a separate decision and is not part of this prompt.
Copy and paste this prompt
The client has approved this plan: [paste approved plan]. Before building in [account], confirm any unresolved settings: target and excluded locations, presence vs interest, languages, device exclusions and supported bid adjustments, bid strategy and targets, daily budget, ad schedule and timezone, network settings, conversion goals and actions used for bidding, and URL tracking. Flag any conflicts with the approved plan. Wait for my answers.
Check whether an existing or partially built version of the approved campaign is already present before creating anything. Use the Adpulse MCP to build the approved campaign in a paused state, following the account’s campaign and ad group naming conventions. Do not change existing campaigns or shared assets without separate approval. Flag unsupported settings rather than silently substituting them.
Once built, read back and verify the campaign and confirm it is paused. List everything created and the final settings, clearly distinguishing what was created, what was verified and what still needs attention. If any step fails or cannot be verified, keep the campaign paused, explain what is complete and what remains, and check existing results before retrying to avoid duplicates.
What you will get
A build report that separates:
What was created, including campaign and ad group names and identifiers where available.
The final settings and items independently read back and verified.
Confirmation of the campaign’s paused status, or an explicit warning if that status could not be verified.
Unsupported settings, failed steps, partial work and anything requiring attention.
What to check before retrying or deciding whether the campaign is ready for a separate launch approval.
A successful creation response is not the same as a verified build. The report should not call the campaign complete while required items or its paused status remain unverified.
Limits and safety
This prompt creates account objects. Use it only after the client has approved the plan and you are authorised to build in the selected account.
Do not launch the campaign or enable it briefly to test it. Keep review and launch as separate steps.
Do not change existing campaigns or shared assets without separate approval. Reusing an asset is not permission to edit it everywhere it is used.
A paused campaign can still be incomplete, under policy review or incorrectly configured. Paused status does not prove the rest of the build is correct.
If a step fails, inspect existing results before retrying. Do not blindly repeat creation requests and risk duplicates.
If an item or paused status cannot be verified, stop and make the gap explicit. Do not substitute unsupported settings or claim that an unverified campaign is safe to launch.