Documentation

API and Server Endpoints

FourLook exposes server endpoints for click tracking, first-party bridge routing, postbacks, and selected integrations. These endpoints are operational interfaces, not a public open API marketplace.

Primary tracking endpoints

  • /km/{campaign_key} — standard campaign tracking route
  • /gads-click — Google Ads transparent click tracker
  • First-party GGADS uploaded index.php — advertiser-domain bridge that calls FourLook server-to-server

Bridge and conversion endpoints

  • /api/google-first-party-route.php — authenticated bridge routing/logging endpoint used by uploaded GGADS files
  • Postback endpoints — receive conversion events from networks or customer systems

Security notes

  • Bridge endpoints require a per-campaign token.
  • Operational endpoints should not be exposed beyond intended tracking and conversion workflows.
  • Do not publish secrets, tokens, or private credentials in public documentation or destination URLs.

Need more detail?

Return to the documentation hub, review Google Ads transparent tracking, or contact [email protected].