Analysis / Growth experimentation and pricing
Plan a landing page conversion experiment
Define a landing page test with eligible visits, a primary conversion, event requirements and an appropriate analysis plan.
Growth leader · Revenue operations analyst
Bring this question into Chat
Your starting prompt.
Using our landing page visit and conversion records, plan a comparison of [proposed change] with the current page. Define eligible visitors, assignment persistence, the primary qualified-conversion event and guardrails. Estimate the sample under stated baseline and improvement assumptions. Identify missing tracking and specify acceptance checks before launch. Produce a test brief and analysis plan that keeps traffic-source changes and repeat visitors visible.
Copy this starting point, then replace the placeholders with your own inputs.
Method and review
Keep the assumptions visible.
State the hypothesis, baseline, unit economics and decision rule. Compare total contribution and uncertainty, and separate modeled scenarios from measured experimental results.
For this task, check
A signup rate and a qualified-lead rate can move differently; select the business outcome before inspecting the test results.
Before you begin
- Permitted uploaded records or queryable Data with the specified fields
- Agreed outcome definitions and an accountable business reviewer
Work with permitted files or queryable data. Verify the result against the original records.
Synthetic illustrative example
See the method in practice.
Synthetic input. Illustrative output checked locally; this is not a live Proforma run or customer result. Three historical weeks each have 400 eligible persistent visitors and 40 qualified conversions. A 14-day test and +2 percentage-point improvement are proposed assumptions.
These invented records explain the method. They are not a recorded Proforma run.
| Historical week | Eligible visitors | Qualified conversions |
|---|---|---|
| Week 1 | 400 | 40 |
| Week 2 | 400 | 40 |
| Week 3 | 400 | 40 |
| Planning arm | Expected visitors | Rate basis | Expected conversions |
|---|---|---|---|
| Control | 400 | 10.0% | 40 |
| Proposed page | 400 | 12.0% assumed | 48 |
| Hypothetical difference | Equal exposure | +2 percentage points assumed | 8 |
Method
Historical conversion = 120 / 1,200 = 10%. Two weeks at unchanged arrival volume suggest 800 visitors total, or 400 per arm. Expected conversions multiply planned exposure by assumed rates. Require persistent assignment, a qualified-lead event and tracking acceptance checks before launch.
What the result tells you
The expected +8 conversions is a scenario, not a result or proof of adequate power. A sample-size assessment, traffic-source checks and approved launch are still required; no page is changed.
Take the next step
Make it your investigation.
Copy the prompt above, create or open your Workspace, and paste it into Chat. Add the inputs you have permission to use and adapt the assumptions with your agent.
Start exploringYour prompt is carried by copy and paste. Signing up does not submit it or start this work automatically.
Or start with your own agent
The setup prompt includes this public task. Your agent will help you connect when needed and use the access you approve.