Adbot Tracking Platform

Description

Adbot helps you connect and maintain your marketing measurement stack — Google Tag Manager, Google Analytics 4, Google Ads, and Google Search Console — from a single WordPress admin screen.

Features:

  • Guided onboarding wizard.
  • Google OAuth connection to your Google marketing accounts.
  • One-click Google Tag Manager container injection (head + body snippet) with an admin-exclusion toggle.
  • Automated audit of your GTM container (tags, triggers, gaps, a tracking health score).
  • Optional paid audit-apply feature via Paystack.

External Services

This plugin sends data to third-party services to provide its functionality. No external requests are made until you explicitly start the connection flow in the plugin UI. The plugin stores an opt-in flag (adbot_consent_given) and refuses to contact any external service until the flag is true.

The plugin communicates only with the Adbot Tracking backend service (https://adbot-tracking-platform.vercel.app). The same API will later be served from https://tracking.adbot.co.za when DNS is migrated; until then the plugin uses the Vercel deployment URL. The Adbot backend then relays authorized requests to the following services on your behalf:

  • Adbot Tracking backend (https://adbot-tracking-platform.vercel.app/api/wp) — the proxy/service your WordPress site talks to. Terms & privacy: https://adbot.co.za
  • Google OAuth and Google APIs (called server-side by the Adbot backend) — authenticates and accesses the Google services you choose to connect (Tag Manager, Analytics, Ads, Search Console). Terms: https://policies.google.com/terms · Privacy: https://policies.google.com/privacy
  • Supabase (called server-side by the Adbot backend) — stores the account linkage and encrypted OAuth tokens. Terms: https://supabase.com/terms · Privacy: https://supabase.com/privacy
  • Paystack (called server-side by the Adbot backend) — processes payments if you enable the paid audit-apply feature. Terms: https://paystack.com/za/terms · Privacy: https://paystack.com/za/terms?q=/privacy

Data sent from your WordPress site to the Adbot backend: site URL, site name, WordPress version, admin email (when the site first registers with the backend), and — per feature — the Google container you choose, the audit parameters you run, and the payment reference you verify. The WordPress site never sees, stores, or transmits your Google OAuth tokens directly; those live on the Adbot backend and are encrypted at rest.

Credits

  • Adbot brand and logo: © Adbot. Used with permission for the official Adbot plugin.
  • Google product logos (Tag Manager, Google Analytics, Google Ads, Google Search Console) are trademarks of Google LLC. Used for identification purposes in accordance with Google’s brand guidelines.

Installation

  1. Upload the adbot folder to the /wp-content/plugins/ directory, or install the plugin through the WordPress Plugins screen.
  2. Activate the plugin through the ‘Plugins’ screen in WordPress.
  3. Go to the Adbot menu in the WordPress admin.
  4. In the Adbot admin screen, open Settings in the sidebar to review the external-services disclosure. Enable the consent toggle there before connecting, or follow the onboarding wizard / Google connection flow (consent may be recorded when you start a connection).
  5. Complete onboarding to connect Google and install your GTM container when ready.

FAQ

Does this plugin make external requests on activation?

No. Activation only seeds local defaults and sets the consent flag to false. External requests occur only after consent has been granted (via the Settings toggle or when starting a flow that records consent, such as Google connection) and the plugin performs the corresponding action.

Why does the plugin say the site is still registering or “not finished registering”?

Before Google OAuth, the plugin registers your site with the Adbot backend and stores a per-site token. The backend verifies ownership by requesting a public URL on your WordPress site (/wp-json/adbot/v1/verify). Your Settings General Site Address (URL) must therefore be reachable from the internet (for example a live HTTPS domain or an HTTPS tunnel). Installations that only use http://localhost as the site URL generally cannot finish registration because the backend cannot reach that address.

Where are my OAuth tokens stored?

Google OAuth access and refresh tokens are not stored in your WordPress database. They are held and encrypted on the Adbot backend (and associated storage). The plugin only keeps an encrypted site token (used to authenticate API calls to the backend). That site token is encrypted at rest in WordPress using AES-256-GCM with a key derived from your wp-config.php authentication salts (AUTH_KEY, SECURE_AUTH_KEY, LOGGED_IN_KEY, NONCE_KEY). No separate encryption key is required from you for OAuth tokens.

How do I revoke Google access?

Click “Disconnect” on the Adbot Connect tab. This removes the stored account link on the Adbot backend and clears local references. You can also revoke access at https://myaccount.google.com/permissions.

How do I cancel a Paystack payment or get my data removed?

Contact support via https://adbot.co.za. Uninstalling the plugin also removes all local Adbot data from your WordPress site.

Do I need to configure anything?

No. The plugin works out of the box. There are no secrets, API keys, OAuth client IDs, or .env files to set up. All third-party credentials are held by the Adbot backend service; the plugin communicates with that service via a per-site token it mints automatically on first use.

Optional developer overrides

Define either in wp-config.php (both optional):

  • ADBOT_API_BASE — point the plugin at a staging or alternate backend (defaults to https://adbot-tracking-platform.vercel.app/api/wp; omit trailing slash).
  • ADBOT_DEBUG — verbose error logging when WP_DEBUG is on.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“Adbot Tracking Platform” is open source software. The following people have contributed to this plugin.

Contributors

Changelog

1.0.0

  • Initial release.