Step 1
Collect ad-level results per period, the campaign objective with the metric that represents it, the spend limits in force, the stated conversion delay, and each ad's launch date and change history so the learning period stays visible.
Ads are switched off on impression, with no written rule separating genuine weakness from a learning period or a delayed conversion. In this case, the immediate task is to define when underperforming ads should be paused. The workflow should return an optimization plan with budget guardrails and each proposed pause tied to a fixed evidence window.
First replace every [bracketed] placeholder with real store scope and constraints, then add any actual records or data you have, and paste it into your preferred AI assistant or Spark agent. Spark will follow this page's workflow to produce structured output and verification steps.
Act as a Shopify operations specialist.
Help me define when underperforming ads should be paused.
My store context is [describe the business, products and target audience].
My scope is [specify the affected products, pages, customers or reporting period]. Use these inputs: [ad-level results per period, the campaign objective with its representative metric, the spend limits in force, the stated conversion delay, and each ad's launch date and change history]. Judge each ad inside a fixed evidence window measured from its last structural change, requiring both the minimum spend or click volume the merchant states and no conversion still sitting inside the delay, and proposing a pause only where the ad misses the objective metric across the whole window.
Return the optimization plan with budget guardrails and each proposed pause verified against the supplied records for the specified task.
Show the relevant evidence or before-and-after examples and explain how I can verify the result.
If essential data is missing, ask for it and mark unsupported conclusions as unknown.
Do not invent metrics, product claims or customer facts.
For any publication, message, account or store change, use only connected tools within my explicitly authorized scope and report success only after verification; otherwise provide the draft or proposed steps.Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
Collect ad-level results per period, the campaign objective with the metric that represents it, the spend limits in force, the stated conversion delay, and each ad's launch date and change history so the learning period stays visible.
Judge each ad inside a fixed evidence window measured from its last structural change, requiring both the minimum spend or click volume the merchant states and no conversion still sitting inside the delay, and proposing a pause only where the ad misses the objective metric across the whole window.
Deliver the optimization plan with the budget guardrails that cap spend while a decision is pending, listing each proposed pause with its window, figures and reason, then verify every entry against the ad-level export and report which ads remain inside their learning period.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
From the ad's last structural change, since a creative or audience edit resets what the ad is and earlier results no longer describe it; measuring from launch instead usually mixes two different ads into one verdict.
The window and the minimum volume requirement run first, and an ad inside its learning period is reported as pending rather than paused, because early delivery has not yet settled into a stable result.
A spend cap holding the ad at a reduced level keeps evidence accumulating while limiting exposure, which is safer than full delivery and less destructive than a pause that removes the ad from the record entirely.
Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.
Ciwi Spark builds Shopify-native AI tools and agents around the workflows merchants actually run: research, ads, translation, and customer support. Stop rewriting the same prompts by hand.