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

Openmost

DataLayer for GTM and Matomo

Add contextual information to dataLayer for GTM and MTM

Heitor_tito

array.codes

Wp Tracking Codes

The tracking codes in one place. Support: Google Tag Manager, GA 4 Global Tag, Google ADS Remarketing Global Tag,Google Merchant Reviews,Facebook Pixe …

Array é Vida

Datalayer for WooCommerce FREE

The Data Layer is an object that makes available in real time the information that is executed by users while browsing the WooCommerce Store.

sourei

otaviodeveloper

Datalayer For Elementor

Integration between the Elementor Forms and Datalayer

Lee Penney

Digital Data Layer Plugin for WooCommerce

Adds a JavaScript data layer to your WooCommerce installation that conforms to the W3C spec

ashish963

WP Saint

Implements web analytics like a pro. We took care of all your headache. Deploys data layer, Google Analytics, FB pixel & Tag Manager in minutes.

Seresa

inPIPE by Seresa

Generate, store, and decode UTM parameters for enhanced tracking in Google Analytics, Facebook Ads, and other platforms with dataLayer integration.

antoniolite

GTM4Publishers – Smart content tracking for blogs, news sites and magazines

Integrate Google Tag Manager into WordPress and generate an advanced, customizable dataLayer for publishers, blogs, and digital media.

Scripts + Pixels Studio

Scripts + Pixels DataLayer Manager

Automatically detects WordPress context and injects dataLayer variables for analytics tools (GA4/GTM). No coding required.

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.

Alternatives to Tracking for Divi

Top alternatives