The requirements for using Easybid are as follows:

For all plans
– Prebid.js version 9.19 or later
– A CMP including Nexx360 (ID 965) and Italiaonline (ID 1068) as vendors
– Compliance with TCF 2.3

For the Full Stack and MCM plans
– A Google AD Manager network code

For the MCM plan
– Being a Publisher with a large-scale network

For the initial setup, the following information is required:
– Domain
– Placement name
– Ad formats (sizes)
– Desktop/mobile indication, if available

Three integration options are available, depending on the chosen configuration:

– Header Bidding only: Easybid is integrated as a bidder within the Prebid.js stack using the relevant tagIds. The Prebid.js bundle in use must include the Nexx360 adapter, for which Easybid acts as an alias.

– Header Bidding + Google/Amazon (snippet-only): This option does not require any existing Prebid.js configuration. Integration is carried out exclusively through a code snippet. Activation of Google MCM between the Publisher and Easybid is required.

– Dedicated AD Server: This option provides access to a fully featured Google AD Manager (GAM) AD Server instance.

The Easybid tagId is a unique identifier assigned to each placement. It is required to correctly link placements to the Prebid.js configuration.

Yes. You must add the Easybid lines to the domain’s ads.txt file to allow proper campaign delivery.

Yes. You can provide Easybid with a customized blocklist to exclude specific categories or advertisers.

Easybid provides a customer area where key performance data is available, including impressions and net revenue.

Payment is made within 30 days from the end of month of the invoice date (EOM).

Yes. You need to integrate the dedicated SDK (MAOR, Mobile Advertising Orchestrator and Rendering) into your app, which handles and manages the entire programmatic demand.

Detailed instructions are available here:

MAOR Documentation for Android

MAOR Documentation for iOS