When a public post affects a campaign decision, record its source link, the time you observed it, the relevant context, and the decision it informed. Keep only the content you are permitted to retain, with a named owner and a review date. A disappearing post is a reason to document your reasoning promptly. It does not create permission to keep someone's content indefinitely.
Decide what you need to preserve
Start with a sentence such as: "We need to decide whether the campaign FAQ explains delivery eligibility clearly." That purpose tells you which details matter. A question about delivery wording rarely requires the author's profile photo, follower list or unrelated posting history.
Sprout Social's listening guide connects goals, source selection, queries and action. An evidence record should preserve that connection at the individual-post level. Someone reviewing the decision later should understand why this item mattered and what it could establish.
Use these questions before saving a copy:
- Relevance. What decision could change because of this post?
- Permission. Does the access method and applicable platform agreement allow this capture, storage and proposed sharing?
- Minimum detail. Can a source reference and a short analytical note answer the decision question?
- Expiry. Who will review the record, when, and after which events?
If you cannot answer the permission question, pause the capture and ask your data or privacy owner. Do not move into a private group, borrow another person's access, or search for a deleted copy to bypass a restriction.
For work subject to the UK GDPR, the ICO's principles guide requires a specified purpose, data minimisation, storage limitation and appropriate security. Those principles do not supply a universal retention period for campaign research. The ICO also marks this guidance as under review following the Data (Use and Access) Act. Check the current requirements with your privacy owner when setting policy.
The workflow below is an operational recommendation. Platform terms and applicable law determine what you may retain.
Keep the observation separate from the interpretation
A post asking about shipping can establish that the question appeared in the material you reviewed. It cannot, by itself, establish how many customers share the concern or whether an alleged delivery problem occurred.
Record what was visible before assigning a label. Was the item an original post, a reply or a quotation of another person? Did the parent post change its meaning? Was the displayed time precise, or only a relative label such as "yesterday"?
Keep publication time and capture time in separate fields. Preserve the source's displayed timestamp and timezone where available. If you convert to UTC, record the conversion. If the exact publication time is unavailable, say so rather than inventing precision.
Discovery context matters too. X's Search Posts documentation distinguishes Recent Search, covering the last seven days, from Full-Archive Search with different access requirements. It also documents pagination. A saved query alone does not describe which endpoint, period or result pages you reviewed.
Record those limits without suggesting that your tool captured every relevant conversation. Use the guide to explain listening coverage gaps to stakeholders when the decision report needs a fuller account of missing material.
Evidence-record template
Use one record per relevant item. Store any permitted source capture in a restricted location and link to it from the record. Keep broad campaign reports focused on the finding and action, without copying identifiable material into every deck.
| Field | What to record |
|---|---|
| Record ID and owner | Internal reference and person responsible for review |
| Decision purpose | The campaign question this item can inform |
| Source reference | Platform, permalink and native post ID when available and permitted |
| Publication time | Timestamp as displayed, timezone and any uncertainty |
| Observation time | Capture date and time, including timezone |
| Discovery method | Tool or interface, query, filters, time window and pages reviewed |
| Visible context | Post type, relevant parent context and language |
| Observation | Short factual description of what was visible |
| Interpretation | Proposed theme, uncertainty and reviewer name |
| Retained material | Permitted excerpt or capture location, plus redactions made |
| Access and authority | Who may view it and the policy or permission supporting retention |
| Decision link | Action taken, decision date and responsible team |
| Retention review | Review date, deletion triggers and required handling of copies |
| Current status | Last source check, changes observed and action completed |
A screenshot, when permitted and necessary, should include enough context to prevent a misleading crop. Record any redaction or crop. Do not collect a whole thread because one sentence matters. Conversely, do not remove the sentence that makes clear a complaint was hypothetical or already resolved.
If a displayed engagement count matters, record its label and observation time. Keep it separate from the post's publication time. Do not turn a visible like count into an estimate of unique people persuaded by the post.
Worked example with synthetic material
This hypothetical example contains no real person, post or campaign result.
A public reply asks whether a campaign's delivery offer includes remote areas. The team is considering an FAQ revision. Its evidence record would distinguish these entries:
| Record element | Hypothetical entry |
|---|---|
| Observation | A reply asks which delivery areas qualify for the offer |
| Relevant context | Reply appears under the campaign announcement |
| Interpretation | Eligibility wording may need clarification |
| Uncertainty | The reply does not establish purchase intent or a failed delivery |
| Proposed action | Ask operations to confirm eligibility, then review the FAQ wording |
| Data excluded | Profile photo, unrelated replies and personal biography |
| Review trigger | Review the record after the FAQ decision and on any source-status change |
In a live record, add the actual source reference and timestamps. This synthetic example deliberately has no invented permalink or capture.
If the post disappears, the team can still review its own FAQ decision, provided any remaining record is lawful and permitted. Do not preserve prohibited content by relabelling it as an internal note. A paraphrase can still identify someone or reproduce content subject to platform restrictions.
Before escalating a serious allegation, verify the potential brand issue. The existence of a saved post does not verify its claims.
Review retention when the source changes
A calendar review alone may be too late for a platform obligation. Under the X Developer Policy's content-compliance rules, offline X Content must reflect deletions and modifications on X. Action is required as soon as reasonably possible, or within 24 hours of a request from X or the applicable account owner, with further requirements tied to the agreement and law. The policy also covers changes such as protected status.
That is an X developer-policy rule. Do not copy its deadline into a cross-platform policy without checking each source's terms. Do not assume an internal investigation creates an exception; route a possible preservation-duty conflict to counsel and the platform-agreement owner.
At each scheduled review, and when you receive a removal request or observe a source change, check:
- Does the original decision still require identifiable source material?
- Has the post changed, disappeared or become restricted? Record an access failure as an access failure, not proof of deletion.
- Do the platform agreement, permission and applicable privacy requirements still allow retention and use?
- Can you delete the capture and retain only a permitted, non-identifying decision record?
- Where else did copies go, including exports, presentations and supplier systems?
- Who must update or delete those copies, and how will completion be recorded?
- Does any proposed retention exception need documented legal review?
Assign the record owner before the next relevant post enters your report. Have that person complete the purpose, permitted-material and retention-review fields before anyone distributes a capture.
