Integrations

To properly monetize your ad slots and recognize users, you must configure Integrations. Bidkernel abstracts the raw configurations required for your ad stack into clean form fields. Integrations can encompass several categories, such as Ad Servers, Bidders, and User IDs.

Types of Integrations Link to section

1. Ad Servers Link to section

Ad Servers are the primary decisioning engines for your inventory (e.g., Google Ad Manager). Configuring an ad server integration tells Bidkernel where to send the winning bids and how to map targeting keys.

2. Bidders (Demand Partners) Link to section

Bidders represent the SSPs and exchanges competing in your header bidding auction (e.g., AppNexus, Rubicon, IndexExchange). You can supply required global parameters (such as placementId or siteId) through these integrations.

3. User IDs (Identity) Link to section

User ID modules allow you to recognize users across sessions and domains (e.g., SharedID, UID2, LiveIntent), which significantly increases the value of your inventory to buyers in cookieless environments.

Adding an Integration Link to section

1. Navigate to your target Property.
2. Go to the Integrations tab and click Add Integration.
3. Select the desired integration from our supported catalog.
4. Provide the required parameters specific to the integration type.

Integration Scope Link to section

Integrations can often be configured globally (applying to all ad slots) or mapped explicitly to specific ad slots. This allows you to route demand or apply identity solutions precisely based on performance or partner requirements.

When Bidkernel compiles your custom Prebid.js bundle, only the code for the active integrations you have configured is included. This ensures the lowest possible bundle sizes and maximizes fast loading for high web vitals.

Bidder Targeting & Constraints Link to section

Bidkernel allows you to apply precise targeting rules to each bidder integration.

Every additional bidder increases the auction latency. By applying smart constraints, you ensure a bidder is only called for impressions it is likely to bid on, improving overall page performance.

Ad Slots Link to section

By default, an active bidder will participate in auctions across all available ad slots. Selecting specific Ad Slots here binds the bidder exclusively to those placements.

Exclude Slots Link to section

Inversely, you can exclude a bidder from specific ad slots. If a slot is listed here, the bidder will be blocked from participating in its auctions, regardless of other targeting rules.

Media Types Link to section

Restrict a bidder to specific ad formats. For instance, if you have a video-only demand partner, you should restrict their requests exclusively to slots supporting video.

Viewports Link to section

Restrict a bidder to specific viewports (e.g., Mobile, Tablet, or Desktop) defined at the property level. This allows for precise control over which environments a demand partner executes in, rather than relying on inferred device types.

Geos Link to section

Geographic targeting uses standard ISO 3166-1 alpha-3 shortcodes (e.g., USA, CAN, GBR). Using Geo constraints is the single most effective way to eliminate wasted timeout latency from regional demand partners.

Sizes Link to section

Use Exact Sizes targeting to only trigger a bidder for specific dimensions (e.g., strictly 300x250 or 728x90). If a slot is dynamic, the bidder will only be included if the slot's potential dimensions overlap with the targeting rules you define here.