Use normalized social analytics
Compare impressions, reach, views, clicks, reactions, comments, shares, saves, followers, and watch time carefully.
App9 Post maps available provider metrics into a common analytics shape. Unsupported metrics are null, definitions remain provider-dependent, and account or post context must stay visible when comparing performance.
What this means in practice
App9 Post maps available provider metrics into a common analytics shape. Unsupported metrics are null, definitions remain provider-dependent, and account or post context must stay visible when comparing performance.
Use the documented brand and account boundaries consistently across the scheduler, REST API, SDK, MCP tools, SSE consumers, and webhooks. That makes the same social operation explainable to an operator and reproducible by an integration.
Implementation checklist
Fetch brand summary metrics for dashboards and post analytics for target-level detail.
Preserve null, zero, and not-yet-synced as three different states.
Display metric definitions and capture time near comparisons.
Compare like placements and time windows when ranking content.
Retain provider links for investigation of discrepancies.
Example request
This example uses a server-side API key and an explicit brand selection. Replace placeholder values and keep credentials out of browser bundles, client logs, and source control.
curl --request GET \
--url 'https://postapi.app9.co/v1/analytics/summary' \
--header 'Authorization: Bearer APP9_POST_API_KEY' \
--header 'X-App9-Post-Brand: BRAND_ID'Operational details
Normalized field names do not make provider measurement methodologies identical.
Analytics snapshots allow trend views without rewriting historical observations.
Some metrics become available hours or days after publication.
Common mistakes to avoid
- Do not sum reach across providers and call it unique people.
- Do not replace unavailable data with zero.
- Do not promise realtime analytics when the provider refresh cadence is delayed.