AIVORIA collects spend from your TikTok ad accounts, matches it with revenue from your tracker and shows profit per campaign — on one screen, without exports and spreadsheet reconciliation.

The daily overview. Figures shown come from a demonstration dataset.
Data comes from the TikTok Marketing API at campaign level. Dates are calculated in each ad account's own time zone, so the totals match what the advertiser sees inside TikTok.
Revenue is pulled from the tracker and matched to spend by campaign identifier. The team sees profit and ROI, not just how much was spent.
Ad accounts in different currencies are never summed blindly. The original amount is stored as reported; conversion happens only at display time, so past reports are never rewritten.
An administrator sees the whole team; a media buyer sees only their own ad accounts and campaigns. The separation is enforced server-side, not hidden in the interface.
Ad accounts are linked to antidetect-browser profiles, so it is always clear which fingerprint and proxy a given ad account is operated from.
The application requests read access to advertising statistics. It does not create, modify, pause or delete advertising campaigns.
Once the owner of an ad account approves access, the service requests only what the report needs:
The service does not request or store personal data of TikTok users, creative content, or audience data. No write scopes are requested, so the application cannot change anything inside an advertiser's account.
The ad account owner opens a TikTok authorisation link and approves access. The resulting token is stored by the service and used solely to request statistics for that ad account. One TikTok login may cover several ad accounts — all of them are added at once, so no part of the spend goes unaccounted for.
Access can be revoked at any time on the TikTok side; the service then stops receiving new data.
A walkthrough of every screen with real interface captures, plus the five steps from registering the application to reading the first report.
Open →Who builds the service, the problem it started from, and the principles the code actually follows — including what it deliberately does not do.
Open →What data is processed, what is never collected, how long it is kept, how access is revoked and how to have collected data removed.
Open →Access rules, connecting ad accounts, acceptable use, and our relationship to TikTok — the service is independent and read-only.
Open →