# Ketch manages consent signals. Lokker confirms they reach the network layer.

Ketch takes a code-first approach to consent management, connecting consent decisions to data flows through APIs and tag orchestration. That sophistication introduces complexity: each integration point between Ketch and a third-party tag is a place where a misconfiguration can let data flow through unchecked.

## Ketch

Ketch is a programmatic privacy and consent platform that manages consent signals, data rights requests, and vendor controls through a developer-friendly API and tag orchestration layer.

## Programmatic consent creates programmatic risk

The more code-driven the consent architecture, the more ways there are for integration errors to go undetected until something breaks in production.

### Integration mismatches between Ketch and third-party tags

Each third-party tag that relies on Ketch signals for its firing condition needs to be tested end-to-end. API-level configuration does not guarantee tag-level behavior.

### Consent signal timing

If Ketch signals are not available at the moment a tag container fires, a tag may use a fallback or a prior state. This is especially common with tags loaded eagerly by a tag manager.

### Version and environment drift

Development and staging environments often have different Ketch configurations than production. Drift between environments creates a gap between what was tested and what visitors experience.

## API-level consent configuration needs browser-level confirmation

Ketch processes consent decisions at the API layer. What matters from a compliance perspective is what the browser actually does with those signals: which scripts fire, which cookies are set, and which requests leave the site.

- Each vendor in the Ketch vendor list needs to be tested individually in reject state to confirm its tag actually stops.
- GPC signal handling should be validated alongside the explicit consent flows, not treated as equivalent.
- Data Subject Rights requests managed by Ketch operate at the data layer; the consent state at collection time is a separate validation point.

## Multi-jurisdiction consent requires jurisdiction-specific testing

Ketch is designed to handle multiple regional consent frameworks simultaneously. That strength depends on each geo-rule being configured correctly and tested independently. A US visitor seeing the California opt-out path, which under the CPRA must cover both sale and sharing for cross-context behavioral advertising including GPC recognition, and a European visitor seeing the GDPR opt-in path should each be validated as distinct flows.

## How Lokker validates Ketch-managed consent

Lokker runs browser-level consent flows and inspects the network, giving you evidence that Ketch signals are reaching the tags and producing the right behavior in each consent state.

### Multi-state consent testing

Consent Validator simulates each consent state and compares what the network shows, producing P1-P3 remediation priorities for any gaps between Ketch configuration and network behavior.

### Portfolio-wide consent monitoring

Privacy Edge maintains a continuous scan of your properties so consent drift from code changes is caught between audit cycles.

## Products that address Ketch privacy risk

Each product links to its full details so you can explore features, view a demo, and understand how it applies to your Ketch deployment.

### Consent Validator

Validates Ketch-managed consent states at the network layer, not just the API layer.

### Privacy Edge

Monitors the full property portfolio for consent and tracker drift on a regular cadence.