Facebook’s Miscalculated Metrics: What Marketers Need to Know

Facebook's Miscalculated Metrics: What Marketers Need to Know. Things were overestimated. And at the end of the day, what did it mean for marketers? Instead, the total viewing time was divided by the number of times the video was watched for three seconds or more. So, let’s say a video received a total viewing time of five hours, or 300 minutes, and it was watched by a total of 1,000 people, 700 of whom watched it for at least three seconds. The viewership metric should be 30%. Facebook clarified that this error would not impact paid ads. In addition to the Page Insights, the bug really only impacted a total of four out of Facebook’s 220 measured metrics, according to WSJ. What It All Means for Marketers So just how seriously should we be taking it? And, we’ll continue to bring you updates to all things social as they emerge.

17 Hidden Facebook Marketing Tools That Will Increase Your Engagement by 154%
The Do’s and Don’ts of Facebook Ad Visuals for Non-Designers
How to Establish Thought Leadership on Emerging Social Platforms
Facebook Metrics.png

Over the past couple of months, you may have heard some things about Facebook’s metrics.
There was talk of numbers — lots of them. Things were overestimated. Others were underestimated. People were kind of upset. But mostly, they were confused. What the heck happened? How was Facebook going to respond? And at the end of the day, what did it mean for marketers? Breathe, and don’t panic — we’re here to answer all of that.But before we dive in, let’s make one thing clear — none of it is the end of the world. In fact, most of the issues have already been addressed and repaired; at this point, the most important item on our agenda is to clarify what’s actually going on.

What Happened?

 

It started with video


The drama began in September 2016, when Facebook revealed that there was a problem with its video viewership metrics -- the average time that users spent watching videos was being largely overestimated.
Mathematically, Facebook wrote in a statement, that metric should have been the resulting figure from dividing the total time spent watching a video by the total number of people who played it. Instead, the total viewing time was divided by the number of times the video was watched for three seconds or more.
So, let’s say a video received a total viewing time of five hours, or 300 minutes, and it was watched by a total of 1,000 people, 700 of whom watched it for at least three seconds. The viewership metric should be 30%. Instead, Facebook was dividing those 300 minutes by 700, resulting in a larger metric of nearly 43%. And, says the Wall Street Journal [WSJ], that went on for nearly two years.
For a social media platform that boasts how effective its video tools are for marketers, the announcement was an embarrassment. The advertising world was especially unhappy about it -- Publicis Media, an ad-buying agency, told its clients that Facebook indicated viewing time overestimates of up to 80%. There were calls for third-party metric verification protocols to be put in place, and while Facebook said that it fixed the error and would be looking into such improvements, the metric misfortune didn’t end there.

A bit of a bug

 
In fact, just yesterday, Facebook announced that it discovered a bug in its Pages Insights that’s been lurking since May. The summary displaying seven- or 28-day organic page reach was incorrectly added up as the sum of daily reach over that period. That means duplicate visitors were being counted in every instance, leading to a number that was 33% higher than it should have been for seven-day summaries, and 55% for the 28-day ones. Facebook clarified that this error would not impact paid ads.
Here’s how Facebook visually represented the error -- the red circle indicates where the duplicate viewership would have appeared.
Facebook Page Insights
Facebook Page Insights

But you’ll notice that there are green circles in that image, too. Those indicate the insights that...

COMMENTS

WORDPRESS: 0
DISQUS: 0