Use this guide to put a consent-led AgentPixel tag on a site you control. The tool can generate a snippet; your site must actually publish it before installation can be verified.
Open Connect AgentPixel. Follow the account setup guide if you need a private API key. Use whoami(), setup_status() and list_pixels() before creating a second tag.
Use create_pixel(domain) with the host, not a page URL. For an existing pixel use get_pixel(pixel_id). Use configure_consent(pixel_id, ...) with the actual controller name, HTTPS site privacy-policy URL and applicable purposes. The choices include analytics, resolution, newsletter and named sharing/contact purposes. Do not enable purposes the site will not use. get_policy(pixel_id) lets you review the hosted notice. Changing consent settings creates a policy version, and returning visitors are asked again.
Install the exact returned consent-aware snippet in your site HTML. Run check_install(pixel_id). A successful installation result is evidence of the tag check, not evidence of any consent or identity match. If the check fails, read its issue, update the owning website and retry. Do not mark installation Done just because a snippet was issued.
Review the live site in a browser. Declining identification must not start resolution. Review the notice and accept only when you, as the visitor, want those stated purposes. Then use setup_status() to review setup and the contacts guide for stored results.
30-day trial without a card, then $1 per account/month. Includes 3 pixels and 500 new contacts per UTC calendar month. No extra charges. New resolution pauses when the trial expires until subscribed. At the monthly contact limit, new resolution pauses until the next UTC calendar month; subscribing does not raise this limit.