# Consent & Tracker Regression Monitor — Before / Reject / Accept (`bin_ai_tools/consent-tracker-regression-monitor-before-reject-accept`) Actor

- **URL**: https://apify.com/bin\_ai\_tools/consent-tracker-regression-monitor-before-reject-accept.md
- **Developed by:** [Bin Bin](https://apify.com/bin_ai_tools) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$50.00 / 1,000 completed consent regression scans

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Consent & Tracker Regression Monitor — Before / Reject / Accept

Detect whether a website release changed consent behavior, trackers, third-party domains, or cookies.

### What it does

For every URL, the Actor opens three fresh browser contexts:

1. **Before consent** — load the page and do nothing.
2. **Reject all** — load a clean session and attempt a deterministic Reject/Decline action.
3. **Accept all** — load another clean session and attempt a deterministic Accept/Allow action.

The first completed scan creates a baseline. Later runs compare the new three-state snapshot with the previous completed baseline and return machine-readable regression codes.

### Why this is different from a cookie scanner

A one-time scanner tells you what exists now. This Actor is designed for release QA: **what changed after your site was deployed?**

Typical findings include:

- `TRACKER_ADDED_BEFORE_CONSENT`
- `TRACKER_ADDED_AFTER_REJECT`
- `TRACKER_ADDED_AFTER_ACCEPT`
- `CONSENT_BANNER_DISAPPEARED`
- new/removed third-party domains
- new/removed cookie names/domains

### Input

```json
{
  "urls": ["https://example.com/"]
}
```

Optional advanced controls bound navigation timeout, settle time and the number of recorded network requests.

### Output statuses

- `BASELINE_CREATED` — first completed scan was stored.
- `NO_MATERIAL_CHANGE` — completed scan matches the previous baseline.
- `CHANGES_DETECTED` — one or more technical differences were found.
- `SCAN_FAILED` — at least one of the three isolated states could not be captured; the old baseline is preserved and the URL is not charged.

`ACTION_NOT_FOUND` is not automatically a scan failure. It means no deterministic Accept/Reject control was found on that page/state; the observation is returned as evidence.

### Privacy and scope

This Actor stores cookie metadata only (name/domain/path/security flags), never cookie values. Request URLs are stored without query strings or fragments. It does not read form values or local/session storage.

This is **technical regression evidence, not legal advice**. It does not claim GDPR/CCPA compliance or non-compliance.

### Pricing intent

PPE event: `consent-regression-scan`.

Target launch price: **$0.05 per completed URL scan**, subject to final Apify Cloud cost validation. Failed/incomplete URL scans do not call the PPE event.

### Known MVP limitations

- Deterministic consent button matching; no AI vision fallback.
- Common Accept/Reject wording only.
- Small built-in list of high-frequency commercial trackers; raw third-party domains are always retained even when unclassified.
- No geo/proxy matrix in v0.1.

# Actor input Schema

## `urls` (type: `array`):

Add 1–20 public HTTP/HTTPS URLs. The first completed scan creates a baseline; later scans report changes.

## `waitTimeoutSecs` (type: `integer`):

Maximum time for each isolated consent state to load.

## `settleMs` (type: `integer`):

How long each isolated browser state waits after loading or applying a consent action.

## `maxNetworkRequests` (type: `integer`):

Maximum network requests recorded for each isolated consent state.

## Actor input object example

```json
{
  "urls": [
    "https://example.com/"
  ],
  "waitTimeoutSecs": 20,
  "settleMs": 1000,
  "maxNetworkRequests": 250
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `summary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urls": [
        "https://example.com/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("bin_ai_tools/consent-tracker-regression-monitor-before-reject-accept").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "urls": ["https://example.com/"] }

# Run the Actor and wait for it to finish
run = client.actor("bin_ai_tools/consent-tracker-regression-monitor-before-reject-accept").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urls": [
    "https://example.com/"
  ]
}' |
apify call bin_ai_tools/consent-tracker-regression-monitor-before-reject-accept --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bin_ai_tools/consent-tracker-regression-monitor-before-reject-accept"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/rcYZ7JJikKrLQLGa0/builds/NXG9BtYpeahUBGoEc/openapi.json