Monetization – ADXCG.COM

Prebid 3.0 is coming

admin — Fri, 29 Nov 2019 00:16:38 +0000

Prebid project maintainers have scheduled release 3.0 for november 2019. Most important to remember:

-sizes are defined in other json property.

Old sizes definition:

sizes: [[300, 250], [300, 600]],

Prebid 3.0 sizes requirement:

mediaTypes: {
banner: {
sizes: [[300, 250], [300, 600]] }

-many adapters are not updated yet. All adapters that are not updated will be disabled. Just make sure that your adapter is on 3.0 compatibility list.

app-ads.txt against mobile fraud

admin — Mon, 25 Mar 2019 17:25:34 +0000

IAB Tech Lab has introduced a beta version of the ads.txt protocol specification specific for mobile applications. It will be open for public discussion until February 4.

New app-ads.txt file allows app developers to verify their inventory – just as site owners can. It lists the names and identification codes of all authorized sellers of the advertising inventory available in the app. As a result of the implementation of this Protocol, advertisers will only be able to bid on mobile placements from those sellers listed in the file.
The first version of app-ads.txt was introduced in June, but it outlined only possible approaches to the implementation of the ads Protocol.txt for applications. The current version already describes a specific approach that relies on app stores. Recall that the new tool to combat fraud in programmatic-ads.txt – was first introduced in may 2017. And in July of the same year, IAB Tech Lab published the final version of this Protocol for websites.
The purpose of the ads.txt is to eliminate fraud and increase transparency in programmatic by registering authorized ad sellers and removing illegitimate sellers from the supply chain.

Prebid.js 2.0 Released

admin — Wed, 30 Jan 2019 13:45:54 +0000

Prebid team announced Prebid 2.0 is available. No major changes, however publishers have to check compatibility before upgrade.

IAB released VAST 4.1 specification

admin — Fri, 30 Nov 2018 10:17:26 +0000

VAST 4.1 Updates
The updates made in VAST 4.1 are summarized here:
● Verification: Changes that enable verification to be supported in a non-VPAID architecture (separated from media file). Also includes changes required to work with
Open Measurement.
● Digital Audio Ad Serving Template (DAAST): With VAST 4.1, DAAST has been merged into VAST. This mostly involves providing direction in places where audio ads might need to be treated differently. The main change is an optional “adType” added to the “Ad” element to support the various audio use cases.
● Ad Requests: VAST is a response protocol. 4.1 now includes a basic Ad Request specification, based on macros.
● Updates to Macros: With the new Ad Requests proposal, the Macros section has been completely revamped and updated.
● Server Side Ad Insertion (SSAI) related changes: VAST 4.1 includes minor changes to how headers should be handled. The “Ad Request” section is also relevant to SSAI use cases.
● Deprecating Video Player Ad-Serving Interface Definition (VPAID): While VPAID will likely be in use for some more time, with VAST 4.1 we are taking the first steps to officially deprecate the use of VPAID. The apiFramework attribute on MediaFile, and the conditionalAd attribute on the Ad element are being deprecated.
● Updates to Tracking Events: Added “loaded”, “closeLinear” (back from VAST 3.0). Removed acceptInvitationLinear and timeSpentViewing
● AdServingId: A required field has been added to simplify comparing data about a video impression across the various systems involved with the delivery and tracking of the impression.
● VAST Interactive Templates: Recognizing the need for standardizing interactive ads without ad delivered executable code, VAST 4.1 introduces the concept of interactive templates, with End-Cards as an example template.
● Closed Captioning: VAST 4.1 enables Closed Captioning by standardizing the delivery of Closed Captioning files.
● Flash: Following up on the white paper to transition video ads from flash to HTML5 with VAST 4.1, all references to Flash
and Flash resources are being removed.
● Survey: The survey node is being deprecated as of VAST 4.1.
● Other Updates:
● MediaFile fixes – fixes to UniversalAdId, added support for more types,
changed bounding of Mezzanine files, added support for fileSize etc.
● Added id attribute to “Advertiser” element
● Added “Expires” element
● Added variableDuration to InteractiveCreativeFile

adxcg.com is official Prebid Header Bidding partner for Digital Monetization

admin — Wed, 06 Sep 2017 07:15:14 +0000

After extensive testing by our Publishers our team is one of only a few Prebid.js members that now has has been officialy approved by Prebid.js team.

What this means for your: You can easily integrate our adapter for additional yield optimization. Prebid.js team members verify adapter specification.

Benefits of Using Prebid Wrapper
As claimed by Prebid.org, header bidding auctions run faster using Prebid.js wrapper, which results in decreasing the demand partner response time and ends up providing a better user experience. Furthermore, the technology is quite flexible, works for both mobile and desktop channels including display, native, and video ad types.

Ads.txt against fraud

admin — Sun, 18 Jun 2017 10:22:37 +0000

Networks, advertisers and publishers can fall for scammers who sell low-quality inventory, passing it off as advertising on premium sites at the prices of the original.

Ads.txt is aimed against such fraud. The procedure for purchasing advertising becomes more transparent, which allows to eliminate illegitimate sellers from the supply chain.

What is ads.txt?
Ads.txt is a text file. Developers of web sites indicate in it who has the right to sell advertising and who does not. This file can be viewed by programmatic platforms, agencies and advertisers. It is a specification published by IAB in 2017 for sites.

What will need to be done?
We advise web sites to create an ads.txt file. Publish it on root of your domain. This ensures that the ads will only be shown on the agreed advertising spaces: the advertising budget will be spent on the right audience, and the reputation of the brand will not suffer because of fake impressions.

Make sure you include all the necessary information in the file.

As a domain name, you need to specify the advertising network with which you work. The publisher ID must be replaced by an identification code.