Accuracy
Numbers you can get paid on
Partners are paid and advertisers are invoiced from these numbers, so accuracy comes before features. Here is what Metrixed guarantees, in plain words, and the automated checks that hold us to it.
One conversion per order
Twenty identical postbacks sent at the same instant create exactly one conversion and one ledger entry. Retries after a timeout or a crash get the same answer.
Checked by: Reconcile suite: 20 identical parallel postbacks, one created, one stored.
Restarts and outages do not lose or double clicks
Clicks are written to local disk before the redirect is answered and published once after a restart. Database, queue and cache outages delay events; they do not drop or duplicate them.
Checked by: Chaos suite: every service killed and restarted, stores taken down, CPU starved, clocks skewed, under sustained load.
Reports agree with the raw events
A labelled stream of clicks and conversions is checked at every layer: redirect, event stream, raw tables, reports, portals, logs, caps and the ledger.
Checked by: Reconcile suite: the expected value comes from the test harness, never from another layer.
Money adds up
Statements, invoices and payout runs are checked against expected balances, including carryover and tiered commissions.
Checked by: Ledger oracle against a fixed fixture.
Caps are never exceeded
Twenty parallel postbacks against a cap of five admit exactly five. Hard click caps hold even when the cache is unavailable.
Checked by: Reconcile suite and chaos suite.
The product checks itself
A continuous self-audit compares raw events, aggregates, the ledger and cap counters, repairs derived data and shows a verified badge on the dashboard.
Checked by: Data-health checks in the product, with a corruption test in the suite.
How it is tested
Real traffic, a full stack, an independent answer
The suites send labelled clicks and postbacks through the same services that run in production, then compare every layer with the value the test harness expects. A layer is never checked against another layer.
Every change to the main branch
Replays of recorded traffic, a live end-to-end customer path, the reconcile suite on a fresh stack, and the reporting and ledger oracles.
Every night
Two reconcile passes on one stack, the chaos suite under load, and a differential oracle over 300,000+ events.
Under faults
The chaos suite kills and restarts every service, takes databases, queues and caches down, starves CPU and skews clocks while traffic flows, then counts what was stored.
Under contention
Identical postbacks are fired in parallel, thousands of rounds at a time on small machines, to prove each order is answered and stored once.
In the product
The dashboard tells you when it last checked
A continuous self-audit compares raw events with report aggregates, the ledger with statements and payouts, and cap counters with what was admitted. When all checks pass, the dashboard and reports show when the numbers were last verified.
The limits, stated openly
Guarantees have edges. These are ours.
- A server that loses power before its disk cache is flushed can lose the clicks it had just written; a process crash or restart does not.
- When the cache that holds click sessions is unavailable, repeat clicks are counted as unique until it is back; offers with hard click caps send that traffic to their fallback instead.
- Postbacks and webhooks to your systems are delivered at least once. Each attempt carries the same idempotency key, so your receiver can ignore a repeat.
- A derived report row that falls behind its raw events is found and repaired by the data-health check; the raw events and the ledger are the record.
Bring your hardest reconciliation
Send us the report that never matches your invoice. We will show you how the same month looks in Metrixed.
Monthly billing No setup fee Fraud prevention in every plan