Tracker Playbook
Tracker Playbook
@TrackerPlaybook

Mistake: tracker and network in different timezones

Mistake: tracker and network in different timezones

Failure mode: your tracker runs UTC, the network reports in EST, and you reconcile spend against revenue on misaligned day boundaries. End-of-day numbers never match and you chase phantom discrepancies.

Fix — 4 steps:
— Document the timezone of every system: traffic source, tracker, network, your spreadsheet. Write them down.
— Standardize on one reporting timezone, ideally UTC, and convert everything else to it before reconciling.
— In Keitaro and Voluum, set the workspace timezone explicitly — do not leave it on browser-default, which shifts when you travel.
— When comparing daily revenue to spend, compare 24-hour windows in the same zone, not "today" on two different clocks.
— For cutoff-sensitive offers, note the network's billing-day boundary; conversions near midnight can land on either day.

Verify: pick one day, pull conversions from both systems in the same timezone. Counts must reconcile within retry lag.

Save this SOP. Run this before every launch.
Этот пост опубликован в Telegram-канале Tracker Playbook. Подписаться можно по ссылке: @TrackerPlaybook.
tech

Свежие посты в категории «Tech Infrastructure»

Все каналы категории →

start

Готовы запустить рекламу через сеть public.tg?

Новый оффер, продукт, GEO, кейс, событие или партнёрский запуск — соберём маршрут под задачу и отдадим медиаплан.

Telegram для медиаплана: @AFFtop_connect. Быстрый тест: $20 за канал, $1000 за пакет по сети.