Campaign creation
Turn a campaign brief into a Shopify landing page
Carry the audience, promise, offer, proof and visual direction from your campaign into the page shoppers see after clicking.
Install Lexsis MCP and skills in your AI client
Run the installer, then follow the authentication prompts to connect Lexsis MCP and add the workflow skills to your supported AI client.
curl -fsSL https://mcp.trylexsis.com/install.sh -o /tmp/lexsis-install.sh && sh /tmp/lexsis-install.shWhat this workflow does
This workflow turns a campaign brief into a complete, responsive Shopify landing page.
The agent first plans the shopper journey and writes the final copy. It then resolves the required production assets, builds the page through Lexsis, and returns an unpublished hosted preview for review.
Planning, asset production, page creation and publication remain separate approval stages.
What you need
- Product or collection
- Target audience
- Traffic source
- Campaign promise or angle
- Offer and dates
- Primary conversion goal
- Campaign creative or visual references
- Any mandatory proof, claims or sections
Starting prompt
Replace the bracketed details, then give the complete prompt to your connected AI agent.
Use Lexsis to create a Shopify landing page from this campaign brief.
Product or collection: [PRODUCT]
Audience: [AUDIENCE]
Traffic source: [META ADS, GOOGLE ADS, EMAIL, CREATOR, ETC.]
Campaign message: [MESSAGE]
Offer: [OFFER AND TERMS]
Primary goal: [PURCHASE, ADD TO CART, LEAD, QUIZ, ETC.]
Creative or references: [ATTACH OR LINK]
First verify the connected store, theme and live product information. Then create the complete page strategy, section order, final copy, proof decisions, offer treatment, responsive layout and asset requirements.
Show me the plan before producing assets or creating a page. After I approve the plan and assets, create one unpublished Lexsis draft and review it at mobile, tablet and desktop widths.
Do not publish the page.How the workflow works
Follow the sequence in order. Approval and verification remain separate from page creation and live publication.
- 01
Confirm the store context
The agent reads the existing Lexsis setup and confirms the selected workspace, store and theme.
If setup is missing or belongs to another store, the agent stops and asks you to run the setup workflow.
- 02
Understand the campaign
The agent extracts the campaign’s:
- Promise
- Audience
- Product
- Offer
- CTA
- Claims
- Tone
- Visual cues
- Traffic source
- 03
Refresh product and proof information
Lexsis refreshes the selected products, variants, options, prices, availability, selling plans, media and relevant reviews.
This prevents the landing page from relying only on an old setup snapshot.
- 04
Choose the page structure
The agent chooses one page type based on the audience, awareness level, campaign source, product count, offer and desired action.
Sections are ordered around the shopper’s actual decision questions.
- 05
Write the complete page
The plan includes final:
- Headlines
- Supporting copy
- Benefit language
- Labels and bullets
- CTA text and destination
- Offer terms
- FAQs
- Proof placement
- Mobile and desktop layout intent
There should be no placeholders or “write something here” instructions.
- 06
Approve the plan
You review the page strategy, copy, proof, offer and section order before the agent spends credits or creates a draft.
- 07
Resolve production assets
The agent searches Shopify media and the Lexsis asset library first.
For every asset, it checks mobile crop, desktop crop, focal point, resolution, visual consistency, rights and whether text is baked into the image.
Generation or editing is used only when permitted and explicitly approved.
- 08
Build an unpublished page
The agent resolves the required design components, authors the page source, and compiles it through Lexsis.
A successful compile is required before creating the draft.
- 09
Review the hosted page
The hosted draft is reviewed at:
- 390px mobile
- 768px tablet
- 1280px desktop
The agent verifies layout, copy, assets, variants, quantity controls, cart behaviour, navigation, accessibility and overflow.
How Lexsis MCP is used
Each operation stays tied to the selected workspace, store, page and version for this workflow.
- Product and review retrieval
- Theme and design context
- Page-kit and section-template search
- Asset search and inspection
- Asset import or approved generation
- Design component schemas
- Page compilation
- Unpublished draft creation
- Version-safe corrections
- Hosted QA recording
Approval points
- Page plan and final copy
- Paid generation or editing
- Final asset selection
- Hosted design
- Publication as a separate workflow
What you receive
The result includes the working artifacts and verification evidence needed for the next decision.
- Approved page strategy
- Final customer-facing copy
- Ordered page sections
- Proof and claim decisions
- Responsive layout direction
- Verified asset bindings
- Unpublished Lexsis page
- Hosted preview URL
- Mobile, tablet and desktop QA
- Page ID and version