Fidelity
New questionRe-run this query

did we hit our targets in august

anon
ANON8 Sept, 14:17agent took 2m 15stask 495dc80e

By the end of August, average order value had beaten its 2026 target and annual revenue was ahead of the pace needed to hit target.

1 Aug 2026 to 31 Aug 2026 · compared with 1 Aug 2025 to 31 Aug 2025 · Europe/London

What happened

  • Annual revenue is ahead of pace

    £2,657,780
    up +11.10%from £2,392,242

    Revenue reached £2,657,779.69 by 31 August, equal to 84.7% of the £3,139,321 annual target after 66.7% of the year; it was 11.1% higher than at the same point in 2025.

  • Average order value beat target

    £30.04
    up +2.70%from £29.25

    Year-to-date average order value was £30.04, 0.9% above the £29.77 target and 2.7% above the comparable 2025 level.

  • August revenue grew strongly

    £446,522
    up +25%from £357,121

    August generated £446,522.29 in ecommerce revenue, up 25.0% year on year.

  • August transactions increased

    14,846
    up +18%from 12,586

    Transactions rose to 14,846 in August, 18.0% more than in August 2025.

  • August sessions increased

    225,556
    up +19.50%from 188,679

    Sessions reached 225,556 in August, up 19.5% year on year.

Charts

2026 Target Performance Through Augustcombo
Combo chart comparing actual target performance through August with target or expected pace; revenue completion is 84.7% against 66.7% expected pace, while average order value is 100.9% of target.

Source: GA4 and Zequence objectives; cumulative revenue completion and year-to-date average order value through 31 August 2026.

What to do next

  • Protect the stronger order value

    Achieved

    Continue the merchandising, bundle, and pricing tactics supporting a £30.04 year-to-date average order value, and monitor it monthly against the £29.77 floor.

    TowardsMaintain an average order value of £29.77 across 2026

  • Maintain revenue momentum

    On track

    Only £481,541.31 remains to reach the annual revenue target. Prioritise proven acquisition and retention activity while checking that the August growth remains profitable.

    TowardsAchieve £3,139,321 in total ecommerce revenue during 2026

Objectives

On track1Achieved4of 5 objectives

  • Achieve £3,139,321 in total ecommerce revenue during 2026

    On track

    Target £3,139,321actual £2,657,780

    Revenue was 84.7% of target by the end of August, ahead of the straight-line pace of 66.7%.

  • Achieve £2,354,490.75 in total ecommerce revenue during 2025

    Achieved

    Target £2,354,491actual £2,354,491

    Zequence marks this historical 2025 objective as completed.

  • Deliver a cumulative ROI of 345% across 2025

    Achieved

    Target 345%actual 345%

    Zequence marks this historical 2025 objective as completed; GA4 alone does not contain the cost data needed to recalculate ROI.

  • Maintain an average order value of £27.39 across 2025

    Achieved

    Target £27.39actual £27.39

    Zequence marks this historical 2025 objective as completed.

  • Maintain an average order value of £29.77 across 2026

    Achieved

    Target £29.77actual £30.04

    Year-to-date average order value was £30.04, 0.9% above target.

Notes

  • GA4 returned no sampling or thresholding warning. Average order value was calculated as purchase revenue divided by transactions; revenue pacing uses a straight-line annual benchmark and does not account for seasonality.
  • August 2026 was compared with August 2025 because the question asks whether targets were hit in August and year-on-year comparison controls for seasonality.
  • Annual objective progress uses 1 January–31 August 2026 and compares it with 1 January–31 August 2025.
  • Average order value is calculated as purchase revenue divided by transactions because GA4 does not provide an average-order-value metric in the available schema.
  • The report is anonymised throughout; underlying numeric data uses the configured anonymised source property.
  • All objectives returned by Zequence are included; 2025 objectives are historical and were already marked completed.
  • The saved file was created before its own URL was available, so its embedded jsonFileUrl may show a placeholder; the inline report contains the valid recovery URL.