These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Social Media Analytics
- Features
- Source evidence
Source evidence
Connect snapshots, observations and verified documents.
OverviewSnapshot Freshness×
Social Media Analytics · Source evidence
New
Snapshot Freshness
Source snapshots
| Name | Captured at | Source system | Coverage start | Coverage end | Freshness status | |
|---|---|---|---|---|---|---|
| Snapshot 256 | 06 Oct | SS-979 | 09 Oct | 11 Oct | Fresh | |
| Snapshot 276 | 23 Oct | SS-386 | 30 Oct | 08 Nov | Stale | |
| Snapshot 725 | 17 Oct | SS-568 | 25 Oct | 28 Oct | Failed | |
| Snapshot 693 | 18 Oct | SS-777 | 21 Oct | 29 Oct | Fresh | |
| Snapshot 583 | 23 Oct | SS-254 | 31 Oct | 02 Nov | Stale |
6 of 6 records
Snapshot 256Source snapshots · SS-95916
FreshCaptured at06 Oct
Source systemSS-979
Coverage start09 Oct
Coverage end11 Oct
What you can do
Explain where a reading came from
Source snapshots record the capture time, source system, coverage dates, record count and freshness state of a measured input. Metric observations connect a metric name and reporting window to both a snapshot and social profile. These links let the Data Analyst answer a practical question: which captured source supports this value for this property and period?
Evidence documents add attachments, external references and verification state for material that needs a person to inspect. The Evidence Coordinator can identify who verified a document and when the underlying document was dated. This is useful when a snapshot is stale, a mapping changes or the reviewer asks for a source receipt before deciding on a profile revision.
How the work is organized
- Capture. A snapshot states its source system, coverage window and freshness state.
- Observation. A metric reading points to the profile and snapshot used for its window.
- Verification. An evidence document keeps a reference, attachment and verifier together.
What to agree during setup
List the source systems that will provide observations and decide how each capture’s coverage window is defined. Agree what Fresh, Stale and Failed mean operationally. The recorded freshness state is a queue signal for people; it should be reviewed with the actual coverage dates and the period the analyst intends to report.
Set a convention for source hashes and external references. They help the team compare captures and locate original files after a later correction. Decide which documents need verification and which person may verify them. The reviewer should be able to distinguish an uploaded document from a checked one when considering a revision.
Check the handoff on an actual case
Capture a source snapshot for a reporting window and attach an observation to it and to a social profile. Enter the metric name, numerator, denominator and value. Then attach a document with an external reference and ask a different person to verify it. Open the observation and trace both links without searching through unrelated properties.
Now mark a second snapshot Stale with a later capture time but a coverage window that misses the reporting period. The analyst should choose the source that actually covers the period and explain the choice to the reviewer. A date alone is not enough; coverage and provenance make the result credible.
What your team sees
- Snapshot Freshness — Review capture sources, coverage windows and freshness states together.
- Observation Windows — Inspect dated metric values with their profile and snapshot links.
Follow the work through
The observation collection process prepares source material. Revision review uses that evidence for an independent decision.
What it keeps track of
Data model- Source snapshots
- Sourced snapshot captures with coverage window and freshness status.
- Metric observations
- Observation-level metric readings tied to a snapshot and source.
- Evidence documents
- Supporting source evidence documents and verification state.
- Social profiles
- Measured web properties with lifecycle status and observed outcome fields.
- People
- Analysts, owners and reviewers belonging to an organization.
- Source mappings
- Reviewed field mappings between source and target definitions.
Who uses it
Permissions- Data Analyst
- , Evidence Coordinator, Independent Reviewer, Analytics Lead
Set up Social Media Analytics your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.