Using burl to send billing notifications
Publishers can use the OpenRTB An open industry standard for communication between buyers and sellers of online advertising in real-time bidding auctions. It's published by the IAB. burl
(billing notify URL) field to notify Index Exchange (Index) and DSPs when an ad renders on the user’s device and becomes billable. Using the burl
field standardizes the billing notifications sent to DSPs and helps reduce reporting discrepancies. To use burl
with Index, your software development kit (SDK) or server must support HTTP 302 redirects.
To enable burl
with Index, contact your Index Representative.
Index accepts burl
for publishers using either server-side A process where the header bidding takes place on an external server, as opposed to bidding from a browser. This is also called as server-to-server (S2S) header bidding. or client-side A type of header bidding where the auction takes place on the user's browser. beaconing:
-
Server-side beaconing: You send Index a notification when a billable event has happened on the device or app, initiated from your ad server A platform that manages, stores, and delivers advertisements to a publisher's site. or SSAI Server-Side Ad Insertion (SSAI). The technology that combines ads into a video file on the server-side, then delivers video content with the ads embedded to the video player as one file. Also known as server-side ad stitching.. For more information, see Sending billable event notifications (burl) to Index through server-side beaconing.
-
Client-side beaconing: You send Index a notification when a billable event has happened from your site or app code. For more information, see Sending billable event notifications (burl) to Index through client-side beaconing.