Slot Identity
Every ad slot in Adkit has a unique identity that determines where ads are served, how analytics are tracked, and what constitutes a booking on that placement.
How slot identity works
A slot is identified by the combination of its site ID and slot name:
For example, if your site ID is site_abc and your slot is named sidebar, the full slot identity is site_abc:sidebar. This identity is used in all API calls for serving ads, logging events, and managing bookings.
Slot names are not page-specific
A slot named sidebar is the same placement regardless of which page it appears on. If you include a sidebar slot on /blog/post-1 and /blog/post-2, any booking for sidebar will serve the same ad on both pages simultaneously.
This is intentional — advertisers are booking a placement on your site, not a specific URL. The placement is defined by the slot name, not the page path.
blog-sidebar, homepage-hero, about-sidebar, etc.Slot identity and the SDK
Both the React SDK and the JavaScript CDN SDK use the slot name to construct the full slot identity when making API requests.
In the React SDK, the slot prop on <AdSlot> is the slot name. The SDK sends both the siteId (from <AdkitProvider>) and the slot name to the serve API, which resolves the full siteId:slotName identity.
In the JavaScript SDK, data-adkit-slot is the slot name. The same resolution happens server-side.
Slot status
Each slot has a status that reflects its current availability:
| Status | Meaning |
|---|---|
| pending | Slot is registered but has not yet been detected on the site. |
| available | Slot is live and can be booked. |
| filled | Slot has an active ad running. |
| inactive | Slot has not received traffic in the last 2 hours. |
| paused | Publisher has manually paused the slot. |
| archived | Slot is hidden but data is preserved. |
A slot transitions to inactive automatically when no mount event is received for 2 hours. This triggers inactivity tracking for any active bookings on that slot.