WordPress plugin intelligence profile

Tracking for Divi

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

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 6.9
Current version1.1.1
WordPress coverageTested up to WordPress 6.9
Minimum stackWP 5.3 · PHP 7.4
Directory statusactive
Last directory update4 Mar 20268mo ago
Active installations100Adoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records Tracking for Divi version 1.1.1 as active, updated 8mo ago and tested up to WordPress 6.9.

Overview

About this plugin

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:

  • a dataLayer event
  • a Google Analytics 4 event (using gtag.js)
  • a Google Ads conversion (also using gtag.js)

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 not using the standard naming, and the event names, separately for dataLayer and gtag.

Data layer reporting

The structure of the object pushed to the dataLayer is the following, with the default naming:

: Record<string, unknown>, // when "Include all form data" is enabled }

It’s up to you to use or discard the form data.

Google Analytics 4 reporting

The Google Analytics event is sent with flattened parameters:

com", message: "Hello", // additional fields when "Include all form data" is enabled } );

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.

e. the gtag() function is available. Otherwise, you will see a warning in your console like this:

>

Tracking for Divi: gtag event failed, gtag is not defined

Google Ads conversion reporting

The Google Ads conversion is sent like so:

gtag( "event", "conversion", { send_to: "<conversion_id>/<conversion_label>", } );

There is no default for conversion_id and conversion_label as they are always created individually in Google Ads.

e. the gtag() function is available. Otherwise, you will see a warning in your console like this:

>

Tracking for Divi: Google Ads conversion event failed, gtag is not defined

Note: This plugin hasn’t been thoroughly tested with Divi forms that redirect to a success page. g. if Google Tag Manager has a lot of logic and doesn’t trigger the tags in time.

The tags themselves these days use the beacon API (see MDN for reference) so the requests shouldn’t be interrupted as long as they are fired before website unload.

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • tag manager
  • datalayer
  • divi
  • tracking
Compatibility & maintenance

Compatibility & maintenance

Tested up to WordPress 6.9

Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 6.9.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to6.9
Minimum requirementsWordPress 5.3 · PHP 7.4
Update activity4 Mar 20268mo ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

No tracked version or compatibility changes have been recorded by WP PlugIndex yet.

Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.