Sales & E-commerce LLM Prompts Easy Automation Ready

Pixel Purchase Event Setup

Set up the “Purchase” event with dynamic value parameters in your pixel to record transaction amounts precisely.

Best Model
ChatGPT GPT-5.5 Thinking / Claude Sonnet 4.6CRO diagnosis
Brevity Mode
Standard
Difficulty
Easy
Automation
Yes

Use This When

Landing pages, product pages, CRO audits, funnel fixes, FAQs.

Inputs Needed

Website/store URL, product/service, audience, funnel stage, analytics, conversion goal, current blocker.

Expected Output

Conversion diagnosis, prioritized fixes, copy/UX recommendations, test plan, KPI impact.

The Workflow Prompt

Copy-paste ready. Replace [bracketed placeholders] with your specifics.
You are a CRO strategist and eCommerce revenue operator.

Objective:
Pixel Purchase Event Setup

Context:
Set up the “Purchase” event with dynamic value parameters in your pixel to record transaction amounts precisely.

Original task:
I want to track purchases and their values on my e-commerce site. Could you explain how to set up the “Purchase” event with dynamic value parameters to accurately record transaction amounts?

Inputs I may provide:
Website/store URL, product/service, audience, funnel stage, analytics, conversion goal, current blocker.

Operating instructions:
- First, restate the objective in one clear sentence.
- If critical information is missing, ask up to 5 focused questions. If there is enough information to proceed, make practical assumptions and label them.
- Use a Standard response style.
- Be specific to the business, audience, channel, and constraints provided.
- Avoid generic AI advice. Give concrete recommendations, examples, templates, copy, or steps I can use.
- When current facts, competitors, laws, prices, policies, or market claims matter, use current research and cite sources.
- Do not expose hidden chain-of-thought. Provide a concise rationale or decision summary instead.
- End with a short QA checklist that helps me verify the output.

Required output:
Conversion diagnosis, prioritized fixes, copy/UX recommendations, test plan, KPI impact.

Caution:
Avoid generic output; require concrete examples, assumptions, and next steps.

QA Follow-Up Checklist

After the AI returns its output, verify against:

  1. Output is specific to the provided business/context.
  2. Assumptions are clearly labeled.
  3. No unsupported claims without source checks.
  4. Next actions are clear and usable.

Follow-Up Prompt

Run this next to refine the first output into a client-ready version.
Now turn the result for 'Pixel Purchase Event Setup' into a client-ready version: tighten wording, remove fluff, add missing assumptions, and provide the next 3 actions.

Avoid / Cautions

Avoid generic output; require concrete examples, assumptions, and next steps.

Related Workflows

Copied to clipboard