Back to Bidders

Advergic

Features

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

Note

The Advergic bidder requires an account ID before it can be used. Publishers should contact hello@advergic.com to request an accountId and test setup.

Bid Params

Name Scope Description Example Type
accountId required Advergic account identifier. Publishers should obtain this value from Advergic. '12345' string
endpointId optional Advergic endpoint or placement identifier. When supplied, it is used as the OpenRTB impression tagid; otherwise the ad unit code is used. 'homepage_300x250' string
publisherId optional Publisher identifier supplied by Advergic. 'pub-123' string
custom optional Publisher-defined custom data passed to Advergic in the impression extension. { section: 'sports' } object
position optional Banner position value passed to Advergic. 1 integer

Test Parameters

The following example shows the required setup. Replace YOUR_TEST_ACCOUNT_ID with the test accountId provided by Advergic.

var adUnits = [
  {
    code: 'test-div',
    mediaTypes: {
      banner: {
        sizes: [[300, 250]]
      }
    },
    bids: [
      {
        bidder: 'advergic',
        params: {
          accountId: 'YOUR_TEST_ACCOUNT_ID'
        }
      }
    ]
  }
];

The Advergic adapter supports the banner media type. Banner sizes are read from mediaTypes.banner.sizes and sent to the Advergic endpoint as OpenRTB banner formats.

First Party Data

The adapter supports Prebid First Party Data through ortb2 and ortb2Imp.

Global site, user, device, regulations, and source data are preserved when available. Impression-level OpenRTB data from ortb2Imp is also preserved and sent with the corresponding impression.

Publishers should use the standard Prebid First Party Data configuration:

pbjs.setConfig({
  ortb2: {
    site: {
      content: {
        data: [
          {
            name: 'section',
            segment: [
              { id: 'sports' }
            ]
          }
        ]
      }
    },
    user: {
      data: [
        {
          name: 'publisher_data',
          segment: [
            { id: '123' }
          ]
        }
      ]
    }
  }
});

Floors

The adapter supports Prebid Floors. When a floor is available, the adapter sends bidfloor and bidfloorcur in the OpenRTB impression.

User IDs

The adapter forwards Prebid user IDs supplied through userIdAsEids in the OpenRTB user.ext.eids object.

The adapter also maintains an Advergic user ID in browser local storage when storage access is available.

Event Tracking

The adapter can send additional event notifications to Advergic for win, timeout, and bidder-error analytics.

Publishers can disable these additional event-tracking requests without disabling the auction:

pbjs.setConfig({
  advergic: {
    disableEventTracking: true
  }
});

The normal bid request and bid response processing continue when event tracking is disabled.

User Sync

Advergic supports both image and iframe user synchronization when the publisher enables the corresponding Prebid user-sync type.

If the bidder response does not provide sync URLs, the adapter uses the Advergic default sync endpoint.

Example:

pbjs.setConfig({
  userSync: {
    filterSettings: {
      iframe: {
        bidders: ['advergic'],
        filter: 'include'
      }
    }
  }
});

Privacy

The adapter forwards supported privacy signals to the Advergic endpoint:

  • GDPR consent signals
  • US Privacy / CCPA consent
  • GPP consent
  • COPPA

The adapter forwards the supplied GPP string and applicable section IDs.

Advergic does not currently have an IAB Global Vendor List (GVL) ID and does not declare TCF-EU support (tcfeu_supported: false).

Prebid TCF Enforcement

If a publisher enables Prebid TCF enforcement and configures enforceVendor: true for an applicable rule, the publisher can add advergic to that rule’s vendorExceptions to exempt Advergic from vendor-level enforcement for that rule.

If enforceVendor: false, no exception is needed because vendor-level enforcement is already disabled for that rule.

Example:

pbjs.setConfig({
  consentManagement: {
    gdpr: {
      rules: [{
        purpose: 'basicAds',
        enforcePurpose: true,
        enforceVendor: true,
        vendorExceptions: ['advergic']
      }]
    }
  }
});

This example exempts Advergic from vendor-level enforcement for the specified rule while leaving purpose enforcement enabled. Exceptions apply only to the rules where they are configured and do not override purpose enforcement or other applicable privacy controls. Publishers should ensure their configuration complies with applicable privacy requirements.

Supply Chain

The adapter supports the Prebid Supply Chain Object (schain) and forwards it in the OpenRTB source.ext.schain field.

"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_advergic hb_bidder_advergic hb_adid_advergic
hb_size_advergic hb_source_advergic hb_format_advergic
hb_cache_host_adverg hb_cache_id_advergic hb_uuid_advergic
hb_cache_path_adverg hb_deal_advergic

Back to Bidders