You just published a campaign and you want the numbers now. The button exists for exactly that: instead of waiting, it starts the account's sync by hand. This guide explains what the button does, what limits it obeys, and what each of its four answers means.
Refresh
⚠️ Note: Every press sends a full round trip to Meta and therefore spends quota. That is why a refresh runs once every ten minutes; press it before the floor is clear and nothing happens — and you are told so.
How the panel collects its numbers
None of the numbers on the screen come from Meta at that moment; all of them are read from the panel's own archive. The archive is filled by a maintenance run that works in the background every hour. This arrangement has three benefits: opening a screen spends no Meta quota, the section can open before permissions are approved, and past numbers stay with you even if Meta changes them.
The maintenance run's schedule is:
Daily account metrics are refreshed every six hours. Each run re-fetches the last 3 days, because Meta fills in delayed data afterwards.
The first sync backfills 30 days. At most 8 days are fetched per run, so the history on a fresh install completes over a few runs.
Audience demographics are refreshed once a day.
Post metrics are refreshed every 12 hours, at most 12 posts per run.
A day written into the archive is never deleted. So even if you switch the section off for a while, the history is not lost; it simply is not refreshed during that time.
Using the Refresh button
Open My profile › Insights. The button sits to the right of the heading on both the Overview and the Posts tab.
Click Refresh.
The button goes inactive for a moment; the run is in progress.
A notification appears in the corner of the screen. Its text tells you what happened (see below).
If the run really executed, the numbers update on their own — you do not need to reload the page. Your chosen period and sorting stay exactly as they were.
The button on both tabs does the same job; either one refreshes the whole section.
The four result messages
The notification is honest: "refreshed" is only written when Meta was actually contacted.
"Metrics refreshed from Meta." The run executed and the archive was updated. This is the message you will see most often.
"The metrics were refreshed a moment ago." The quota floor is not clear: the last attempt is less than ten minutes old. This is not an error, and there is nothing new to fetch. Try again shortly.
"This account is already being synced." Another sync is running at the same time — either the background maintenance run or a second press. Wait; the numbers update on their own when it finishes.
"The metrics could not be refreshed because the Instagram connection is broken." This one arrives with an error tone because there is something to do: you have to reconnect the account. The archived history stays visible. See The connection dropped.
Why the quota floor exists
The ten-minute floor protects Meta's quota and it is durable: even if the server restarts or your request lands on a different instance, the same account is not synced again. The floor counts from the account's last attempt — if the background maintenance run just passed, a manual refresh has to wait too, because there is nothing new to fetch.
Pressing before the floor is clear produces no error and harms no numbers; it simply does nothing.
Refreshing does not refresh everything
Pressing the button does not re-fetch every metric. Whatever is due within the run gets done:
Daily metrics are refreshed on almost every run.
Demographics are only fetched if 24 hours have passed since the last time.
Post metrics are only fetched if 12 hours have passed, and only for the 12 posts whose turn it is.
So if the audience bars did not change after you pressed Refresh, that is not a fault; the demographics were not due.
When refreshing still does not fill the numbers
Three reasons make a refresh ineffective, and all three sit on Meta's side:
The insights permission is not approved. The run executes but Meta returns no data. A yellow banner sits at the top of the screen, and in this state the panel does not poll the account every 50 minutes; it tries on its normal schedule and starts working by itself the day the permission arrives.
Meta said "slow down" (a rate limit). The rest of the run is skipped and the account is retried on its normal schedule.
Meta's data is not ready yet. Metrics lag by up to 48 hours. Refreshing today will not fill in yesterday's number.
All three are restrictions on Meta's side and they apply to every tool that uses their interface.
A concrete example
A café posts a Reel on Saturday evening and wants to see the numbers on Sunday morning.
At 09:00 they press Refresh: "Metrics refreshed from Meta." The Reel appears in the post list, but with an Awaiting metrics badge beside it.
At 09:02 they press again: "The metrics were refreshed a moment ago." They have to wait for the floor.
At 09:20 they press again: the run executes and the post's first numbers arrive, but reach is lower than expected.
On Monday lunchtime they look at the same post: reach has nearly doubled. The reason is not the refresh but Meta's 48-hour lag finally clearing.
The rule that follows: refreshing skips the queue, it does not skip Meta's lag.
Common mistakes and how to fix them
Pressing repeatedly. The second press does nothing; wait ten minutes.
Expecting a refresh to close the lag. If Meta's data is not ready, refreshing does not create it.
Thinking reloading the page is the same as refreshing. Reloading reads the archive and never contacts Meta. Only the button contacts Meta.
Expecting a refresh on an account with a broken connection. The run never starts; repair the connection first.
Expecting the audience bars to change on every refresh. Demographics refresh once a day.
Assuming a shared link starts a sync for someone else. Refreshing is a button action and is not carried in the address bar; the link you copy starts no run for anyone.
If the section stays completely empty despite refreshing, see The stats look empty or contact our Support team.