keegankelly

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:
<ul>
<li>Guided onboarding wizard.</li>
<li>Google OAuth connection to your Google marketing accounts.</li>
<li>One-click Google Tag Manager container injection (head + body snippet) with an admin-exclusion toggle.</li>
<li>Automated audit of your GTM container (tags, triggers, gaps, a tracking health score).</li>
<li>Optional paid audit-apply feature via Paystack.</li>
</ul>
<h4>External Services</h4>
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 (<code>adbot_consent_given</code>) and refuses to contact any external service until the flag is true.
The plugin communicates only with the Adbot Tracking backend service (<code>https://adbot-tracking-platform.vercel.app</code>). The same API will later be served from <code>https://tracking.adbot.co.za</code> 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:
<ul>
<li>Adbot Tracking backend (<code>https://adbot-tracking-platform.vercel.app/api/wp</code>) — the proxy/service your WordPress site talks to. Terms & privacy: https://adbot.co.za</li>
<li>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</li>
<li>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</li>
<li>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</li>
</ul>
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.
<h3>Credits</h3>
<ul>
<li>Adbot brand and logo: © Adbot. Used with permission for the official Adbot plugin.</li>
<li>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.</li>
</ul>

Adbot Tracking Platform

Connect your Google marketing stack in one click. Inject a Google Tag Manager container and audit your tracking setup. Source code and build tools: ht …

Kuba Serafinowski

Ever wanted to track the built-in contact form from Divi? If you tried using Google Tag Manager’s built-in form submit events to do it you probably noticed an inflated number of events flowing.
This is because the form submission event is triggered even if there are form validation errors or the server returns another error.
Since Divi doesn’t provide any JavaScript events to hook into there is no straightforward way to find out if a message has actually been sent.
To get around this, this plugin listens to the network communication that is happening underneath. It’s based on the same mechanism Divi itself uses.
There are three options now:
<ol>
<li>a <a href="https://developers.google.com/tag-platform/tag-manager/datalayer" rel="nofollow ugc">dataLayer</a> event</li>
<li>a <a href="https://support.google.com/analytics/answer/12229021" rel="nofollow ugc">Google Analytics 4 event</a> (using gtag.js)</li>
<li>a <a href="https://support.google.com/google-ads/answer/1722022" rel="nofollow ugc">Google Ads conversion</a> (also using gtag.js)</li>
</ol>
You can use either one of them or event all of them together.
You’ll be able to customize the dataLayer variable if you’re <a href="https://developers.google.com/tag-platform/tag-manager/datalayer#rename_the_data_layer" rel="nofollow ugc">not using the standard naming</a>, and the event names, separately for dataLayer and gtag.
<h4>Data layer reporting</h4>
The structure of the object pushed to the dataLayer is the following, with the default naming:
<pre><code>{
 event: "contact_form_submit",
 formId: string,
 postId: number,
 formData: {
 name: string,
 email: string,
 message: string,
 },
 allFormData?: Record<string, unknown>, // when "Include all form data" is enabled
}
</code></pre>
It’s up to you to use or discard the form data.
<h4>Google Analytics 4 reporting</h4>
The Google Analytics event is sent with flattened parameters:
<pre><code>gtag(
 "event",
 "contact_form_submit",
 {
 form_id: "divi/contact-form-0",
 name: "John",
 email: "john@example.com",
 message: "Hello",
 // additional fields when "Include all form data" is enabled
 }
);
</code></pre>
Form data (name, email, message) is included by default. When “Include all form data” is enabled, all form fields are flattened into the event parameters.
This will only work if you have a <a href="https://support.google.com/google-ads/answer/11994839" rel="nofollow ugc">Google Tag</a> already deployed on the website i.e. the <code>gtag()</code> function is available. Otherwise, you will see a warning in your console like this:
<blockquote>
Tracking for Divi: gtag event failed, gtag is not defined
</blockquote>
<h4>Google Ads conversion reporting</h4>
The Google Ads conversion is sent like so:
<pre><code>gtag(
 "event",
 "conversion",
 {
 send_to: "<conversion_id>/<conversion_label>",
 }
);
</code></pre>
There is no default for <code>conversion_id</code> and <code>conversion_label</code> as they are always created individually in Google Ads.
This will only work if you have a <a href="https://support.google.com/google-ads/answer/11994839" rel="nofollow ugc">Google Tag</a> already deployed on the website i.e. the <code>gtag()</code> function is available. Otherwise, you will see a warning in your console like this:
<blockquote>
Tracking for Divi: Google Ads conversion event failed, gtag is not defined
</blockquote>
Note: This plugin hasn’t been thoroughly tested with Divi forms that redirect to a success page. The tracking works just as well, however the redirect could interrupt the tracking flow e.g. if Google Tag Manager has a lot of logic and doesn’t trigger the tags in time. The tags themselves these days <a href="https://support.google.com/analytics/answer/9964640#event-batching" rel="nofollow ugc">use the beacon API</a> (see <a href="https://developer.mozilla.org/en-US/docs/Web/API/Beacon_API" rel="nofollow ugc">MDN</a> for reference) so the requests shouldn’t be interrupted as long as they are fired before website unload.

Tracking for Divi

Track successful Divi contact form submissions with dataLayer events, Google Analytics, and Google Ads conversions.

Adbot Tracking Platform vs Tracking for Divi