Skip to content

article

Reading Campaign Analytics

Use the Analytics tab to track posts, targets, queue jobs, and completed vs. failed delivery per campaign and per post.

Overview

The Analytics tab is StretchSocial's performance view. Where Insights answers "how healthy is our process," Analytics answers "what happened to our posts" — how many were produced, how many network targets they had, how many publishing jobs ran, and how many completed or failed. It's the tab to open after a launch or at the end of a reporting period.

Read the stat strip

Five cards summarize activity across your workspace:

  1. Posts — tracked content records.
  2. Targets — total network destinations across all posts (a post to three networks contributes three targets).
  3. Queue jobs — total publishing attempts.
  4. Completed — jobs that finished successfully.
  5. Failed — jobs needing attention.

The ratio of Completed to Failed is your delivery health at a glance. A rising Failed count is your cue to open the Queue and read error reasons.

Read the charts

  • Campaign analytics — a bar chart of posts by campaign, so you can see which campaigns you're producing most for. Untagged posts group as Unassigned.
  • Post status — a donut chart of posts by publish status (draft, scheduled, published, and so on), useful for confirming a launch actually moved content to Published.

Read the per-post table

Below the charts, a table lists each post with:

  • Post — title and the most relevant date (published, scheduled, or created).
  • Campaign — the campaign name, or Unassigned.
  • Status — a publish/workflow status chip.
  • Targets — how many networks the post targets.
  • Queue — how many queue jobs it generated.
  • Completed — successful jobs.
  • Failed — jobs needing attention.

Sort your eye down the Failed column to find posts with delivery problems, then jump to the Queue for the specific error.

Concrete example

You just ran a three-network product launch and want a quick report:

  1. Open Analytics. The strip shows Posts: 12, Targets: 30, Queue jobs: 30, Completed: 27, Failed: 3.
  2. The Campaign analytics bar shows most posts under Fall Launch, a few Unassigned — a reminder to tag stragglers.
  3. The per-post table has one launch post with Failed: 1. You open the Queue, find the failed X job, see the error was a disconnected channel, fix the connection, and reschedule.
  4. The Post status donut confirms the rest moved to Published.

Tips

  • Tag every post with a Campaign so campaign analytics are meaningful — untagged posts hide in Unassigned.
  • Compare Targets to Queue jobs: they should track closely, since each target becomes a job.
  • Use the table's Failed column as your triage list after any launch.
  • The Analytics numbers reflect StretchSocial's own records; live provider metrics (reach, likes) arrive once network analytics are connected — see Cross-app scheduling and integrations for how StretchAnalytics folds in.

FAQ

Why do Targets and Queue jobs differ from Posts? One post can target several networks, so it produces several targets and jobs. That's expected.

What counts as Completed? Jobs whose status is complete/completed/published/ok. Failed counts error/failed/blocked jobs.

Where do reach and engagement numbers come from? Not yet from the networks in governed mode — Analytics currently reflects production and delivery activity, with provider metrics arriving as channels go live.

Was this helpful?

Help us improve this article

Use these controls to share whether this answer solved the issue. Feedback helps prioritize updates to StretchSuite Support.