Back to Bidders

Lane4

Features

Bidder Code lane4 Prebid.org Member no
Prebid.js Adapter yes Prebid Server Adapter no
Media Types display, native Multi Format Support check with bidder
TCF-EU Support no IAB GVL ID check with bidder
GPP Support usstate_all, usnat DSA Support no
USP/CCPA Support yes COPPA Support yes
Supply Chain Support no Demand Chain Support check with bidder
Safeframes OK no Supports Deals yes
Floors Module Support yes First Party Data Support check with bidder
Endpoint Compression check with bidder ORTB Blocking Support no
User IDs none Privacy Sandbox check with bidder

Registration

For assistance or setup instructions, please contact us at adsupport@lane4.io.

Name Scope Description Example Type
placement_id mandatory Placement Id 110044 number
height optional Height of the creative 250 number
width optional Width of the creative 300 number
bid_floor optional Bid Floor Price 0.5 decimal

AdUnit Format for Banner

var adUnits = [
            {
                code: 'banner-ad',
                mediaTypes: {
                    banner: {
                        sizes: [[300, 250]]
                    }
                },
                bids: [{
                    bidder: 'lane4',
                    params: {
                        placement_id: 110044,
                        height: 250,
                        width: 300,
                        bid_floor: 0.5
                    }
                }]
            }
        ];

Native Params

Name Scope Description Example Type
placement_id mandatory Placement Id 110045 number
bid_floor optional Bid Floor Price 1 decimal

AdUnit Format for Native

var adUnits = [
            {
                code: 'native-ad-container',
                mediaTypes: {
                    native: {
                        title: { required: true, len: 100 },
                        image: { required: true, sizes: [300, 250] },
                        sponsored: { required: false },
                        clickUrl: { required: true },
                        desc: { required: true },
                        icon: { required: false, sizes: [50, 50] },
                        cta: { required: false }
                    }
                },
                bids: [{
                    bidder: 'lane4',
                    params: {
                        placement_id: 110045, // Required parameter
                        bid_floor: 1 // Optional parameter
                    }   
                }]
            }
        ];

First Party Data

In release 4.30 and later, publishers should use the ortb2 method of setting First Party Data. The following fields are supported:

  • ortb2.user.id
  • ortb2.user.buyeruid
  • ortb2.user.keywords
  • ortb2.user.ext.*

Example first party data that’s available to all bidders and all adunits:

pbjs.setConfig({
  ortb2: {
    user: {
      id: 123456789,        // Unique pseudonymized ID for the user (e.g., NPI).
      buyeruid: 987654321,  // DSP-assigned user ID for identity resolution.
      keywords: "kw1,kw2",  // Interest or specialty tags (e.g., oncology, cardiology)
      ext: {
        key1: "values",    // Custom healthcare metadata (e.g., icd10), single or comma seperated.
        key2: "values"     // Additional campaign context (e.g., ndc), single or comma seperated.
      }
    }
  }
});

"Send All Bids" Ad Server Keys

These are the bidder-specific keys that would be targeted within GAM in a Send-All-Bids scenario. GAM truncates keys to 20 characters.
hb_pb_lane4 hb_bidder_lane4 hb_adid_lane4
hb_size_lane4 hb_source_lane4 hb_format_lane4
hb_cache_host_lane4 hb_cache_id_lane4 hb_uuid_lane4
hb_cache_path_lane4 hb_deal_lane4

Back to Bidders