Checklist the per-video bar — engine/sim
79.5/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review thread-field-notes-W30-Sat good|bad)⚠ 6 flag(s) — not yet ship-ready: copy_genericlow_vo_coveragedead_airgeneric_scene · see docs/strategy/VIDEO-CHECKLIST.md
Composition comp · template family · expected output
9:16 Reelrendered1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
expected output: 1/7 rendered — same matrix the /media preview surfaces for this asset.
Composition layer × scene 5 scenes · 25.0s · comp_id + rendered still + tier + the script
| # | Layer (comp_id · still · tier) | Beat | Timecode | Motion | Logo | Audio | VO / on-screen / caption |
|---|---|---|---|---|---|---|---|
| 1 |  matches intent shared field signature-3d | hook | 0–5.0s | kinetic-build | icon·wireframe | ♪ node_lock | Field note. A third of your visitors block your analytics and you never even see them. on-screen: Ad blockers eat your data |
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape boxground blacktreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→Ad blockers eat your data | |||||||
| 2 |  matches intent ChecklistCard template | teach | 5.0–10.0s | kinetic-build | icon·wireframe | ♪ node_lock | The old setup fired GA4 from the browser, where blockers kill it. on-screen: Tag from the server |
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Tag from the servercurate items, nodes | |||||||
| 3 |  matches intent CodeWindow template | diff | 10.0–15.0s | crossfade-8f | icon·wireframe | ♪ node_lock | Stand up a server container and move your most important event behind it. on-screen: Move one event server-side |
expected on screen: black ground · a CodeWindow panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id CodeWindowvisual codeshape boxground blacktreatment wireframemotion crossfade-8fpower morphinstrument morph→Move one event server-sidecurate codeLines, windowTitle | |||||||
| 4 |  first render · fix pending AnnotatedDiagram templatedead_airgeneric_scene | proof | 15.0–20.0s | receipts-count | icon·wireframe | ♪ node_lock | Field Notes |
expected on screen: black ground · a AnnotatedDiagram panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id AnnotatedDiagramvisual receiptsshape boxground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Field Notescurate callouts, statsLabels | |||||||
| 5 |  first render · fix pending shared field signature-3ddead_airgeneric_scene | resolve | 20.0–25.0s | coalescence | icon·liquid-chrome | ♪ bed_out | Field Notes |
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground blacktreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Field Notes | |||||||
Format stack 3 aspects · same scenes[], re-cropped
9:16
1080×1920
Stories · TikTok · YouTube Shorts · Reels
1:1
1080×1080
LinkedIn · Facebook · Instagram
16:9
1920×1080
X/Twitter · YouTube · LinkedIn video
Channels 9 destinations
LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBluesky
Social captions supplemental published copy · per channel (comp_id level)
tiktokField note: about a third of your visitors block your analytics, so you never see them. The old setup fired GA4 from the browser, where blockers kill it. The fix is to stand up a server container and move your most important event behind it. (AI-assisted)
instagramField note.
A third of your visitors block your analytics. You never see them.
The old way: GA4 from the browser. Blockers kill it.
The fix: move one key event server-side.
#analytics #ga4 #thebigtm #data #marketing
linkedinField note: a third of your visitors block your analytics, and you never see them.
Most setups fire GA4 from the browser, which is exactly where ad blockers kill it. You end up making decisions on partial data without knowing it.
The fix, given away: stand up a server-side tagging container and move your single most important event, a purchase or a signup, behind it. You do not have to move everything. Move one event server-side and you stop flying blind on the metric that matters most.
xField note: ~1/3 of your visitors block your analytics, so you never see them. GA4 fired from the browser is where blockers kill it. Fix: move one key event server-side. temerarii.com
facebookField note: about a third of your visitors block your analytics, which means you never see them at all. The old setup fires GA4 from the browser, exactly where blockers stop it. The fix is to stand up a server-side tagging container and move your most important event behind it. Start with one event, like a signup, and go from there.
threadsField note: a third of your visitors block your analytics, and you never even see them.
The old setup fired GA4 from the browser, where blockers kill it.
The fix: stand up a server container and move your most important event behind it. Start with just one.
pinterestAnalytics field note: roughly a third of website visitors block your analytics tracking, so they never show up in your data. Browser-side GA4 is where ad blockers stop it. The fix is server-side tagging: stand up a server container and move your most important event, like a purchase or signup, behind it. Practical GA4 and data accuracy tips.
blueskyField note: ~1/3 of your visitors block your analytics, so you never see them. GA4 fired from the browser is where blockers kill it. Fix: stand up a server container and move one key event server-side.
youtubeTitle: A Third of Your Visitors Are Invisible (Move One Event Server-Side)
Field note: about a third of your visitors block your analytics, so you never see them and you make decisions on partial data. Most setups fire GA4 from the browser, exactly where ad blockers kill it. In this short we give the fix away: stand up a server-side tagging container and move your single most important event, a purchase or a signup, behind it. You do not have to move everything, just the metric that matters most. Topics: GA4, server-side tagging, analytics accuracy, ad blockers.