Skip to content
All updates

Know when an account needs to be reconnected

Release

From time to time, Facebook or Instagram ends the authorization Post Track uses to collect a page or account, after a password change, a security check, or when you stop managing the page. Until now, collection simply stopped without any warning. Now Post Track notices right away, lets you know, and shows you exactly what to do.

Notice on the Report screen saying an account needs to be reconnected

How you're notified

As soon as the social network rejects the authorization, the person who connected the account and the person in charge of the monitor get an email and an in-app notification explaining why. Until the account is reconnected, a notice stays visible on the monitor's Report and Comments screens, and the account is flagged under Settings -> Integrations.

What to do

On the Integrations screen, the affected account shows what the social network reported and a Reconnect button. In most cases, you just sign in again with Facebook or Instagram and collection picks up where it left off.

Facebook page with the reconnect notice and the Reconnect button

Two cases need an extra step first, and the notice makes it clear which one applies.

  • You're no longer an admin, editor, or moderator of the page (or the page now requires two-factor authentication). Get the role back on Facebook, then reconnect. Signing in again on its own won't restore access to that page.
  • Facebook asked for a security check. Sign in at facebook.com, complete the check, then reconnect.

Deactivated accounts

If you keep a deactivated account only to preserve its history, it's left out of this notice, nothing on screen asks you to act on it and no one gets an email about it. When you reactivate it, Post Track tries to collect again and only lets you know then, if the authorization has really lapsed.

What happens to your data

Nothing is lost. The posts and comments already collected stay available, and Post Track stops trying to sync the account until it's reconnected, so your sync history doesn't fill up with repeated failures. As soon as you reconnect, collection runs normally again.