From a website tag to a server-to-server connection, start with an integration that matches your inventory and technical resources.
Website placements, a compatible player, feeds or programmatic inventory.
Exact endpoints, versions, credentials and account-specific parameters are provided during onboarding.
| Channel | Connection | Best-fit starting point |
|---|---|---|
| Header bidding ↗ | Prebid.js or Prebid Server, connected to an agreed OpenRTB configuration. | Website publishers with display inventory and teams managing an existing programmatic setup. |
| Popunder ↗ | A publisher JavaScript placement with configured XML / JSON demand routing. | Direct publishers evaluating an additional monetization channel for approved website traffic. |
| OpenRTB ↗ | An agreed OpenRTB endpoint, protocol version, inventory schema and event-notification flow. | Publishers, SSPs, DSPs and ad networks with technical teams and programmatic trading requirements. |
| XML / JSON feeds ↗ | A partner-specific XML / JSON request and response contract, or an approved direct link. | Publishers, traffic partners and networks that need feed connections or approved direct-link routing. |
| Search monetization ↗ | Configured publisher search links or provider feeds, with agreed keyword and source parameters. | Publishers and search partners with genuine user queries and approved search experiences. |
| Push subscribers ↗ | Website configuration, permission flow, service worker and compatible push delivery services. | Website publishers looking to develop a browser notification channel with clear user choice. |
| Video / VAST ↗ | VAST tags connected to compatible player or SDK implementations. | Video publishers and partners with web, app or CTV inventory that can support the agreed delivery setup. |
| CPA / CPI / CPL ↗ | Offer tracking links and validated conversion postbacks with agreed attribution rules. | Performance publishers, affiliate partners and advertisers with measurable conversion objectives. |
This is an integration planning guide. It is not an endpoint reference or a claim that every external adapter, demand source or player is supported.
A visitor sees an ad format. The systems behind it may use several different integration methods to select and deliver that ad.
A header-bidding setup brings eligible demand into an auction for a publisher’s ad opportunity. Prebid.js and Prebid Server are different deployment approaches within that workflow. The setup needs defined placements, bidder parameters and timing that works with the publisher’s ad server.
This decision concerns how demand competes. It does not determine whether the eventual creative is a display or video ad.
Explore the header-bidding workflow ↗OpenRTB defines a structure for participating systems to exchange an advertising opportunity and a bid. The integration needs an agreed version, supported inventory, source identifiers and response rules. The request must describe the opportunity consistently enough for the other side to evaluate it.
An OpenRTB connection can support an auction workflow, but the protocol itself is not the complete publisher setup.
Compare header bidding and OpenRTB ↗XML and JSON are data representations used in configured feed connections. Both sides still need to agree what a request means, which fields are required, how results are selected and how a click or other accepted event is recorded.
A feed’s format alone does not establish search eligibility, a pricing model or the behavior of a destination. Those belong to the agreed channel and commercial setup.
Prepare an XML or JSON connection ↗MyBestClick offers OpenRTB connections and VAST video integrations based on IAB Tech Lab specifications. Protocol versions, inventory requirements and partner compatibility are agreed for each integration.
Connect compatible supply and demand systems through a defined bid request and response protocol. Agree the version, inventory fields, auction timing and event notifications before starting a controlled traffic test.
Explore OpenRTB integration ↗Connect video demand to a compatible player through VAST ad responses. Confirm the supported version, creative requirements, playback events and error handling for your player and devices.
Explore VAST video delivery ↗For relevant programmatic inventory, review ads.txt or app-ads.txt authorization, sellers.json records and the OpenRTB SupplyChain object (schain). Confirm the advertising-system domain, seller IDs and actual selling path for the proposed connection.
Read IAB supply-chain guidance ↗Identify the privacy signals required by your markets and partners, including whether the connection requires IAB Europe TCF or IAB Tech Lab GPP. Confirm the participants, applicable purposes and behavior after refusal or withdrawal before activation.
Understand privacy signals ↗Define impressions, deliberate clicks and accepted conversions separately. Agree source identifiers, duplicate-event handling, invalid-traffic criteria and discrepancy review for the integration, so both sides can evaluate the same activity.
Review traffic and reporting checks ↗On this public website, Analytics and Marketing load only after their respective choices are accepted. Visitors can reject optional services or change their decision in Cookie settings. Advertising-platform privacy requirements are scoped separately for the integration.
Manage website privacy choices ↗For your connection, confirm the implemented protocol version, required seller records, applicable privacy signals and reporting rules with your technical contact. The requirements depend on your inventory, markets and partners.
Confirm protocol, fields, source identifiers, timeouts, allowed inventory and consent signals.
Test requests, responses, creative or destination behavior and the events each side records.
Use a limited traffic sample. Compare delivery, errors and commercial reports before increasing volume.
Your existing ad server or player, supported protocols, sample schema without credentials, expected volume and a technical contact will help the team assess the connection.
A connection is useful when both sides understand the inventory, the delivery path and the evidence in their reports. Use the initial conversation to identify the people and systems responsible for each step.
Share the domains or applications you control, the intended formats, your ad server or player and the approximate request volume. Describe the main markets and device mix, and provide a representative request schema with credentials and personal data removed. Include the available consent signals and identify who can make changes on your side. This context helps distinguish a straightforward placement setup from an integration that needs development.
Choose a publisher integration ↗A test should cover a valid request, no eligible response, timeouts and invalid inputs. Check that identifiers survive the full path and that the intended creative or destination can actually be reached. Then align the events in both reports: a request, bid, impression, click or accepted conversion must not be confused with another stage. Increase traffic after the basic delivery and reporting behavior are understood.
Review the reporting checkpoints ↗Confirm the protocol version, supported fields, required seller records, applicable privacy signals and test results with your technical contact. OpenRTB and VAST are IAB Tech Lab specifications. Protocol support, industry membership and independent certification have different scopes; any required certification should be verified for the named company and service.
A straightforward website placement may only need someone who can update the site and test the result. An ad-server, player or server-to-server connection usually needs the person responsible for that system. Share your setup so the team can identify the work and the right technical contact.
The systems may count different events or use different periods, timezones, filters or reconciliation rules. Compare the same source and time range first, then trace a request through response, rendering and the accepted commercial event. Matching definitions is more useful than comparing totals alone.
Record the agreed configuration, who owns changes on each side, the events being measured and how to identify errors. Include the validation results and a way to pause or remove the test integration if the agreed behavior changes. Account credentials belong in the approved secure channel.
Tell us about your website, audience and current setup. We’ll map the next step together.