How we write these

The posts on this blog come out of building the product. The material is our own: the rules our audits actually apply, the things the ad platforms' APIs do that surprised us, and the arithmetic behind the calculators on this site.

Where the numbers come from

Every figure describing how AuditRoger works is read from the code that does the work, not from memory. When a post says a search term has to have cost an average order and been clicked twice as often as an order usually takes, that is the rule in the audit, and a test fails if the post and the code ever disagree.

Worked examples use invented numbers, and each one says so. They are there to show the shape of a calculation, not to stand in for a benchmark.

What we will not publish

No statistics about our own customers. You will not read that some percentage of the accounts we audit waste some share of their budget, because we have not measured that and a number with nothing behind it is worse than no number. A test rejects a post that claims one.

When a post turns out to be wrong, we change it and say what changed rather than quietly editing it away.

How AI is used

We use AI tools in our own work, including drafting these posts. The subject, the argument and the material are ours; a draft is written with AI assistance from our engineering notes and from the code itself, and then checked line by line against that code before it is published. Nothing goes up that a person here has not read and agreed with.

We think that is worth stating plainly, because it is a reasonable thing to wonder about anything published today, and because the alternative is letting you guess.

Who writes them

The AuditRoger team. If something here is wrong, or does not match what you are seeing in your own account, write to hello@auditroger.com and we will correct it.