Landing Page Optimization Agent
Tests page variants to lift conversion.
- Industry
- Oil & Gas
- Department
- Marketing
- Team
- Demand Generation
- Kind
- Decision-maker
- Approver
- Head of Fuels Marketing
- Code
- MKT-06
It tests variants of the fuel card application, loyalty app sign-up, bulk fuel quote request and lubricant selector pages to lift completed applications and quote requests. It reads the results against the significance and guardrail rules and ships or stops the variant once approved.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the web analytics and experimentation tool: visitors, conversions and guardrail metrics per variant for the test named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Head of Fuels Marketing with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the web analytics and experimentation tool: it ships the winning variant to all traffic or stops the test once approved. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The experimentation standard: significance and sample rules, guardrail metrics such as credit-check failure rate and application quality, the fuel card terms that must appear unchanged, and the pages under test.
Reads from
the web analytics and experimentation tool: visitors, conversions and guardrail metrics per variant for the test named.
Acts in
the web analytics and experimentation tool: it ships the winning variant to all traffic or stops the test once approved.
Hands back
An object with verdict (ship, stop, keep_running or inconclusive), winner (or null), lift_percent, confidence_interval (low and high), p_value, guardrail (metric, control, variant and harmed (true or false)) and reason.
Asks a person when
It ships a winner, sends more than 50 percent of traffic to a new variant, or a variant changes fees, credit terms, consent wording or loyalty terms.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Significance level | 0.05 | A result counts only below this p-value. |
| Least visitors per variant | 3000 | No verdict before each variant reaches this many visitors. |
| Shortest test (days) | 14 | Covers two full weeks of weekday fleet and weekend retail traffic. |
| Most traffic to a new variant (%) | 50 | More than this needs the approver. |
| Least lift to ship (%) | 3 | A smaller significant lift is not worth the change. |
| Guardrail metric | approved applications | A variant that harms this is never shipped. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- No verdict before 14 days and 3000 visitors per variant; until then the verdict is keep running.
- A variant wins only below 0.05 with a lift of at least 3 percent and no harm to approved applications.
- A variant may never change the fuel card fees, credit terms, data consent wording or the loyalty terms; such a test is stopped.
- Never send more than 50 percent of traffic to a new variant without the Head of Fuels Marketing.
- Report the lift with its confidence interval, never a single number.
See the Landing Page Optimization Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.