Callback
Quick answer
Use callback delivery only when your infrastructure specifically needs decision handoff to a controlled callback endpoint.
The underlying jobs, decisions, consent, and beacons remain the same public API model.
Callback delivery is an advanced server-side pattern. Use it only when you specifically need decision handoff back into your own callback endpoint rather than polling or standard browser-driven reads.
When it fits
When your infrastructure is already organized around callback-based ingestion and you want decisions to arrive at a controlled server boundary.
What it does not change
The canonical concepts stay the same: jobs, decisions, consent, and beacons remain part of the same API model.
Need rollout review?
Start with the Server API. Use contact only when you need rollout review, enterprise coordination, or non-standard integration help.