Understand Social analytics and sync status | Noticestry One

Understand Social analytics and sync status

Social → Analytics reports Social activity from synchronized provider metrics in Noticestry One. It is separate from email Reports and paid-ad reporting.

Choose your view

  1. Confirm the workspace and open Analytics under Social.
  2. Select the intended Platform and Source filters.
  3. Review the From and To dates.
  4. Choose the metric that should drive the trend, heatmap, and ranking.
  5. Use Refresh metrics when you need an updated provider synchronization, then read the resulting status or error.

Source labels can include Relay, Provider, and External. “Relay” is a legacy label for app-originated content; it does not indicate that you are using a different product.

Social analytics filters for platform, source, dates, and metric view

Choose the platform, source, date range, and metrics before comparing Social results.

Understand the metrics

  • Impressions: recorded displays of content, including repeat displays.
  • Reach: the provider's reported reached audience for the available scope.
  • Engagements: recorded interactions according to the provider's definition.
  • Likes, Comments, Shares, Clicks, and Views: the available individual interaction or viewing measures.
  • Engagement rate: the rate supplied or calculated for the metric scope shown; compare equivalent scopes.

Definitions and availability differ across platforms. Adding reach across posts or platforms does not establish a deduplicated count of people. A provider may not expose every metric for every content type.

Check freshness

The Social Dashboard shows Social sync status and Last successful sync. Check that timestamp alongside analytics refresh status. A synchronized connection and a fresh metric result are related but different signals.

Read any partial-sync or account failure message. Existing mirrored data can remain visible while a refresh fails. A blank, unavailable metric, or error is not the same as a confirmed zero.

Investigate differences

Compare the same account, date range, post, and metric in Noticestry One and the native provider. Check source filters and refresh timing before assuming a discrepancy. Imported history or externally created posts can have different coverage.

If a result remains missing, share the workspace, platform, post, selected filters, last successful sync, and error with support. Do not treat likes, views, or provider acceptance as proof of sales or completed delivery.