Deprecated: Return type of WP_Theme::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/superbeet/dev.beet.tv/wp-includes/class-wp-theme.php on line 554

Deprecated: Return type of WP_Theme::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/superbeet/dev.beet.tv/wp-includes/class-wp-theme.php on line 595

Deprecated: Return type of WP_Theme::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/superbeet/dev.beet.tv/wp-includes/class-wp-theme.php on line 535

Deprecated: Return type of WP_Theme::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/superbeet/dev.beet.tv/wp-includes/class-wp-theme.php on line 544

Deprecated: Return type of WP_REST_Request::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/superbeet/dev.beet.tv/wp-includes/rest-api/class-wp-rest-request.php on line 960

Deprecated: Return type of WP_REST_Request::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/superbeet/dev.beet.tv/wp-includes/rest-api/class-wp-rest-request.php on line 980

Deprecated: Return type of WP_REST_Request::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/superbeet/dev.beet.tv/wp-includes/rest-api/class-wp-rest-request.php on line 992

Deprecated: Return type of WP_REST_Request::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/superbeet/dev.beet.tv/wp-includes/rest-api/class-wp-rest-request.php on line 1003

Deprecated: Return type of WP_Block_List::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/superbeet/dev.beet.tv/wp-includes/class-wp-block-list.php on line 151

Deprecated: Return type of WP_Block_List::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/superbeet/dev.beet.tv/wp-includes/class-wp-block-list.php on line 175

Deprecated: Return type of WP_Block_List::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/superbeet/dev.beet.tv/wp-includes/class-wp-block-list.php on line 164

Deprecated: Return type of WP_Block_List::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/superbeet/dev.beet.tv/wp-includes/class-wp-block-list.php on line 186

Deprecated: Return type of WP_Block_List::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/superbeet/dev.beet.tv/wp-includes/class-wp-block-list.php on line 138

Deprecated: Return type of WP_Block_List::offsetExists($index) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/superbeet/dev.beet.tv/wp-includes/class-wp-block-list.php on line 75

Deprecated: Return type of WP_Block_List::offsetGet($index) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/superbeet/dev.beet.tv/wp-includes/class-wp-block-list.php on line 89

Deprecated: Return type of WP_Block_List::offsetSet($index, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/superbeet/dev.beet.tv/wp-includes/class-wp-block-list.php on line 110

Deprecated: Return type of WP_Block_List::offsetUnset($index) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/superbeet/dev.beet.tv/wp-includes/class-wp-block-list.php on line 127

Deprecated: Return type of WP_Block_List::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/superbeet/dev.beet.tv/wp-includes/class-wp-block-list.php on line 199

Deprecated: DateTime::__construct(): Passing null to parameter #1 ($datetime) of type string is deprecated in /home/superbeet/dev.beet.tv/wp-includes/script-loader.php on line 333

Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /home/superbeet/dev.beet.tv/wp-includes/class-wp.php on line 173

Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /home/superbeet/dev.beet.tv/wp-includes/wp-db.php on line 3030

Warning: Cannot modify header information - headers already sent by (output started at /home/superbeet/dev.beet.tv/wp-includes/class-wp-theme.php:9) in /home/superbeet/dev.beet.tv/wp-includes/feed-rss2.php on line 8
Mike Yavonditte – Beet.TV https://dev.beet.tv The root to the media revolution Mon, 11 Oct 2021 12:05:34 +0000 en-US hourly 1 https://wordpress.org/?v=5.8.7 Only 20% Of Ads Will Be Addressable, Brands Need A Solution: Yieldmo’s Yavonditte https://dev.beet.tv/2021/10/only-20-of-ads-will-be-addressable-brands-need-a-solution-yieldmos-yavonditte.html Mon, 11 Oct 2021 12:05:34 +0000 https://www.beet.tv/?p=76034 If you thought Apple’s privacy controls for users posed a challenge to advertisers identifying consumers, wait until Google finally gets around to deprecating cookies.

Google may have delayed its switch-off for third-party tracking cookies in Chrome until 2023.

But, in this video interview with Beet.TV, Yieldmo’s CEO Mike Yavonditte says the erosion of targetability presents a problem that must be addressed.

Missing address

“Right now, only about half of all inventory is addressable using a cookie … merely half of all adults,” Yavonditte says.

“A lot of the people that use iPhones, for instance, are not in that target set. They tend to be among the most coveted from a demographic standpoint, yet most, most marketers can’t reach them.”

He says that will get worse when Google switches off cookies. “Addressability will go from 50-50 to about 20%,” he adds. “Brands and agencies and advertisers are going to have to start testing and experimenting with other types of systems.”

After cookies

Yavonditte says potential alternatives include privacy compliance systems and alternative identifiers.

The industry has been racing to plug the addressability gap left by the wave of pro-privacy measures, with a plethora of candidates more diverse than traditional cookies.

Yavonditte’s own company, Yieldmo, which powers an ad marketplace, thinks it has a unique take.

It has a supply-side platform (SSP) technology with an opinion.

The data difference

“Most SSPs do not do not provide targeting and optimization because most of their customers come with their own form of targeting, but we decided to invest in it,” Yavonditte says.

“We spent about $25 million in the last six years, just on the infrastructure required to collect trillions and trillions of the data events every month.

“We take the entire open web… We collect a bunch of information that a lot of other companies like motor IAS or DV360 collect but we also collect dozens and dozens of different kinds of events, every 200 milliseconds, that we believe no one else in the world collects.

“All that data gets organised in very interesting ways, and then gets fed into machine learning models that best correlate to the KPIs of all advertisers that spend money in this marketplace.”

Performance and growth

Yavonditte hopes that tech will help Yieldmo build self-service tools that can increase advertiser performance by 80% to 100%.

The company has been hiring hard over the last year and recently announced integration with LiveRamps Authenticated Traffic Solution.

The company raised a further $2 million in Series C money in mid-2020.

You’re watching “Diversifying Spend: Buying Beyond Audiences” a Beet.TV Leadership Series presented by Yieldmo. For more videos from this series, please visit this page.

]]>
Beet.TV