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.

Lee Penney

The W3C have issued a <a href="http://www.w3.org/community/custexpdata/" rel="nofollow ugc">Customer Experience Digital Layer Specification</a> that allows sites to define a JavaScript object to make data accessible to third parties.
This plugin creates that object for an installation of WooCommerce, exposing various pieces of product and cart data to allow integration with third party code (for example, cart abandonment scripts).
It also exposes the logged in user’s name and email address, but only on their machine, so shouldn’t pose a privacy issue.
Tested on WooCommerce version 2.1.9

Digital Data Layer Plugin for WooCommerce

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

Tracking for Divi vs Digital Data Layer Plugin for WooCommerce