Post performance

A post performance facts row holds an observed date, source reference, outcome and the counts used in performance review. The Data Analyst can inspect sessions, conversions, followers, engagement goals and channel exposure against the profile it belongs to. Consent basis travels with the fact, so the team can discuss whether a reading belongs in a particular analysis before using it.

The fact outcome is a review aid. Pending marks work awaiting a decision; Accepted and Rejected distinguish usable observations from those excluded after inspection. These values do not substitute for the profile’s lifecycle status or the independent revision decision. A profile can contain several facts with different outcomes while the owner resolves an issue.

• Source identity. The source reference and observed date help the analyst locate the original reading.
• Measured values. Session and conversion counts sit with follower and engagement values for the same fact.
• Review outcome. Pending, Accepted and Rejected separate fact review from profile publication.

Choose the reporting grain before entering facts. A team might treat each row as one daily observation or one source event; using both conventions in the same channel makes comparison hard. Agree how the consent basis is recorded and who checks it before an outcome becomes Accepted. Define the source reference format so a rejected observation can still be traced without putting unsupported data back into a result.

The owner and analyst should also agree how corrections are handled. If a reading changes after review, record the correction as a separate fact and keep the earlier source reference with the original decision. Decide whether an incomplete count stays Pending while the source system is checked, or becomes Rejected with a reason held in the related review evidence.

Use one social profile with two post facts on different observed dates. Give each a source reference and consent basis. Let the analyst compare the session and conversion counts with a source snapshot covering those dates. Leave a questionable fact Pending while the reviewer checks the supporting material; mark the supported one Accepted. The profile owner can then see why a summary of the property should rely on one observation and wait on the other.

Ask the reviewer to locate both facts from the parent profile. Have them explain which source was checked, which outcome applies and whether the profile revision can proceed. That rehearsal exposes confusing source identifiers and mixed reporting grains early.

• Post Facts Review — Compare observed values and outcomes for each linked profile.
• Pending Post Facts — Focus the analyst and reviewer on source readings awaiting inspection.

Use observation collection to organize source facts and revision review for the decision on the profile revision.