Back to Bidders

Advergic

Features

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

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'
        }
      }
    ]
  }
];

Banner

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.

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.

When user synchronization is enabled and no usable sync URL is supplied by the bidder response, the adapter can call Advergic’s default setuid endpoint. This endpoint sets the _advid cookie on .avads.live. The cookie is configured with a one-year maximum age and is used by Advergic to recognize browsers and manage advertising frequency caps.

The adapter does not generate a separate persistent user ID in browser local storage. User synchronization is suppressed when COPPA is enabled.

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. Billing notifications supplied in the bid response are handled separately from this optional event tracking.

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 a usable sync URL, the adapter uses the Advergic default setuid endpoint. The fallback may set the _advid cookie described in the User IDs section.

Example:

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

User syncs are not performed when COPPA is enabled through Prebid configuration or the supported getUserSyncs COPPA argument.

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). Publishers remain responsible for ensuring that their use of the adapter, user synchronization, and any identifier storage complies with applicable privacy requirements and their consent-management configuration.

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

Back to Bidders