Targeting Segments

Dry-run Taxonomy Upload

Validates a CSV taxonomy file for the given targeting vendor and returns an impact report (segment counts before/after, diff, affected strategies). Nothing is written to the database — this is a dry-run only.

post/targeting_segments/taxonomy_upload

Request

Request body multipart/form-data

targeting_vendorstring required

Two-character alphanumeric namespace code identifying the targeting vendor (e.g. mm). Must match an existing record in targeting_vendors.

filestring binary required

CSV taxonomy file. Expected columns (header row required): full_path, code, uniques, wholesale_cpm, retail_cpm, buyable, objective. Lines beginning with # are ignored.

Example request

{
  "targeting_vendor": "mm"
}

Response

CSV impact report. The same format is returned by both the dry-run and apply endpoints. Response headers carry the numeric counts; the body is a CSV attachment with two summary blocks followed by an optional affected-strategies table.

Changes

No recorded changes to this operation across all 1 revision of this API.