What to do with erroneous Facebook data

Last week, Facebook had to admit that impression data was reported incorrectly. The good news is that reach was usually under-reported, so if anything you’ll notice a slight bump in your reach and impressions.

Those of you who are data geeks may have also noticed that paid reach figures are weird, too, especially if you’re running promoted posts. (See below for paid, organic, and viral reach as reported on a single timeline post.) The paid numbers are showing differently.

facebook ad data

Part of that could be the near real-time posts reporting on a different schedule than the ads tool, potential page post ads that aren’t being captured in a promoted post, or other known bugs that affect reporting.

When you see conflicting numbers, the best rule of thumb is to go with what’s in the ads system at facebook.com/ads/manage. And instead of looking at reach or impressions, focus on clicks and conversions.

Unless you’re a big brand, you probably don’t care about fuzzy top-of-funnel metrics — go for real ROI. More fans are great, but conversions are better.

As a footnote, we’ve gotten some heat from the PR and sales team at Facebook for pointing out bugs that need to be fixed. To be clear, we think Facebook is doing a great job in providing data and moving quickly. And the faster they can fix bugs in insights, the more confidence brands will have in advertising, which will lead only to more ad revenues.

Facebook should openly embrace these fixes– it makes for a better ecosystem for everyone. But meanwhile, here are some workarounds.

- Dennis Yu

Dennis Yu

About Dennis Yu

Dennis Yu is founder and CEO of BlitzMetrics, a Facebook advertising data platform for brands and local businesses.
This entry was posted in Advertising. Bookmark the permalink.

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>