Export visible performance metrics for owned posts

Why use this

1. Visible post metrics are difficult to compare when captured at different times or mixed with reposts and pinned older material. Missing counts can also be mistaken for zeros, making a creator’s apparent performance depend on how the profile happened to load.

2. This job could create a consistent snapshot for the owner’s subsequent analysis. Keeping capture time, post identity and missing-data labels alongside the figures helps separate a usable observation table from claims about reach, conversion or audience quality that the visible page cannot establish.

Why an agent / simpler alternative

Useful judgment

Recognize post types and normalize differing visible count labels while preserving uncertainty.

Simpler alternative

Use the platform’s own analytics export when it provides the required period and fields.

Unsuitable when

Private audience attributes or metrics not visible to the authorized owner are required.

Proposed inputs

1. Name

   Profile and selection rules

   Owner

   Profile owner

   Minimum scope

   Verified owned profile, date window and treatment of replies/reposts

   Quality check

   Specify whether pinned posts count within the requested sample.

2. Name

   Metric field definitions

   Owner

   Analyst

   Minimum scope

   Visible count names, capture time and missing-value convention

   Quality check

   Distinguish unavailable values from genuine zero counts.

Access and setup — proposed or unknown

Proposed minimum

1. Read the authorized profile and write a snapshot CSV; no engagement actions are included.

Compatibility unknowns

1. Unknown: current page layouts, metric visibility, pagination and runtime access.

External actions requiring approval

1. Signing in, transmitting account data or changing/engaging with posts.

Expected deliverable and review checks

Proposed artifact

Bounded post snapshot CSV with stable links, publication dates, visible metric values, capture timestamp and missing-data notes.

Critical checks

1. Sample membership follows the agreed rules without duplicate pinned entries.

2. Displayed rounded counts remain labelled approximate rather than converted into false precision.

Missing output evidence

This overlay adds no new output inspection or execution validation. Preserve the canonical implementation evidence and its outcome limits.

Failure signals and proposed responses

1. Signal

   A pinned post appears again in the chronological list.

   Why it matters

   Double counting can skew later comparisons.

   Proposed response

   Deduplicate by post identifier while preserving its pinned status.

2. Signal

   A hidden metric is stored as zero.

   Why it matters

   The creator may wrongly conclude that a post received no engagement.

   Proposed response

   Record null with an unavailable reason and exclude it from unsupported calculations.

Effort and cost — unknown

Setup work

1. Define the sample and a consistent metric dictionary.

Ongoing review

1. Review layout changes and refresh snapshots only when needed for the analysis.

Unknowns

1. Unknown: access limits, collection costs and historical metric availability.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

A fictional profile snapshot includes a duplicate pinned post, a rounded count and one hidden reply count.

Acceptance checks

1. Each post appears once.

2. Rounded and missing values retain distinct labels in the CSV.

Stop conditions

1. Private metrics, unauthorized profiles or account changes become necessary.

Limits

1. Visible engagement is a dated snapshot; it does not establish sales impact or complete audience reach.