Automation framework
Capture structured cookie, network and consent observations during your automated journeys. Map them to the agreed evidence schema.
Integrations · Pre-launch
Connect your automated journey evidence.
Third-party consent automation frameworks currently produce the web evidence ConsentTrace evaluates. Upload the resulting JSON or use a configured API connection; source identity is retained whichever submission method you choose.
Getting started
Generate evidence, then choose a submission route.
JSON upload
Import automation-generated evidence files without an API integration. Manual upload is a submission method, not evidence collection.
API connection
Submit evidence using the agreed schema and a connection scoped to the appropriate properties and environment. The automation source and submission method are recorded separately.
Mobile support, internal customer-configurable AI testing and a manual browser-extension collector are planned. The future extension will generate JSON for download or direct submission to ConsentTrace.
Your testing tools
Connect an evidence collector you control.
Frameworks can be integrated by producing the agreed evidence schema. These names illustrate integration approaches; they are not claims of installed connectors, certification or partnership.
Playwright
Map captured observations to the ConsentTrace evidence schema. Collector and platform coverage must be confirmed during onboarding.
Selenium
Map captured observations to the ConsentTrace evidence schema. Collector and platform coverage must be confirmed during onboarding.
Cypress
Map captured observations to the ConsentTrace evidence schema. Collector and platform coverage must be confirmed during onboarding.
Custom collectors
Map captured observations to the ConsentTrace evidence schema. Collector and platform coverage must be confirmed during onboarding.
Classification governance
Use your approved Technology Inventory.
Organisation-wide classifications
Review observed cookies, requests and scripts against the organisation’s approved categories and patterns. An external catalogue is not a substitute for that review.
Scoped evaluation
Keep findings tied to the property, environment, region, journey and consent selection that produced the evidence.
Results and connected systems
Agree the result-delivery path for your pilot.
Report formats, API access and webhook delivery are confirmed for the agreed scope. A named downstream connector is not included merely because a tool can receive structured results.
Reports and exports
Review findings with evidence references and preserve collector context in supported outputs.
API and webhooks
Discuss result retrieval, authenticated delivery and your consumer’s requirements before activation.
Named connectors
HolisticQA and Jira integration requirements can be discussed separately. Their availability is not promised for early access.
Make evidence actionable