CDPGuidesSupport

Data Governance

Configure centralized consent rules that stop event dispatch to destinations based on visitor and event properties. Manage the data-governance record, its categories, and their priority order through the Ours Privacy REST API.

Use this page to configure the centralized consent and routing rules that gate every destination.

Where this fits in the dispatch flow

SourceAllowed EventsData GovernanceMappingsDestination

Configuration changes at any stage take effect once you publish a new version.

Data Governance is the second stage that can drop an event. After Allowed Events decides whether an event is permitted at all, Data Governance evaluates the event against each configured category in priority order. If a category's logic evaluates to TRUE for the event, dispatch is stopped to every destination on that category's destinationIds. Events that don't match any category continue to Mappings and then to the destinations they are allowed to reach.

Write category conditions that evaluate TRUE for opt-out scenarios. The category fires when you want dispatch blocked. Common example: a marketing category whose logic is visitor.consent.rejected_categories Contains "advertising" and whose destinationIds list every ad platform.

Discovering valid property paths

condition.property is a bare dotted path into the event/visitor record being evaluated (no {{...}}; that template syntax is for mapping values, not logic conditions). Use GET /rest/v1/mappings/default-variables to list the platform-provided paths: visitor consent (visitor.consent.accepted_categories, visitor.consent.rejected_categories), event fields (event.event, event.distinct_id, event.time), request context (event.request_context.country, event.request_context.city, ...), and identity fields (visitor.email, visitor.first_name, ...). Custom event properties under event.event_properties.* are caller-defined. A path that doesn't resolve evaluates to undefined and the condition won't fire. Typos fail silently.

Consent state is stored as two arrays: accepted_categories and rejected_categories. Use Contains / DoesNotContain against those arrays rather than IsFalsy against a non-existent visitor.consent.marketing.

Account singleton

Each account has at most one data-governance record, so the list returns zero or one entity. Categories and isEnabled change through PATCH on the existing record.

isEnabled: false is the off switch. Categories stay configured but no event is gated. Use this to stage a configuration before going live.

Categories: wholesale replacement and priority renumbering

PATCH /rest/v1/data-governance/{id} follows standard partial-update semantics for name, notes, and isEnabled: only the fields you send are changed.

categories is the exception: when you send it, the entire list is replaced, so send every category the record should keep:

# Read the current state
curl "$BASE/rest/v1/data-governance/$ID" \
  -H "Authorization: Bearer $TOKEN"

# Modify one category and PATCH the full list back
curl -X PATCH "$BASE/rest/v1/data-governance/$ID" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "categories": [
      {
        "name": "Advertising",
        "priority": 1,
        "destinationIds": ["dest_facebook", "dest_google_ads", "dest_tiktok"],
        "logic": {
          "condition": {
            "property": "visitor.consent.rejected_categories",
            "operator": "Contains",
            "value": "advertising"
          }
        }
      },
      {
        "name": "Analytics",
        "priority": 2,
        "destinationIds": ["dest_amplitude", "dest_mixpanel"],
        "logic": {
          "condition": {
            "property": "visitor.consent.rejected_categories",
            "operator": "Contains",
            "value": "analytics"
          }
        }
      }
    ]
  }'

priority is a sort key, not a stored value. On write, the server sorts categories ascending by priority, then re-stamps each one to (sorted index + 1). The persisted priority is always sequential 1..N with no gaps or duplicates. Send any positive numbers; their relative order determines category order.

How destination dispatch sees governance

A destination only receives an event if all of these are true:

  1. An allowed event exists for the inbound event name and lists this destination in destinationIds.
  2. No data-governance category evaluates TRUE for the event with this destination on its destinationIds.
  3. A mapping on the destination matches.

Governance can stop one destination while letting the same event through to another, by listing only the gated destination on the category. That's how the standard "stop ad platforms when the visitor rejects the advertising category, keep analytics platforms" pattern is expressed.

GET/rest/v1/data-governance

GET
/rest/v1/data-governance
AuthorizationBearer <token>

Ours Privacy API key

In: header

Query Parameters

limit?|

Maximum number of items to return. Defaults to 25; values below 1 are clamped to 1 and values above 100 are clamped to 100.

cursor?string

Opaque pagination cursor from pagination.nextCursor in the previous response. Do not decode or modify it. Malformed cursors return 400 Bad Request.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/rest/v1/data-governance"
{  "entities": [    {      "id": "string",      "name": "string",      "kind": "string",      "isEnabled": true,      "createdAt": "string",      "updatedAt": "string",      "notes": "string",      "categories": [        {          "name": "string",          "description": "string",          "priority": 0,          "destinationIds": [            "string"          ],          "logic": {            "AND": [              {                "property1": "string",                "property2": "string"              }            ],            "OR": [              {                "property1": "string",                "property2": "string"              }            ],            "NOT": {              "property1": "string",              "property2": "string"            },            "condition": {              "property": "string",              "operator": "Is",              "value": "string"            }          }        }      ]    }  ],  "pagination": {    "nextCursor": "string",    "hasMore": true  }}

POST/rest/v1/data-governance

POST
/rest/v1/data-governance
*object
AuthorizationBearer <token>

Ours Privacy API key

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/rest/v1/data-governance" \  -H "Content-Type: application/json" \  -d '{}'
{  "id": "string",  "name": "string",  "kind": "string",  "isEnabled": true,  "createdAt": "string",  "updatedAt": "string",  "notes": "string",  "categories": [    {      "name": "string",      "description": "string",      "priority": 0,      "destinationIds": [        "string"      ],      "logic": {        "AND": [          {            "property1": "string",            "property2": "string"          }        ],        "OR": [          {            "property1": "string",            "property2": "string"          }        ],        "NOT": {          "property1": "string",          "property2": "string"        },        "condition": {          "property": "string",          "operator": "Is",          "value": "string"        }      }    }  ]}

GET/rest/v1/data-governance/{id}

GET
/rest/v1/data-governance/{id}
AuthorizationBearer <token>

Ours Privacy API key

In: header

Path Parameters

id*string

Data-governance record UUID from the list or create response.

Formatuuid

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/rest/v1/data-governance/497f6eca-6276-4993-bfeb-53cbbbba6f08"
{  "id": "string",  "name": "string",  "kind": "string",  "isEnabled": true,  "createdAt": "string",  "updatedAt": "string",  "notes": "string",  "categories": [    {      "name": "string",      "description": "string",      "priority": 0,      "destinationIds": [        "string"      ],      "logic": {        "AND": [          {            "property1": "string",            "property2": "string"          }        ],        "OR": [          {            "property1": "string",            "property2": "string"          }        ],        "NOT": {          "property1": "string",          "property2": "string"        },        "condition": {          "property": "string",          "operator": "Is",          "value": "string"        }      }    }  ]}

PATCH/rest/v1/data-governance/{id}

PATCH
/rest/v1/data-governance/{id}
*object
AuthorizationBearer <token>

Ours Privacy API key

In: header

Path Parameters

id*string

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X PATCH "https://example.com/rest/v1/data-governance/string" \  -H "Content-Type: application/json" \  -d '{}'
{  "id": "string",  "name": "string",  "kind": "string",  "isEnabled": true,  "createdAt": "string",  "updatedAt": "string",  "notes": "string",  "categories": [    {      "name": "string",      "description": "string",      "priority": 0,      "destinationIds": [        "string"      ],      "logic": {        "AND": [          {            "property1": "string",            "property2": "string"          }        ],        "OR": [          {            "property1": "string",            "property2": "string"          }        ],        "NOT": {          "property1": "string",          "property2": "string"        },        "condition": {          "property": "string",          "operator": "Is",          "value": "string"        }      }    }  ]}

DELETE/rest/v1/data-governance/{id}

DELETE
/rest/v1/data-governance/{id}
AuthorizationBearer <token>

Ours Privacy API key

In: header

Path Parameters

id*string

Data-governance record UUID from the list or create response.

Formatuuid

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X DELETE "https://example.com/rest/v1/data-governance/497f6eca-6276-4993-bfeb-53cbbbba6f08"
{  "id": "string",  "deleted": true}

How is this guide?