Testing
Test the canonical API path first. The important gates are key class, activation, job creation, decision shape, consent, and beacons. The advanced SDK should only be tested after the core API path is already green.
Checklist
Minimum validation path
Use test keys
Use sk_test_* and publishable test keys first so you can validate the full route chain without billing traffic.
Exercise no-fill and fill
Do not test only the happy path. Validate both filled decisions and no-fill states for your configured formats and constraints.
Confirm beacons
Check rendered and completion beacons for the formats you actually ship. Billing evidence depends on that path, not just on job creation.
Script Tag
Browser-specific checks
Verify activation against the expected origin, validate consent-required behavior, and confirm that the browser receives only the runtime-safe project config for the active client_id.
Need rollout review?
Start in the dashboard, choose Script Tag or Server API, and use contact only when you need rollout review, enterprise coordination, or non-standard integration help. Billing beacon rules live in the API concepts guide.