Connecting X (Twitter)

Connect your X account and its numbers sit right alongside your other platforms, with no separate tab and no separate app to check.

• Connecting your X account lets BrandOps pull your profile numbers (followers, following, and total tweet count) plus tweet-level engagement, alongside your other platforms in Content Analytics.
• It's read-only: the tweet.read, users.read, and offline.access scopes requested at connect time never include posting, DMing, or account-management permissions. BrandOps can't tweet, reply, or change anything on your account.
• Data syncs automatically as part of BrandOps's daily sync at 9 AM IST, alongside every other connected platform.

A standard OAuth flow, with one small but notable security detail.

• Click Connect Twitter / X in Settings → Integrations. The flow uses OAuth 2.0 with PKCE, so no client secret is ever exposed in your browser during the exchange.
• No special account type is required. Any existing X account you can sign into works, unlike Instagram, which needs a Business or Creator account.
• After you approve access, BrandOps stores a long-lived refresh token (granted by the offline.access scope) alongside a short-lived access token, so it doesn't need you to re-approve every couple of hours.
• Once connected, the card shows your handle (@username) and always offers a Reconnect option next to Disconnect, not just when something's expiring, so refreshing your consent is one click any time.

A defined slice of your public profile and recent tweet activity: nothing from your DMs or private lists.

• Profile numbers: followers count, following count, and total tweet count, pulled straight from your public profile.
• Up to 100 of your most recent original tweets for the selected time period (retweets and replies are excluded), each with like, reply, retweet, and quote counts.
• Impressions per tweet, where available. BrandOps requests non-public metrics first (impression count) and falls back to public metrics only if that's not accessible for your app's permission level.
• An average engagement figure: likes plus retweets plus replies, divided by tweet count, calculated across whatever tweets were fetched for the period.

X's access tokens are short-lived by design. Here's how BrandOps keeps the connection alive without bothering you.

• X access tokens are short-lived, about 2 hours by default, and BrandOps refreshes them automatically in the background using the stored refresh token, up to 15 minutes before they'd expire.
• If a refresh ever fails, for example if you revoked BrandOps's access from your X account's connected-apps settings, you'll need to reconnect. Click Reconnect on the Twitter/X card in Settings any time.
• Disconnecting removes your token from BrandOps entirely; reconnecting later starts the OAuth flow fresh and issues a brand-new refresh token.