Field asset · two-clock evidence card

One public post. A later Spark Ad. Two clocks.

Use this card to keep creator fulfilment, Spark authorization, ad configuration and the first evidenced delivery interval in their proper order. The figure is a schematic sequence, not an elapsed-time scale.

Fictional teaching example. The handle, post and ad IDs, reserved example.invalid URL, dates and impression count below are invented to show the recording method. They are not an owned Superdirector campaign, a TikTok receipt, or measured performance.

The two-clock sequence

On a narrow screen, scroll the diagram sideways. Every event is also in the text table below.

Evidence lane14 Oct 202615 Oct16 Oct17 Oct18 Oct19–20 Oct25 Oct15 Oct 2027

Clock 1
Creator post

Public by 14:20 UTCFirst reviewer verification of demo post. Exact upload instant unknown.

Bridge
Permission and sync

AuthorizedContent Suite video request accepted; exact post matched.

SyncedAuthorized post moved to Ads Manager.

Expiry shown15 Oct 2027 in this fictional record.

Grant window →

Authorization period shown in the fictional record: 15 Oct 2026 → 15 Oct 2027. This is permission, not a delivery period.

Clock 2
Paid delivery

Ad configured17 Oct, 16:10 UTC. No impression proven.

Planned start18 Oct, 09:00 UTC. A schedule, not evidence of delivery.

Earliest positive row19 Oct 00:00 → 20 Oct 00:00 UTC. A whole day, not an exact first impression.

Planned end25 Oct, 23:59 UTC. Actual last delivery unknown.

Text equivalent: The fictional creator post was first verified public by 14 Oct 2026 at 14:20 UTC. Content Suite authorization was accepted on 15 Oct and the post synced on 16 Oct; the displayed grant expires 15 Oct 2027. The matching ad was configured 17 Oct with a planned 18 Oct 09:00 start. Its earliest available positive ad-level daily row covers 19 Oct 00:00 through 20 Oct 00:00 UTC. The planned end is 25 Oct 23:59. Exact publication, first-impression and last-delivery instants are not evidenced. Visual spacing is schematic.

The text record behind the diagram

This table is deliberately more precise than the drawing. The two CSV files include all fields, including evidence sources, time zones, report granularity and discrepancy notes.

Fictional example record for a creator post and later Spark Ad
Field	Fictional value	What to preserve in a real case
Creator and post	`@fictional_creator`; `DEMO-POST-056`; `https://example.invalid/tiktok/DEMO-POST-056`	Exact account, post ID and URL. The reserved example URL is not a real TikTok post.
Agreed public window	14 Oct 2026, 13:00–15:00 UTC	The creator-confirmed window and its time zone, kept apart from observation.
First verified public	14 Oct, 14:20 UTC	Dated observer capture or platform receipt tied to the post. This means public by the check, not necessarily published at that minute.
Actual publish instant	Not evidenced	Enter only if a reliable receipt provides it; otherwise keep unknown.
Authorization	Content Suite video request accepted 15 Oct, 11:00 UTC; displayed expiry 15 Oct 2027	Route, authorized post, advertiser, accepted time, displayed end and grant evidence. Do not assume another route has this period.
Sync	16 Oct, 16:00 UTC	Receipt that the same authorized post reached the intended Ads Manager account. Sync is not an impression.
Ad identity and configuration	`DEMO-AD-056` matched to `DEMO-POST-056`; configured 17 Oct, 16:10 UTC	Ad account, campaign/ad IDs, exact creative match and dated setup or edit record.
Planned ad flight	18 Oct, 09:00 UTC → 25 Oct, 23:59 UTC	Schedule as configured and ad account time zone. These are intentions, not first or last delivery evidence.
Status observation	Pending / To be delivered on 17 Oct, 16:40 UTC	Status, reason and time. Pending is not delivered.
Earliest available positive delivery row	19 Oct 00:00 → 20 Oct 00:00 UTC; 24 fictional ad-level impressions	Matching ad, positive metric, complete report window, account/report time zone, day granularity and export time.
First and last actual impression	Not evidenced	Do not infer a point from a daily bucket or the scheduled end.
Discrepancy to investigate	Planned start is before the earliest available positive row; earlier delivery is unverified.	Check report coverage, ad status and schedule edits. Preserve both clocks while investigating.

How to use this with a real campaign

Replace every fictional identifier and date with a source-linked record. Keep the raw creator post receipt and ad report with the card.
Record the ad account and report time zone before comparing times. A creator local-time promise and an Ads Manager report day may cross midnight differently.
Use public by for a first public observation, configured for for a planned ad start, and delivery evidenced within for a positive reporting interval.
If the report lacks positive impressions or the matching ad ID, leave paid delivery unresolved. Add a dated correction when evidence arrives; do not overwrite the earlier observation.