Tygart Media

Tag: Metricool Analytics

  • Metricool Analytics Explained: What the Data Actually Tells You

    Metricool Analytics Explained: What the Data Actually Tells You

    Metricool’s analytics are more useful than most tutorials explain and less comprehensive than enterprise tools offer. Understanding what the data actually means — and what its limitations are — is the difference between using it well and either ignoring it or over-interpreting it.

    What does Metricool analytics measure? Metricool tracks post-level performance data from each connected platform’s API — reach, impressions, engagement (reactions, comments, shares, clicks), and follower changes. It aggregates this data across platforms in a unified dashboard and identifies patterns in your posting history to surface best time to post recommendations. It does not provide audience demographic data, competitive benchmarking, or real-time monitoring beyond what the platform APIs expose.

    Post-Level Metrics: What Each One Means

    Reach: The number of unique accounts that saw the post. Reach is typically lower than impressions because one account can see the same post multiple times. For most content performance purposes, reach is the more meaningful number — it tells you how many people actually encountered the content.

    Impressions: Total number of times the post was displayed, including multiple views by the same account. Impressions are always higher than or equal to reach. High impressions relative to reach suggests the same people are seeing the content repeatedly — useful signal for Instagram and LinkedIn where the algorithm resurfaces content.

    Engagement rate: The percentage of people who saw the post and took an action — liked, commented, shared, or clicked. Engagement rate is the most useful benchmark for content quality. A post with high reach but low engagement rate reached many people who didn’t find it compelling. A post with lower reach but high engagement rate resonated strongly with the audience that saw it.

    Clicks: Number of clicks on links within the post. Relevant for any post that includes a URL. Click data tells you whether the post generated actual traffic, not just passive views.

    The Best Time to Post Feature

    Metricool analyzes your brand’s historical posting data and engagement outcomes to identify which days and times generate the most reach and engagement on each platform. This is derived from your specific account’s data — not industry averages or general social media research.

    For this feature to be meaningful, you need posting history. A new brand with fewer than twenty published posts shows essentially generic recommendations. After two to three months of consistent posting — ideally posting at varied times to generate the comparison data the algorithm needs — the recommendations reflect your actual audience behavior.

    The practical way to use this: post consistently for two to three months without worrying too much about timing, then check the best time recommendations and adjust your scheduling window based on what the data shows. This is more reliable than starting with generic best-time advice that may not reflect your audience.

    Platform-Specific Analytics Quirks

    LinkedIn: LinkedIn’s API throttles analytics data, creating a lag of one to two days between when a post goes live and when accurate performance data appears in Metricool. Don’t evaluate LinkedIn post performance within the first 48 hours — the numbers will be incomplete. LinkedIn also limits the granularity of organic analytics available to third-party tools, so some data points you’d see natively in LinkedIn’s analytics aren’t available through Metricool.

    Facebook: Facebook’s analytics update more quickly and are generally reliable within a few hours of posting. Reach data from Facebook has become less reliable over time as the platform has changed how it reports organic reach, but the relative performance between posts is still useful for content evaluation.

    Google Business Profile: GBP analytics in Metricool show views, actions (calls, direction requests, website clicks), and post-level engagement. GBP analytics are less granular than social platform analytics but provide useful signal about whether GBP posting is driving business actions.

    Instagram: Instagram analytics through Metricool track reach, impressions, and engagement at the post level. Story analytics require additional setup and have more limitations than feed post analytics due to Instagram API restrictions on story data access for third-party tools.

    What Metricool Analytics Can’t Tell You

    Metricool’s analytics don’t provide audience demographic data — age, gender, location breakdowns of who’s engaging with your content. That data is available natively in each platform’s analytics but isn’t surfaced through Metricool. For audience research, native platform analytics are necessary. Metricool analytics also don’t provide competitive benchmarking — how your performance compares to competitors or industry averages. That requires a dedicated analytics platform like Sprout Social or native LinkedIn analytics.

    Want your social scheduling set up properly?

    We set up and run Metricool for multi-brand social operations — the pipeline, the API integration, and the scheduling system that runs on autopilot.

    Tygart Media manages 24 brands in Metricool across LinkedIn, Facebook, Instagram, and Google Business Profile. We know this tool at a level most tutorials don’t reach.

    See the social media setup service →

    Frequently Asked Questions

    How accurate is Metricool’s best time to post data?

    Accuracy depends on posting history. With fewer than twenty posts, the recommendations are generic. With two to three months of consistent posting history across varied times, the recommendations become genuinely predictive of when your specific audience is most likely to engage. The data is derived from your account’s historical performance, not industry benchmarks — which makes it more relevant to your actual audience but requires time to accumulate before it’s meaningful.

    Why does LinkedIn data take so long to appear in Metricool?

    LinkedIn’s API throttles analytics data retrieval for third-party tools, creating a delay of one to two days between post publication and complete analytics data in Metricool. This is a LinkedIn API limitation, not a Metricool issue. The same delay affects all third-party tools that pull LinkedIn analytics via the API. For accurate LinkedIn performance evaluation, wait at least 48 hours after posting before reviewing the data.

    Can Metricool analytics tell me why a post performed well?

    Metricool tells you what happened — reach, engagement, clicks — but not why. Interpreting why requires combining the performance data with your knowledge of the content itself: what topic it covered, what format it used, what call to action it included, what was happening in the world when it posted. The analytics surface the performance; the analysis of causation requires human judgment about what was different about that post.

  • How Metricool Works: The Backend Infrastructure Behind Your Scheduled Posts

    How Metricool Works: The Backend Infrastructure Behind Your Scheduled Posts

    The Machine Room · Under the Hood

    How does Metricool work? Metricool is a social media management and analytics platform that connects to social network APIs (Instagram, LinkedIn, Facebook, TikTok, Pinterest, X/Twitter, and others) via OAuth authentication. When you schedule a post, Metricool stores it in its queue database, manages the publish timing, and fires the post through each network’s native API at the scheduled moment. It also pulls performance analytics back through the same API connections on a recurring basis.

    Here’s a question nobody asks but everybody should: what is actually happening inside Metricool when you schedule a post at 3am for 9am delivery? Not philosophically — technically. Where does that post live? Who fires it? What happens if the API is slow?

    I got curious about this after we started using Metricool as the social publishing layer for ten-plus brands across the Tygart Media network. When you’re operating at that scale, “it just works” stops being a satisfying answer. You want to understand the machinery — especially when something breaks and you need to diagnose it fast.

    So here’s what I know about how Metricool works under the hood, based on API behavior, published documentation, and a few pointed support conversations.

    The Foundation: OAuth API Connections

    Metricool doesn’t have secret back-channel relationships with Instagram or LinkedIn. It connects to every social platform through the same public APIs that any developer can access — it just handles the complexity of OAuth authentication, token management, and rate limiting so you don’t have to.

    When you connect a social account in Metricool, you’re going through a standard OAuth 2.0 flow: Metricool redirects you to the platform (say, LinkedIn), you authorize access, and LinkedIn sends back an access token. Metricool stores that token (encrypted) and uses it for all subsequent API calls on your behalf.

    This is important to understand because it means Metricool’s capabilities are bounded by what each platform allows in its API. If Instagram restricts carousel scheduling via API, Metricool can’t schedule carousels — no matter how much you want them to. The tool is only as capable as the API beneath it. Most of Metricool’s major feature additions over the years have followed platform API expansions, not platform API constraints.

    The Queue: How Scheduled Posts Are Stored and Fired

    When you schedule a post in Metricool, you’re writing a record to Metricool’s database — not to the social platform. The social platform doesn’t know the post exists yet. Metricool’s backend holds the post content, media assets, target account credentials, and publish timestamp in its own infrastructure.

    At the scheduled time, Metricool’s job queue system picks up the pending post and executes the API call. For most platforms, this is a single POST request to the platform’s publishing endpoint with your content, media, and credentials. The platform processes it and either returns a success response (with a post ID) or an error.

    This architecture has a few practical implications:

    • Slight timing variance is normal. Metricool’s queue fires at the scheduled time, but platform API latency means your post might actually appear 30-90 seconds after the scheduled moment. This is normal — it’s not Metricool being slow, it’s the platform processing the request.
    • Media is stored separately. Images and videos you upload to Metricool live in their own media storage (likely S3 or equivalent cloud storage) until the post fires. The API call includes a reference to the media file, not the file itself — the platform fetches it or it gets attached depending on the platform’s API design.
    • Post failures are API failures. If a scheduled post doesn’t go out, the most likely cause is an API error from the platform — expired token, rate limit, content policy violation, or a temporary platform outage. Metricool logs these and (for most errors) sends a failure notification.

    Analytics: How Metricool Pulls Performance Data

    The analytics side of Metricool works differently from publishing. Instead of pushing data out, it’s pulling data in — and it does this on a scheduled basis, not in real-time.

    Metricool connects to each platform’s analytics API (Instagram Insights, LinkedIn Analytics, Facebook Page Insights, etc.) and pulls metrics for your connected accounts at regular intervals. For most metrics, this is every few hours. For historical data, it pulls on demand when you first connect an account or request a date range.

    This is why your Metricool analytics are never truly real-time. The data is always a few hours behind what the platform natively shows — because Metricool is aggregating across multiple platforms and needs to normalize everything into a consistent format. For most use cases, this lag doesn’t matter. For time-sensitive monitoring (like tracking a post that’s going viral), you’ll want to check the native platform app directly.

    The analytics architecture also explains why Metricool’s data sometimes diverges slightly from native platform numbers. Platform APIs occasionally return different numbers than their native dashboards — either due to processing delays, data sampling differences, or definitional differences in how metrics are counted. The gap is usually small and gets corrected over time, but it’s a known characteristic of API-based analytics aggregation.

    Multi-Brand Operations: How the Data Is Isolated

    If you’re managing multiple brands in Metricool (through their Brand account structure), each brand’s credentials, scheduled posts, and analytics data live in separate logical partitions. API tokens for Brand A can’t accidentally fire posts for Brand B. This isolation is fundamental to the platform’s multi-brand architecture.

    In practice, this means the main failure mode in multi-brand Metricool operations isn’t data cross-contamination (that’s well-handled) — it’s credential drift. When a client changes their Instagram password, Facebook access expires, or a social account gets deauthorized, the OAuth token for that specific brand connection breaks silently. Metricool will attempt to publish, the API call will fail with an auth error, and the post won’t go out.

    The workflow fix: build a monthly “credential check” into your operations. Run a test connection for every brand account, catch expired tokens before they cause a missed post, and document the reconnect process for each platform so team members can fix it without escalating.

    What Metricool Does Not Do (That People Assume It Does)

    It doesn’t bypass platform algorithms. Scheduling through Metricool does not give your posts algorithmic preferential treatment. The post fires via API exactly as if you posted it manually — the platform treats them identically for distribution purposes.

    It doesn’t store your content permanently. Media you upload to Metricool for scheduling is typically purged after a defined retention period. If you need a permanent record of your published content, maintain your own content archive — don’t rely on Metricool’s storage as a backup.

    It doesn’t have native access to Instagram DMs or comments. Meta has restricted comment and DM management access in its API for most third-party tools. Metricool’s engagement features are limited by what Meta allows — which at the time of writing is significantly restricted compared to what was available pre-2023.

    It doesn’t guarantee exact posting times during platform outages. If Instagram’s API goes down at 9am while your post is queued, Metricool can’t override that. Most queue systems will retry on API failures — but if a post matters enough that timing is critical, have a manual backup plan.

    Frequently Asked Questions About How Metricool Works

    How does Metricool connect to social media platforms?

    Metricool connects via OAuth 2.0 authentication. When you authorize a social account, the platform issues an access token to Metricool. Metricool stores this token and uses it for all API calls — publishing content, pulling analytics, and checking account status — on your behalf.

    Why does Metricool sometimes post 1-2 minutes late?

    Metricool’s queue fires at the scheduled time, but platform API processing introduces latency. The API call is made on time; the platform’s servers process and publish it within 30-120 seconds depending on load. This is normal behavior for any third-party scheduling tool, not a Metricool-specific issue.

    Why doesn’t Metricool show real-time analytics?

    Metricool pulls analytics from platform APIs on a periodic basis — typically every few hours. Real-time analytics would require continuous API polling, which platforms rate-limit heavily. The data lag is a design constraint driven by platform API restrictions, not a Metricool limitation.

    What happens when a Metricool scheduled post fails?

    If the API call to a social platform returns an error, Metricool logs the failure and sends a notification (email and/or in-app) to the account owner. Common failure causes include expired OAuth tokens, platform rate limits, content policy violations, and platform outages. Metricool may retry depending on the error type.