Revisions

A Revision is an immutable snapshot of a Property's configuration (ad slots, bidders, integrations, and server-side bidding settings), captured at publish time.

How Revisions Work Link to section

Each property uses one of two revision strategies:

1. Automatic (default): Every configuration change immediately publishes a new revision to the edge.
2. Manual: Changes accumulate in the working configuration until you click Create Revision.

Identical configurations are deduplicated by content hash, so republishing an unchanged configuration does not create a new revision. Price floor rules are deployed through their own floors.json pipeline with a separate revision history; the configuration revision only carries the URL of the hosted floors file.

You can tag revisions (e.g. canary) and choose a traffic strategy: latest serves the newest revision, while split routes traffic between chosen revisions. A sandbox revision for testing is also served at /{id}/sandbox/loader.js.

Rollbacks Link to section

To roll back a configuration change, pin a tag to a previously published revision, or use the split traffic strategy to route traffic to an earlier revision. Ads.txt, price floors, and sellers.json revisions each have a direct action to redeploy any previous revision.