Revenue attribution on every plan,
free to start.

An event is a pageview or a custom event that the server accepted after validation, bot filtering and duplicate removal. Rejected payloads are not counted. A retry of the same event id is stored once and counted once.

The billing page shows the events counted this month next to your plan. Events past the limit are refused, not silently dropped, until the next month starts or you upgrade. Your dashboard and history stay open the whole time.

Plans and limits are configured on the server, and the entitlement service decides what your account may do. Upgrading takes effect immediately. Downgrading applies the new limits from the next period.

The tracker stores one random identifier in the browser under the key aback_vid. It is not a cookie, it is not shared between sites, and the server stores a one way derivation of it. There is no device fingerprinting.

Dodo Payments is the only provider used to sell Aback Analytics subscriptions. If your own product also uses Dodo Payments, you can report that revenue into Aback Analytics through the same revenue endpoint.

Yes. There is a server-side event API, a revenue event API and a website scoped read API. Each API key carries explicit scopes, so a key that can send events cannot read reports and the other way round.

A cancelled subscription keeps its paid entitlements until the end of the period that was already paid for. After that the account falls back to the free plan, and the retention window applies as it does for any other account.

Refunds are handled by Dodo Payments against the transaction you paid with. The request is processed against that same transaction once it is approved, and the subscription state follows the provider.