Revenue Impact & ROAS
Tailor turns each test's lift into an estimated revenue figure, using what a conversion is worth to you, and rolls those up into a 12-month report of estimated test impact.
Set a Conversion Value
Go to Settings β Goals β Conversion value and choose one of two options:
- Use the primary ad platform's average conversion value. Tailor takes the average value from the connected ad platform with the highest spend. Add the drop-off between a conversion on your page and a conversion the platform counts, as a percentage, so the estimate is not overstated.
- Use one site-wide average conversion value. Enter a single figure, such as your average order value or the value of a booked demo.
The setting applies to every report as soon as you save, past results included. Each test is priced on its primary conversion goal. A test with no goal falls back to detected CTA clicks, which is directional only.
Per-Conversion Values
When every conversion is worth a different amount, send the value with the conversion instead of using an average:
- Shopify. Order value and currency are read from the order automatically. See Shopify Integration.
- Your own code. Pass a value and a currency when you record the conversion:
Tailor.convert("YOUR_GOAL_KEY", { value: 129.0, currency: "USD" });Currency
Under Settings β Goals β Currency, set your Report currency and add any other currencies your customers pay in. Every revenue total is shown in the report currency, and Tailor converts each conversion at that day's exchange rate. The setting saves as you pick, and reports switch on their next load.
Where It Shows
- A test's dashboard. A card shows the estimated annual revenue increase for the test, with a How this is estimated breakdown.
- Home. Impact banners summarize what your tests have added.
- The revenue impact report. Under Analytics, a 12-month lookback you can read by month or by test, with a How this is calculated toggle for the method behind each figure.
How It Is Calculated
The estimate is the extra conversions the variant produced, multiplied by the conversion value, then annualized. Only days that had traffic count toward the annual figure. The card names which of four methods it used:
| Method shown | Used when | Calculation |
|---|---|---|
| The value you set | You entered one site-wide average conversion value | Extra conversions Γ your value |
| Your ad platform's value, less your drop-off | You chose the primary ad platform's average conversion value | Extra conversions Γ the platform's average value, reduced by the drop-off you entered |
| Counted by your ad platform | The test targets specific keywords or campaigns | The platform's own conversions and values for that traffic |
| Conversions only | No conversion value is set | Extra conversions, with no revenue figure |
A test is included only after it has run for 3 active days and has 50 visitors on both the original page and the variant.
ROAS
The ROAS card in Analytics is return on ad spend: the conversion value your ad platform reports, divided by ad spend. It uses the ad platforms you have connected, and both numbers come from the platform itself. The Ads guide covers connecting them.
What It Does Not Tell You
- Figures are estimates of test impact, so they will not reconcile line by line with booked revenue in your finance system.
- An annualized figure assumes the lift holds for a year. Seasonal pages and short campaigns will not.
- If a variant attracts smaller orders, an average conversion value overstates its revenue. Send per-conversion values to catch that.
- Downstream outcomes such as pipeline need a connected goal. See Amplitude Sync for Downstream Conversions.
