Checklist: Where routing logic lives — in the smartlink vs in the tracker

Checklist: Where routing logic lives — in the smartlink vs in the tracker

Logic in the smartlink/router (your own layer):
☐ Full control, custom rules, no per-event cost
☐ You own the latency and the maintenance
☐ Best for complex geo/device/connection logic

Logic in the tracker (Voluum/Keitaro-style rules):
☐ Visual, fast to edit, built-in reporting on every branch
☐ Per-event cost at high volume; vendor-defined rule limits
☐ Best for standard country + device flows

Step — Don't split routing across both layers. Pick one home for the decision, or QA can't trace why a click went where it did.
Step — Keep the tracker in the path for reporting even if routing lives in your router — but make it pass-through, not decision-maker.

Tradeoff: router gives control and cost-efficiency; tracker gives speed-to-edit and reporting out of the box.

Audit for duplicated routing logic across layers each quarter.