Skip to main content

Publishing analytics

Publishing Analytics for Multi-Platform Content Teams

Content teams need to know not just whether a post was sent, but how much publishing activity is happening per platform. Wahdx Connection publishing analytics turns publishing requests and provider-item attempts into aggregate metrics: request counts, attempt counts, provider-accepted counts, published counts, failed counts, and skipped counts. Aggregation runs server-side, so the response stays small and accurate as volume grows.

Request-level metrics

See how many publishing requests target each platform and source.

Provider-item metrics

Measure attempts per account and item, including provider acceptance and final publication.

Failure visibility

Track failed and skipped attempts per platform to catch operational issues.

Workflow

How this fits into your publishing operation.

  1. 01

    Call the analytics endpoint

    Use GET /api/analytics/publishing with an optional from and to date range.

  2. 02

    Review aggregate rows

    Use request_count per platform and attempt counts by status to evaluate publishing volume.

  3. 03

    Compare direct and scheduled

    Break down scheduled_post and direct_api sources side by side.

FAQ

Common questions about this workflow.

What is the difference between request_count and attempt_count?

A request can fan out to many accounts and thread items. request_count counts unique requests targeting a platform, while attempt_count counts provider-item attempts.

Does analytics require ledger mode to be enabled?

Yes. The analytics endpoint is available when the publishing ledger is enabled; otherwise it returns 404 and publishing behavior is unchanged.

Can analytics replace status tracking?

No. Analytics summarizes volume and outcomes; status tracking remains the workflow for monitoring individual posts.