Report an error
Found a figure that is wrong? This is the fastest way to get it fixed.
Last reviewed
Every figure here is read automatically from a vendor's published pricing page, and automated reading goes wrong in ways that look entirely plausible on the page. A tier gets renamed, a price moves into a different element, an annual rate is presented where a monthly one was, and the result is a number that is confidently, specifically incorrect. Corrections are the single most useful thing anyone sends.
Before you send it
Every data page on this site ends with a provenance table: each datapoint, the exact URL it came from, the date it was read, and how it was extracted. That table is worth thirty seconds of your time first, because it distinguishes two quite different problems:
- The figure does not match the source page. This is a reading error and is usually fixable within a day.
- The figure matches the source page, but the source is out of date. The date in the table tells you how old the reading is. If the vendor has since changed their page, the next crawl picks it up on its own — though telling us is still useful, because it can mean the crawler is being served a cached or region-specific version of the page.
Sending it
Email a correction — this opens a message to hello@pricingalmanac.com with the right fields already in it. If your mail client does not open, send the same thing by hand.
Include, as far as you can:
- The URL of the PricingAlmanac page carrying the wrong figure
- What it currently says
- What it should say
- Where you checked — a vendor URL is ideal, since it can be verified directly
A screenshot is welcome but never sufficient on its own: a figure is only corrected against a source that can be re-read, because a correction made on somebody's word has exactly the same problem as the error it replaced.
What happens next
- Corrections are read by a person, not triaged automatically. This is a small project; expect a reply within a few days rather than within the hour.
- A confirmed reading error is fixed at the source — the rule that misread the page is corrected, and the fix applies to every figure that rule produced, not just the one reported.
- Where a figure cannot be verified against a live page, it is withdrawn rather than corrected to a guess. A page that loses too many figures stops being published.
- You will not be added to any list, and your address is used only to reply. The privacy policy says so in more detail.
Other kinds of report
- You are the vendor and want the crawler stopped. The crawler page explains how to block it yourself in two
lines of
robots.txt, with no need to contact anyone. - Something on the site is broken rather than wrong — a dead link, a table that will not render, a page that fails to load. Same address.
- You disagree with how something is measured. The methodology sets out every threshold and assumption the site uses; arguments against any of them are welcome and have changed things before.