Publish the site's tag draft as the next version (site_tags.publish)

POST 
/api/integrations/website/sites/:site/tags/publish

The draft at revision becomes version N+1 and goes live: on a mode-A site whose plan has the tag manager, visitors get it on their next page (the config answer carries the version). Every vendor the version names joins the cookie banner; a vendor new to the banner is a material change, so the banner version goes up and every visitor is asked again (published.banner_bumped). 409 for a stale revision, 422 when the draft equals the live version. Audit row website.tags_published.

Request

Responses

200

The site's tags, with the version just published.

403

Authenticated but not allowed.

404

Resource not found (or not visible to the current tenant).

409

The request conflicts with the current state of the resource.

422

The request failed validation.