Skip to main content
Post impression analytics has three SDK-facing pieces:
  • Mark a post as viewed when your app decides it was visible enough to count.
  • Read impression and reach from the post model returned by retrieval or query APIs.
  • Query reached users when you need the list of unique viewers for a post.
The SDK exposes impression and reach counters, but it does not expose a ready-made view-rate metric. Calculate product-specific ratios in your app from the counters and audience size that matter to your experience.

Metrics

Platform APIs

Parameters

Mark a Post as Viewed

Call the analytics method from your own visibility logic, such as a post detail screen opening or a feed cell crossing your viewability threshold. Do not call it from every render or rebuild.

Query Reached Users

Use reached-user queries when you need the user list behind the reach count. TypeScript names the ID parameter viewId; iOS, Android, and Flutter name it viewedId.

Notes

  • Keep the unsubscriber, notification token, or stream subscription so you can dispose it when the screen is destroyed.
  • Refresh or re-query the post if your UI needs updated impression and reach values after marking a view.
  • Treat analytics failures as non-blocking; viewing a post should not depend on the analytics event being accepted.
  • Apply your own viewability threshold and debounce rules before calling the SDK method.

Query Posts

Query posts by feed target, post type, review status, or tags

Viewing Content

Render post data and child media safely

Story Impressions

Track story views and query reached users for stories