Skip to main content
Adgentek currently supports conversion ingestion through a server-authenticated API. There is no verified public browser pixel to install in Google Tag Manager, Webflow, Framer, or a Custom HTML block.

​
Do not expose API keys

The Conversions API uses an advertiser API key with the capi permission. Never place this key in:
  • browser JavaScript
  • a tag-manager web container
  • a Webflow or Framer code embed
  • client-visible environment variables
  1. Preserve the adgtclid query parameter through your landing and conversion flow.
  2. Trigger your existing analytics or tag-manager event when the conversion occurs.
  3. Send the event to your own backend or server-side tag-manager container.
  4. Have that trusted server call the Conversions API, mapping adgtclid to click_id.
For hosted site builders, use a platform-supported server function, webhook receiver, or automation that can store secrets. If the platform offers only client-side code, it cannot call the Conversions API safely.
This page will include browser-container installation steps only after a production Adgentek pixel artifact is published and verified.