Post-level analytics by platform

Post-level analytics help you understand how an individual post performed after publishing. They are useful for comparing hooks, captions, platforms, posting times, formats, and creative choices—especially when you review Analytics Posts or open a published item from Content.

Use post-level views to learn what worked for a specific destination, not only how your account performs in aggregate. Depending on your plan, you may also compare multiple posts, filter by platform, or open a detailed post view with timeline and insights where supported.

1. 1Sign in to Flikly.
2. 2Open Analytics or Content from the navigation.
3. 3Find the post you want to review.
4. 4Open the post details or analytics view where available.
5. 5Review platform-reported metrics and compare them with the post goal.
6. 6Use the results to improve future posts.

In Analytics, open the Posts section to browse grid or table views, filter by platform or date range, and select a post for more detail where available. From Content, open a published post to review status, destination, and any linked performance context your workflow provides.

When you open a post in Analytics or review performance from Content, you may see platform-reported fields such as:

Exact metric names and availability vary by platform.

Post detail views may also show likes, comments, shares, saves, and clicks as separate values when the provider returns them. Some posts include performance scores or comparison tools where your plan supports them.

Platforms define metrics differently. A view, impression, reach count, save, or engagement action can mean different things depending on the provider, content type, and account capabilities.

Use comparisons directionally instead of assuming every platform reports the same way. A strong engagement total on one network may reflect different user behavior than a high impression count on another.

Supported platforms (12 total)

When the same or similar content is posted to multiple connected platforms, compare how each destination performed—but remember Flikly shows platform-reported metrics, not a single unified definition across networks. Consider:

• Hook and first second of video content
• Caption and hashtags
• Aspect ratio and media format
• Posting time and timezone
• Audience fit for each destination
• Platform format (feed, short-form, story, etc.)
• Destination account or profile
• Content type (image, video, carousel, text, etc.)

If you use post comparison in Analytics where available, treat results as a side-by-side view of platform-reported data—not guaranteed cross-platform attribution of which creative element caused a difference.

• Save strong hooks that held attention in the opening seconds.
• Reuse formats and layouts that performed well on a given platform.
• Turn high-performing longer content into more clips with Split clips.
• Adjust captions and calls to action based on comments and engagement patterns.
• Test different posting times when timing data is available.
• Compare platform fit before scaling a campaign to every destination.
• Avoid making major decisions from a single post without more context.

Split longer videos into short clips · Best-time-to-post and AI suggestions

Some platforms may delay reporting or update metrics over time. New posts may not show complete analytics immediately after publishing.

Metrics can change as posts continue receiving activity or as platforms revise reporting. Refreshing Analytics or reopening a post detail view may show updated totals when the provider sends new data.

Post-level analytics can depend on:

• Connected platform and destination account
• Account permissions granted during connection
• Supported metrics from the provider for that content type
• Your Flikly plan and available Analytics features
• Whether the post was published through or tracked by Flikly
• Reporting delays or temporary platform availability issues

Advanced filters, saved filters, post comparison, and detailed timelines may only appear when your account supports them. If metrics are missing, confirm the integration is healthy before assuming the post underperformed.

Platform-specific permissions

Continue with more Analytics & reporting guides.