Skip to main content
AdXensor tracks four event types automatically. You do not need to write any tracking code — the SDK handles everything once initialized.

Tracked events

How events are sent

All events use navigator.sendBeacon — a non-blocking, fire-and-forget transport that survives page unload. The SDK falls back to fetch with keepalive: true when sendBeacon is unavailable. Events are sent to: POST https://core.adxensor.com/v1/events/{type}

Event payload fields

Every event includes these base fields: Country, OS, and browser are resolved server-side from the IP and User-Agent — no client-side fingerprinting.

Session deduplication

Impressions and views are deduplicated within a browser session using sessionStorage. Each ad is recorded at most once per session, even if the user visits the same page multiple times in the same tab. The deduplication key is stored in sessionStorage under _adx_fired.

Manual event firing (advanced)

If you need to fire events manually (e.g. for a custom ad renderer), you can use the lower-level Tracker API:

Viewing stats in the dashboard

Events are processed in near-real-time. You can view aggregate impressions, views, and clicks under: Publisher Dashboard → My Sites → [Your Site] → Statistics