Marketing
Organic Social Command
Instagram, Meta, Pinterest, and LinkedIn should resolve into one comparison layer. BigQuery will become the durable truth and Sultan will add sentiment and post-level readback.
Comparison Layer
This is the combined view the team will use when toggling accounts in and out of the social comparison.
Followers
--
Awaiting account data
Reach
--
Awaiting account data
Impressions
--
Awaiting account data
Engagement Rate
--
Awaiting account data
Comments
--
Awaiting account data
Shares
--
Awaiting account data
Saves
--
Awaiting account data
Profile Visits
--
Awaiting account data
Link Clicks
--
Awaiting account data
Sentiment
--
Awaiting account data
BigQuery Social Layer
Every connected account should land into one comparable truth layer before we trust cross-account storytelling.
social_accounts
This is where cross-account comparison, post rollups, and Sultan sentiment should live.
social_post_fact
This is where cross-account comparison, post rollups, and Sultan sentiment should live.
social_comment_fact
This is where cross-account comparison, post rollups, and Sultan sentiment should live.
social_profile_daily_fact
This is where cross-account comparison, post rollups, and Sultan sentiment should live.
social_sentiment_fact
This is where cross-account comparison, post rollups, and Sultan sentiment should live.
Connected Accounts
Operators should be able to include or exclude accounts from the comparison without leaving the dashboard.
Manual assist and member identity
Meta / Instagram
No metrics imported
Instagram Organic
No organic metrics imported
No board analytics imported
Recent Posts + Engagement
This is the post-level readout the team should work from once social data is landed. Sultan sentiment will fill in from comment and caption analysis.
| Account | Post Type | Published | Reach | Engagement | Comments | Saves | Shares | Sentiment |
|---|---|---|---|---|---|---|---|---|
| Awaiting connected post streams | -- | -- | -- | -- | -- | -- | -- | -- |
Social Workflow
Content, publishing, engagement, and reporting should all share the same post identity.
Guardrails
Until the accounts and BigQuery layer are wired, this stays a structured shell instead of pretending to be live truth.