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: Optional parameter $attr declared before required parameter $content is implicitly treated as a required parameter in /home/superbeet/dev.beet.tv/wp-content/plugins/wp-fancybox-3/src/Core.php on line 207

Deprecated: Optional parameter $value declared before required parameter $field is implicitly treated as a required parameter in /home/superbeet/dev.beet.tv/wp-content/plugins/wp-gdpr-compliance/Includes/Extensions/GForms.php on line 142

Deprecated: Optional parameter $lead declared before required parameter $field is implicitly treated as a required parameter in /home/superbeet/dev.beet.tv/wp-content/plugins/wp-gdpr-compliance/Includes/Extensions/GForms.php on line 142

Deprecated: Optional parameter $username declared before required parameter $errors is implicitly treated as a required parameter in /home/superbeet/dev.beet.tv/wp-content/plugins/wp-gdpr-compliance/Includes/Extensions/WC.php on line 47

Deprecated: Optional parameter $emailAddress declared before required parameter $errors is implicitly treated as a required parameter in /home/superbeet/dev.beet.tv/wp-content/plugins/wp-gdpr-compliance/Includes/Extensions/WC.php on line 47

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: Return type of Requests_Cookie_Jar::offsetExists($key) 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/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) 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/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $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/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) 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/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/superbeet/dev.beet.tv/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) 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/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) 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/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $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/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) 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/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/superbeet/dev.beet.tv/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91

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
joe barone – Beet.TV https://dev.beet.tv The root to the media revolution Wed, 20 May 2020 23:48:42 +0000 en-US hourly 1 https://wordpress.org/?v=5.8.7 Advertisers Warming to News Investment as “Positive Associations” Emerge, GroupM’s Joe Barone https://dev.beet.tv/2020/05/barone.html Wed, 20 May 2020 23:48:42 +0000 https://www.beet.tv/?p=66579 While brand safety was not the main reason for advertisers having pulled back from investing during the early days of the pandemic, those being budgets and messaging, concerns about brand safety or suitability have been a factor —  but they are abating.

Initially putting investment on hold during the initial days, advertisers are finding that news is increasingly providing “positive associations” says Joe Barone, Managing Partner, Brand Safety, US at GroupM in this interview Beet.TV

CTV Lacks Transparency 

Barone sees the CTV ecosystem as troubled by a lack of transparency, multiple technology platforms along wiht fraud and piracy.   He says the industry needs to run exclusion and exclusion lists.  “We  need know where we are running,” he demands.  He calls for the industry adoption of bundle ID’s.

This video is part of a series titled Brand Suitability at the Forefront, presented by Integral Ad Science.  For more segments from the series, please visit this page.

]]>
Beet.TV
GroupM’s Viewability Demands Based On TV, Barone Says https://dev.beet.tv/2017/02/17iabgroupmbarone.html Fri, 17 Feb 2017 02:54:57 +0000 http://www.beet.tv/?p=44583 HOLLYWOOD, Fl — It is now 12 months and one day since GroupM announced it would only buy online ads that it could be proved would be viewed by human consumers – a “100% viewability” demand that has caused some publishers anxiety.

So, why did the media agency make the switch. In this video interview with Beet.TV, GroupM digital ad ops managing partner Joe Barone explains.

“The GroupM 100% standard basically recognises the fact that the dollars moving out of TV are dollars being spent in an environment where you would anticipate sound, you would anticipate the full screen being viewable,’ he says. “So we created a standard.”

Bundled up in concerns over multiple kinds of ad fraud, a couple of years ago, the industry began worrying about rogue publishers invoking ads in spaces where they were not even being seen by audiences but, nevertheless, were triggering an ad buy.

Since then, the industry has done much to address the problem. Now numerous technology vendors offer software that assigns a viewability rating to ad inventory. And that development prompted GroupM to demand 100% viewability or nothing.

“In the last three years, we’ve come a long with with viewability,” Barone adds. “It’s an amazing testimony to the industry coming together and helping our clients achieve what they want, which is having ads seen by real human beings.”

In a world where wholesale advertising targeting data is now commoditised, Barone says the differentiator is the data brans hold about their own customers.

This video is part of a series produced at the IAB Annual Leadership Meeting. Beet.TV’s coverage of this event is sponsored by Index Exchange. For more videos from this series, please visit this page.

]]>
GroupM Ad Ops Chief Joe Barone on Ad-Blocking: Industry Challenges and Solutions https://dev.beet.tv/2015/09/groupmbarone.html Wed, 09 Sep 2015 23:35:45 +0000 http://www.beet.tv/?p=35151 When Apple brings iOS 9 out of beta on September 16, many in digital advertising fear the pillars of their kingdom could begin to crumble. For, the latest version of the mobile operating system includes a content blocking architecture that could allow developers to release ad-blocking extensions for download by users.

Some in advertising are jumping to act.  “We are closely working with the IAB, 4As and ANA to identify anti-ad-blocking solutions, some of which are directly content-related,” GroupM’s managing partner for digital ad operations, Joe Barone, tells Beet.TV in this video interview.

“Publishers will have the opportunity to promote to their users – ‘If you want this content, you need to turn off the ad blocker or there might be some micropayment involved’.”

This Bloomberg article investigates the possible threat to publishers. The Washington Post has already begun blocking ad-blockers.

In truth, Apple is not launching an ad blocker. Indeed, in iAds, the Cupertino company operates a mobile advertising business of its own. But its extensions will allow Safari users to block content – whether that be mentions of the Republican party, Mail Online in its entirety or, yes, ads. Barone says Safari represents “a big chunk of traffic”. Apple is far from alone – one of the leading developers of ad block software for the desktop has just released an ad-blocking mobile browser.

An early 2014 study put the number of people blocking ads at 4.9%. Later studies seem outlandish, but are nevertheless scaring the horses.

“Some numbers say as much as 16% to 25% of US traffic is blocked,” Barone says. “It was more prevalent outside the US. We’ve reached a point where we can’t no longer say that it isn’t an issue in the US.”

“The real concern is targets like millennials, IT professionals, who are almost invariably using ad blockers.”

This interview is part of a series of videos leading up to the DMEXCO conference in Cologne. The series is presented by 4C Insights + Teletrax.

]]>