Tracker Playbook
Tracker Playbook
@TrackerPlaybook

Timezone and currency — config before data, not after

Timezone and currency — config before data, not after

Get these wrong and every report, reconciliation, and dayparting decision is quietly off. They're nearly impossible to fix retroactively. Set them at setup.

Timezone checklist:
— Set the tracker's reporting timezone to match your DECISION timezone (where you read reports and run dayparting), and keep it fixed forever.
— Confirm the traffic source and network use the same — or document the offset. A network reporting in UTC while you're in EST shifts conversions across the midnight boundary.
— Disable any auto-DST shift on the tracker if your sources don't observe DST. A one-hour drift twice a year corrupts cohort comparisons.

Currency checklist:
— Set tracker base currency to your accounting currency (what you actually settle in).
— If offers pay in mixed currencies, lock the conversion rate handling: fixed rate vs live FX. Fixed = predictable books; live = accurate but volatile ROI.
— Confirm cost (spend) and revenue (payout) are in the SAME currency before computing ROI. Mixed currency ROI is a meaningless number.

Do this on day one of any new tracker, source, or network. Document the chosen timezone and currency in your account notes.

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

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

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

start

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

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

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