How to keep video platforms data from changing on you

A dashboard is not a record. It is a rendering of whatever the service currently believes, in whatever definitions it currently uses, for whatever period it currently keeps. All three can change without notice, and when they do, your history changes with them.

The fix is not a better dashboard. It is a small habit: pull video platforms data out on a schedule, keep the raw files, and never analyze anything you have not stamped with a date and a definition.

What to take away

Where the differences come from

Before building a pipeline, know what it is defending against. These are the ordinary reasons two honest reports of the same period disagree:

Most unexplained analytics mysteries come down to one of those causes. Working through them in order is faster than theorizing about audience behavior, and it stops you explaining a time zone as a change in taste.

Time zones deserve their own paragraph

Every report has a day boundary and it is rarely the one you assume. YouTube Studio, TikTok Analytics, and Meta Business Suite each cut the day in their own place, and it is not always yours to set. Meanwhile viewers are spread across every zone there is.

Two rules make this manageable. Never compare periods shorter than a week across two different sources, because a day boundary difference can be larger than the effect you are looking at. And record the time zone in the file name, not in your memory.

Dashboard, export, and interface: three different products

Services usually offer several routes to the same numbers, and they do not always agree.

The dashboard is fast, opinionated, and rebuilt periodically. Metrics get renamed, charts get replaced, and history sometimes gets shortened. YouTube Studio, TikTok Analytics, and Meta Business Suite are all built this way.

The manual export is what most people should use. It is a file, it can be kept, and it is usually more detailed than the chart it came from. YouTube Studio, TikTok Analytics, and Meta Business Suite each hand you a CSV to download.

The programmatic interface is the most stable of the three, because other people's software breaks when it changes, so changes are announced in advance. If you are pulling regularly and can manage the setup, this is the one that will still work next year. On YouTube that is the YouTube Analytics API, on TikTok the Business API, and on Meta the Graph API. Each carries its own quotas and its own version history, and those are the two things to read before you build on it.

Whichever you use, take the same one every time. Mixing routes introduces differences you will later mistake for real movement.

A pipeline small enough to actually run

The failure mode here is building something elaborate in week one and abandoning it in week five. The version below takes a few minutes a week.

1. Pull on a schedule. Pick a day, pick a period, and take the same route to the numbers every time. Weekly suits most channels, daily while a campaign is running, and quarterly if you publish only occasionally.

If you would rather not script the pull yourself, the connectors people use for this are Supermetrics, Fivetran, and Stitch, landing the files in a warehouse such as BigQuery; Looker Studio reads from there. A script against the platform's own API does the same job with no vendor in the middle.

Name the file as a pattern — platform-metric-period-timezone-pulldate.csv — so a YouTube Studio monthly view pull becomes something like youtube-studio_views_month_tz_pulldate.csv. CSV is the format these exports arrive in, and JSON is what the APIs return. Open the file read-only; sorting or cleaning it in place is the same as editing the record.

That is the whole system. It is worth the effort because it converts a rented view of your own activity into a record you hold, which is the same principle that governs keeping a platform record in general.

The one number that is comparable across services

Almost nothing in a platform dashboard can be compared with the equivalent in another platform's dashboard, for reasons set out in the notes on what a view actually counts. There is one exception worth building on.

Anything that lands somewhere you control is measured by you, with one definition, in one time zone, on both sides. Clicks to your own destination, sign-ups, replies to an address you own: these are smaller numbers than any platform metric and they mean the same thing everywhere.

If you need to know which of two services is doing more for you, this is the only honest comparison available. It is also why the video platforms overview treats a route to the audience as the decisive structural question.

Demographic splits are estimates wearing a table

Audience breakdowns by age, country, or device are modeled from signals like self-reported birthdays and network location, then aggregated and often suppressed below a threshold. YouTube Studio, TikTok Analytics, and Meta Business Suite all withhold a row when the group behind it is too small, and each service sets that minimum itself. They are usually fine as a rough shape and dangerous as a precise claim.

Treat a split as a hypothesis to check against something independent. If a country stands out in your dashboard, look for a matching signal in your own destination's traffic, then see whether the two agree.

Where they do not, believe neither until you know why. Read why adoption differs by country before assuming a cultural explanation.

Common questions

How long should I keep raw pulls?

Indefinitely. They are small text files and they are the only evidence you will have of what a service reported before it changed. The cost is trivial and the moment you need them is exactly the moment you cannot recreate them.

The service already keeps my history. Why duplicate it?

Because what it keeps is subject to its retention window, its current definitions, and its current interface. A service can shorten a reporting window, retire a metric, or restate a period, and none of those is a fault. It just means the history you can see is theirs, not yours.

My export does not match my dashboard. Which is right?

Check the period boundaries and the time zone before anything else, because that explains most cases. If they still differ, look for a filtering delay by re-pulling the same period a week later. Persistent unexplained differences are worth a support question, and worth recording either way.

Should I be tracking this at all if I publish occasionally?

A quarterly pull answers longer-horizon questions, such as whether older work still earns attention. The record's value is not weekly optimization but showing slow change no single week reveals.

Slow changes are worth knowing because they tend to be structural, not incidental, as the constraints described year by year reshaped the format itself.