How Configuration Changes Reach Serving

LtvAdx has no publish step. A change saved in the dashboard or through the API is picked up by the ad server automatically, within about 15 seconds.

The serving snapshot

Every 15 seconds the ad server fetches a snapshot from the control plane: the line items that can actually serve right now (active, in flight, order approved, advertiser approved and funded), approved creatives, live channels, direct-sold campaigns, rates and spend to date. It swaps the snapshot in one step and decides every ad from it. If a fetch fails, the previous snapshot keeps serving.

What that means for you

  • Saving a change is publishing it — there is no draft state and no diff screen.
  • Pausing a line item can still serve it for up to 15 seconds.
  • A newly approved channel or creative starts serving within about 15 seconds.
  • There is no snapshot history or one-click rollback; revert a change by editing it back.

No separate sandbox environment

There is one production environment. To test end to end without real money or real inventory, ask us to mark your test advertiser and test publisher as internal accounts: internal demand only serves on internal inventory, and the reverse. For RTB integration tests there is a sandbox DSP endpoint (see the OpenRTB guide).