Skip to developer documentation
Browse developer documentation
API documentation / Browser tracking

Browser tracking

Check a visitor tracking country

Country-aware trackers check whether measurement is allowed before starting. A positive result does not provide visitor consent.

GET/api/v1/tracking-policy

Access: Public · no authentication · Permission details

Query parameters

Query parameters
FieldTypeDescription
siteIdRequiredstringPublic website ID. No visitor identifier is accepted.

Request examples

Examples run from your server or terminal. Configure ATTRIBOO_TOKEN privately for authenticated requests. Replace example website IDs and values with your own. The examples make real requests when you run them.

cURL request
curl "https://www.attriboo.com/api/v1/tracking-policy?siteId=site_example"

Response

Illustrative response. This endpoint returns raw JSON. Optional coverage, notes and continuation fields vary by report.

Response fields
FieldTypeDescription
allowedbooleanWhether this request may proceed to the installation’s separate consent checks.
JSON response
{
  "allowed": false
}

Behavior and limits

The response is private/no-store and includes no country, IP, browser identifier or page path. Use the shipped SDKs with data-country-control=true rather than building a cached decision.

A saved nonempty country list blocks selected and unknown locations. An empty list preserves prior collection. A failed check keeps country-aware code off. The endpoint creates no visitor analytics record; hosting still receives request metadata.

A supplied browser Origin must match the website or its subdomain. Country controls do not stop payment imports, erase history, grant consent or establish legal compliance.

HTTP statusMeaning
400Missing or invalid siteId.
403A supplied Origin does not match the website.
404Unknown website.
503Country policy could not be checked; measurement stays off.