01
Step 1
Collect the campaign's offer terms, eligible items, start and end dates with timezone, the approved campaign message and assets, the tracking setup the page must carry, and the merchant's chosen end-of-campaign page state.
Back to topic
Spark playbook scenarios · Spark: AI Store Assistant
Create a landing-page draft for a campaign
The campaign has a message and assets but no destination page, so ads point at the generic collection. In this case, the immediate task is to create a landing-page draft for a campaign. The workflow should produce page structure and copy that place eligibility and dates beside the offer, plus a launch checklist and an end-of-campaign page state.
Topic
Promotional Landing Pages
Target keyword
shopify campaign landing page
Copyable AI prompt
A prompt you can drop directly into Spark
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.
ai-prompt.txt
Act as a Shopify operations specialist.
Help me create a landing-page draft for a campaign.
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: [campaign offer terms, eligible items, start and end dates with timezone, approved campaign message and assets, the required tracking setup, and the chosen end-of-campaign page state].
Draft the page structure and copy so the eligibility conditions and dates appear beside the offer headline and repeat near any code or form entry, and define the post-campaign state, whether the page is unpublished, redirected or repurposed.
Return the page draft and launch checklist, then verify both 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.How to solve
A recommended resolution workflow
Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
02
Step 2
Draft the page structure and copy so the eligibility conditions and dates appear beside the offer headline and repeat near any code or form entry, and define the post-campaign state, whether the page is unpublished, redirected or repurposed.
03
Step 3
Deliver the page draft with a launch checklist covering dates, eligible items, tracking and the end state, verify every stated term against the supplied records, and confirm the draft's URL does not replace an existing collection page unless the merchant approved that change.
FAQ
Common questions when running this scenario
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
How is the post-campaign page state set up?
The end state, whether unpublished, redirected or repurposed, is defined inside the draft before launch. A dated page left live advertises terms that have expired. The state change is scheduled with the campaign end and confirmed on the launch checklist.
What tracking must the draft carry before launch?
The tracking setup the campaign records require, placed on the draft and tested before publish. Retrofitting tracking after launch loses the campaign's attribution window. The checklist blocks publication until the tracking is confirmed firing.
How are eligibility conditions repeated without cluttering the page?
They sit beside the offer headline and repeat in short form near any code or form entry, not in a link-only footnote. Distance between the offer and its conditions invites misread orders. The shortest mobile layout keeps at least the headline-adjacent mention.
Related scenarios
Continue with adjacent or same-topic scenarios
Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.
Next step
Want these AI scenarios embedded directly into daily operations?
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.