- Home
- Technology
Infrastructure engineered for measurement, trust and money.
The Adfacten platform has been continuously improved over the years and in 2026 reached its most advanced architecture: a high-speed tracking engine, an event stream, a real-time analytics database and a double-entry accounting ledger. One goal: every click, every conversion and every cent must be provable.
The journey of a conversion.
The hot path (redirects and postbacks) is kept separate from business logic. The tracking engine responds in milliseconds; heavy work is processed safely through the event stream.
Tracking engine
Redirects, postbacks, pixels and ad tags. Signed, time-limited click IDs; location and device resolved at the network edge.
Event stream
Every click and conversion is written to a durable event stream; workers consume it idempotently, so no event is ever lost.
Ledger
Every approved conversion is posted to the ledger as debit and credit entries. Balances aren't calculated; they're summed.
Analytics
A columnar database that scales to billions of rows; reports in seconds, with sub ID breakdowns.
Measurement ready for a cookieless world.
As browsers restrict third-party cookies, browser-based tracking loses data. On Adfacten, the default method is the server-to-server (S2S) postback.
- Signed click IDsForged or tampered identifiers are rejected at the very first step
- DeduplicationOrder numbers and event IDs ensure the same conversion is never counted twice
- Status lifecyclepending → approved / rejected / refunded; every transition logged
- Multiple sourcesS2S, pixel, MMP, coupons and clickless attribution tokens
- Publisher postbacksMacro-based callbacks to publisher systems; signing and a test tool
Fraud protection, layer by layer.
Infrastructure signals
Data center IP ranges and ASN detection; bot and server-originated clicks are separated out.
Behavioral signals
Click-to-conversion time, conversion-rate anomalies and repeated identifiers are all scored.
Rules engine
Advertiser- and network-level rules: block, flag, route to review. Every decision is logged with its reasoning.
API-first. Even the dashboard uses the API.
Anything you can do in the dashboard, you can do through the REST API. Consistent identifiers, decimal-string money amounts, ISO-8601 UTC timestamps and the RFC 9457 error format.
REST API
api.adfacten.com/v1 · OpenAPI 3.1
Webhooks
React instantly to conversions and events
Reporting API
Data straight into your BI tools
MCP
Tools for AI agents
curl https://api.adfacten.com/v1/me \ -H "Authorization: Bearer af_live_XXXXXXXX" # Money: decimal string + currency { "amount": "12.50", "currency": "TRY" } # IDs: prefixed and opaque off_… campaign · org_… organization · cnv_… conversion
A system that runs quietly and scales safely.
KVKK by design
Full IP addresses and browser details are deleted automatically after 30 days.
Zero-downtime releases
Redundant services; an unhealthy release is rolled back automatically.
Encrypted backups
Regular, encrypted, off-server backups.
Public status
Live service status at status.adfacten.com
Technical questions.
What is an S2S postback and why is it recommended?
An S2S (server-to-server) postback reports a conversion directly from the advertiser's server to the tracking server. It does not depend on browser cookies, so ITP, cookie restrictions and ad blockers do not affect it.
Where is data stored and for how long?
Transactional data lives in a relational database and event data in an analytical database. Full IP addresses and user agents are deleted automatically after 30 days; reporting uses anonymised fields.
Is the API backwards compatible?
Yes. /v1 is backwards compatible; breaking changes ship as a new version and are announced in advance. Errors use RFC 9457 problem+json.
Where can I see system status?
The live status of tracking and API services is published at status.adfacten.com.
Your next growth channel starts here.
Sign-up is free. Once your application is reviewed you get access to campaigns and create your first tracking link in minutes.