# October launch: illustrative campaign report

FICTIONAL EXAMPLE. No posts were fetched and no credits were spent to create this example.
Post names stand in for the source URLs that a real report includes.

Report time: 4 October 2026, 09:05 UTC
Current collection time: 4 October 2026, 09:00 UTC (available rows)
Baseline collection time: 3 October 2026, 09:00 UTC (available rows)
Scope: 4 unique posts; 4 attempted; 0 skipped; 0 unattempted. Baseline supplied.

| Post | Platform | Status | Views | View change | Likes | Comments / X replies |
|---|---|---|---:|---:|---:|---:|
| Launch video | TikTok | Available | 12,000 | +2,000 | 420 | 32 |
| Product reel | Instagram | Not found | Not returned | No comparable reading | Not returned | Not returned |
| Product walkthrough | YouTube | Available | 8,500 | +500 | 280 | Not returned |
| Launch post | X | Available | 2,400 | -200 | 64 | 8 |

## Decision brief

**Resolve the missing Instagram reading before sending a complete delivery update.**

Three of four posts have current metrics. Two comparable view counts increased; one decreased.

Limit: No campaign targets, conversion data or paid-delivery evidence were supplied.

## Prioritized actions

### Check first: Confirm the reel URL with the campaign owner

Evidence: fictional-tiktok-1, fictional-instagram-2, fictional-youtube-3, fictional-x-4. The lookup returned not found. That does not establish deletion or failed delivery.

Proposed draft (not an observed quote):
> Three of four posts have current metrics. TikTok views rose by 2,000 and YouTube by 500; X fell by 200 between the recorded readings. The Instagram lookup returned not found and needs a link check. These observations do not establish conversions or paid delivery.

1. Confirm that the supplied link is the intended deliverable.
2. Record any corrected URL for an explicitly requested next run.

What to learn: Resolve the missing reading or document the remaining gap in the next update.

Confirm before use: Intended reel URL; Whether any contractual target applies.

### Monitor: Keep the X decrease visible

Evidence: fictional-x-4. Views changed from 2,600 to 2,400 between comparable readings; the cause is unknown.

Proposed draft (not an observed quote):
> X shows a decrease of 200 views between readings. We are preserving that change without attributing a cause.

1. Keep both timestamps and values in the client update.
2. Use the saved snapshot for a later authorized comparison.

What to learn: Check whether a later comparable reading changes the picture; do not infer fraud or campaign impact.

Confirm before use: Preferred time for the next reading.

## Observations and gaps

- TikTok: 12,000 observed views across 1 available post; +2,000 between readings.
- YouTube: 8,500 observed views across 1 available post; +500 between readings. Comments were not returned.
- X: 2,400 observed views across 1 available post; -200 between readings. The reason for the decrease is unknown; platform corrections are possible. The final column shows replies for X.
- Instagram: no current metrics. Not found does not establish deletion, and no delta is calculated.
- Counts are platform-specific observations, not unique reach, conversions or proof of paid delivery. Changes are not attributed to the campaign.

## Illustrative billing

Budget: 20 credits. Estimated maximum: 5 credits using the current catalog.
If each of these four lookups were live and charged at its catalog price, the reported total would be 5 credits, including the not-found result. No unreported charges in this fictional example. Real reports sum the charges returned by the tools.

## Next reading

A real run also produces a JSON snapshot with original URLs, post IDs, metric values, timestamps and charges. Supply that file with the same URLs for a later comparison.

To try this fictional comparison offline, download the [previous snapshot](https://sourcevine.io/skills/campaign-report-baseline.json) and [current snapshot](https://sourcevine.io/skills/campaign-report-snapshot.json). Ask your assistant to compare the supplied files without any API calls. Both files are labeled illustrative and use non-resolving example URLs. Their charge fields illustrate hypothetical historical lookups, not spending during the offline comparison.