The ads promise one thing while the destination page leaves visitors to work the offer out for themselves. In this case, the immediate task is to build a landing page around a specific campaign intent. The workflow should produce a landing-page draft and improvement hypotheses grounded in that campaign's own brief.
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 build a landing page around a specific campaign intent.
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: [the campaign intent, the single visitor action the page exists for, the approved offer with terms and expiry, the audience and traffic source, the usable proof assets, and the claims already verified in the merchant's records]. Order the sections so the headline restates the campaign promise, proof follows the promise, the primary action appears where the visitor has enough to decide and repeats after the proof, and cut any section, link or offer that gives the visitor a competing path away from that action.
Return a landing-page draft and improvement hypotheses tested against the campaign 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.
Take the campaign intent, the single visitor action the page exists for, the approved offer with its terms and expiry, the audience and traffic source, and the proof assets the merchant can use, noting which claims are already verified in the merchant's records.
Order the sections so the headline restates the campaign promise, proof follows the promise, the primary action appears where the visitor has enough to decide and repeats after the proof, and cut any section, link or offer that gives the visitor a competing path away from that action.
Deliver the page draft with its section order, copy, primary and secondary actions, and the improvement hypotheses each tied to a stated weakness, then check the draft against the campaign brief for promise, offer terms, audience and destination consistency and list any claim still lacking a source.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
Only where the campaign intent allows it: a page serving one offer works better with the exits the merchant has chosen to keep, while a page meant to introduce the brand can retain navigation; the rule is that every exit must be a deliberate choice, not a default.
Once above the fold for visitors who already decided, and again after the proof section for those who need it, always with the same wording as the campaign; placing it only at the end forces a decided visitor to scroll past content they did not need.
One primary offer, because two offers make the visitor compare instead of act; supporting points may explain the offer's terms or prove it, but any second promotion belongs on its own page or in a later message.
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.