-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.

• Support for Secure Interactive Media Interface Definition (SIMID). SIMID is the replacement for VPAID to support interactive use cases.
• Allow ClickThrough element to be specified in a wrapper to better enable the use case defined in 2.3.5 (managing assets with an ad cloud)
• Added error code 206 to support use cases where the player might decide not to play an ad (for example during live broadcasts where the break needed to be shortened at the last moment).
• Allow multiple UniversalAdID nodes to be provided
• Updates to Icon and Icon ClickFallbackImages
• New macros for better adbreak info

ADXCG.COM SSP a leading special projects 100% programmatic SSP has integrated The Trade Desk’s unified ID solution into their supply stack. This joint commitment is an effort to improve the digital match rates outside of walled gardens in the digital advertising ecosystem. This is available through The Trade Desk offering its inclusive, global cookie footprint at no cost to the digital advertising industry at large.

Adoption of the free unified ID solution allows all parties across the supply chain (SSPs, DSPs, DMPs and data providers) to use The Trade Desk’s cookie footprint to increase their own cookie coverage across the global independent internet.

“Unified ID provides many benefits to marketers, digitals platforms and consumers, which is why we are excited to join The Trade Desk on this initiative” said ADXCG.COM CTO

As expected, Google announced upcoming changes to how its Chrome browser handles cookies and fingerprint addresses at its annual I/O developer conference. New tools in Chrome will allow users to more easily block or delete third-party cookies, Google said. The company also announced a browser extension that will show more information about the parties involved in advertising transactions and tracking. New cookie handling in Chrome. Google said the “dumb approaches” to blocking cookies were not effective for users because they handle all cookies in the same way — from third-party cookies used to log users into sites to third-party cookies used for tracking-so it changes the way cookies work in Chrome. In terms of security, Google said the change would also help protect cookies from cross-site injections and default disclosure attacks. Eventually, Google said, Chrome will limit cross-site cookies to HTTPS connections.
In the coming months, developers will need to make clear which cookies can work across sites and potentially be used to track users with a new mechanism based on the SameSite cookie attribute on the Internet. The SameSite attribute can be used to restrict the use of cookies in the context of the first or the same site. In the weeds. Chrome 76 will include a new cookie flag of the same site by default, according to the web.development. Cookies without the SameSite attribute will not be available in a third-party context. Developers will need to declare cookies that should be available on third-party sites in Chrome with SameSite=None. Google says it will allow Chrome users to clear cross-site cookies and leave single-domain cookies, which are used to log in and configure the site in tact.
Developers can start testing their sites to see how changes to cookie processing will affect their sites in the latest version of Chrome for developers. We deal with fingerprints. The company also said it was taking additional measures to limit browser fingerprinting techniques, which are used as workarounds for in-place tracking when users opt out of third-party cookies. Google said Chrome plans to “aggressively restrict” browser fingerprinting and reduce the ways browsers passively fingerprinted. “Because fingerprints are not transparent and are not under the user’s control, this leads to tracking that does not respect the user’s choice,” Google said. The company added that it does not use fingerprints to personalize ads or allow fingerprint data to be imported into its advertising products.
Custom cookie controls. Google said it would provide users with more information about how sites use cookies and give them easier means to manage cross-site cookies. The company did not say what those changes would look like in Chrome’s interface, but said it would review features for users later this year. Ad data browser extension. The company also announced that it is developing an open source browser extension that will display the names of ad tech players participating in an ad transaction, as well as companies with ad trackers attached to the ad. The extension will also show the factors used for personalization. This will be the same information that Google shows when you click “why this ad”.
Why should we care. The end of the digital advertising ecosystem’s reliance on tracking and attribution cookies is long overdue. Cookies are not supported in mobile applications, and mobile websites and applications now account for the majority of advertising costs. Google and Facebook have moved from cookies to using deterministic identifiers of registered users. Chrome is also not a trailblazer in this area. It follows in the footsteps of Apple Intelligent Tracking Prevention (ITP). The latest version, ITP 2.2, will limit cross-site cookies to track users on Safari for one day. Earlier this week, Microsoft announced that its chromium-based Edge browser will also have new tracking controls for third-party cookies.
For marketers, the full impact of these changes and how users respond to the tools probably won’t be seen for months, but will have a significant impact on remarketing, Analytics, and attribution. It’s also unclear whether (or how much) the new Chrome requirements will benefit Google with its relationship with billions of users compared to other advertising technology firms, as the Wall Street Journal predicted.

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.

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.

This year DMEXCO conference part will have 18 stages and 570 speakers. The discussion will focus on the on the following topics: artificial intelligence, GDPR. The exhibition will bring together marketing and media professionals as well as industry leaders for networking, learning and inspiration.

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.