Statuses flow in from partners; conversions flow out to your source and ad platforms.
Two flows meet here. Statuses come in from the advertiser; conversions go out to whoever needs to know — your traffic source and your own ad platforms. They're separate directions, wired independently.
d0pe pulls status on a schedule: it calls the partner's status API over a date range, matches each item to your lead by external id, maps the partner's status onto your internal ones (auto-creating unknown statuses), and on an FTD promotes the lead to a depositor and records the deposit. A failed or unparseable pull touches nothing — the lead keeps its last good status. A durable partner id keeps sync working even if the originating campaign is later deleted.
When a lead reaches an event — registration, rejected, call, deposit (FTD, the main goal), or redeposit — d0pe fires the postback rules that match. Each rule is one event delivered via one adapter with its own config; a single event (say a deposit) can fan out to several adapters at once.
Rules are team-wide (the owner/team-lead global rule) or a buyer's personal override, and the buyer's rule wins for the same event+adapter. Adapter configs hold secrets (CAPI tokens, API keys) and are encrypted at rest; a per-lead log shows every postback fired. Traffic providers are inbound-only — a provider's postbacks are simply the rules of its owner user, shown per provider.