Divi Form Field IDs and Mapping to Google Sheets

You can send Divi contact form submissions to Google Sheets in real time with a free WordPress plugin - either the one-click Google Sheets connect (v1.12.0+) or a small Apps Script receiver deployed in your own Google account. No Zapier, no monthly fees, no Google API keys. Divi serves over 1,000,000 customers (Elegant Themes, 2026), yet its native contact form only emails you each submission.

That email-only default is the whole problem. Inbox threads are impossible to sort, filter, or report on, and a single spam-folder mishap can swallow a lead forever. A spreadsheet fixes all of that with sortable columns, timestamps, and shared access for your team.

This guide walks through the full setup: deploying the receiver, picking clean Field IDs in the Divi module, mapping fields correctly, and fixing the classic blank-column bug. It follows the same direct approach as our complete WordPress forms to Google Sheets guide, applied specifically to Divi 4 and Divi 5.

You need four things: a WordPress site running the Divi theme or Divi Builder, a Divi Contact Form module on a published page, a Google account with access to Google Sheets, and the free SheetLink Forms plugin from WordPress.org. Total setup time is about a minute with one-click Google connect, or around ten minutes on the classic Apps Script route.

There is nothing to buy for this workflow. The Sheets path is part of the free core, which covers 12 major form plugins including Divi's Contact Form module - see the form integrations docs for the full list. The setup works the same on Divi 4 and Divi 5, and it has been verified on both.

One practical note before you begin: do the whole setup against a published page you can actually submit from. The Divi builder preview does not fire real submissions the way a live page does, and testing on the real URL removes a whole class of "nothing arrived" confusion later.

The fastest route (v1.12.0+): install the plugin, open SheetLink -> Google Sheets (OAuth), click Connect Google, approve the consent screen, pick or create a sheet in the Google file picker, then create a sync rule with your Divi Form ID and send a test submission. That takes about a minute, with no script to deploy and no URL to paste.

Prefer the classic self-hosted route? It has five short steps: install the plugin, create a sheet, deploy the Apps Script receiver, create a sync rule with your Divi Form ID, and send a test submission. If your Field IDs are already clean, it takes about ten minutes end to end.

1. Install and activate SheetLink Forms from Plugins -> Add New in your WordPress dashboard.
2. Create a Google Sheet and give the tab a clear name like "Leads". Column headers are created automatically on the first delivery, so the sheet can start empty.
3. Deploy the Apps Script receiver: copy the script from the plugin's setup screen into script.google.com, deploy it as a web app, authorize it once when Google prompts you, and paste the web app URL back into WordPress.
4. Create a sync rule: choose Divi as the source and enter your Form ID. Both divi_0 and et_pb_contact_form_0 work; the first Divi form on a page is index 0.
5. Submit a test entry on the live page and watch the row appear in your sheet within a couple of seconds.

Leave the field map empty on the first pass. With an empty map, every field the module captures is auto-synced to its own column, which is the fastest way to confirm the pipeline works end to end before you start customizing.

Fields are captured under the Field ID set in the module - name, email, tel, and so on. Field labels also work as mapping keys once lowercased and hyphenated, so a field labeled "Phone Number" can be mapped as phone-number. If the field map is left empty, every captured field auto-syncs to its own column.

That gives you three levels of control. Empty map: everything flows through automatically, ideal for the first test. Partial map: list only the fields you want, in the exact column order you want. Label-based keys: useful when someone else built the form and you would rather not open the module at all.

On the rule side, the Form ID field accepts both styles Divi exposes: divi_0 and et_pb_contact_form_0 refer to the same first form on a page. Both formats are supported and verified on Divi 4 and Divi 5, so use whichever one you can see in your page's HTML source.

A good habit: once the sheet is live, treat Field IDs as frozen. Renaming an ID later creates a new column for new rows while history stays under the old header.

Blank values almost always mean a key mismatch: the key in your field map does not match the Field ID the module actually uses. Open the module, check each field's Field ID, and make your map keys match those exactly - or clear the map entirely and let auto-sync take over.

The classic trap is copying the input's HTML name attribute, which looks like et_pb_contact_name_0. That string is Divi's internal input name, and it is never the mapping key. The plugin keys on the Field ID (name) or the lowercased-hyphenated label (phone-number), not on the raw input name you see in the page source.

Other quick checks, in order: confirm the Form ID matches the form you are testing (a second form on the page is divi_1, not divi_0), make sure you submitted on the live page rather than the builder preview, and open the delivery log to see what was actually sent.

If a delivery failed in transit rather than mapping wrong, it is not lost. Failed submissions queue automatically and retry with exponential backoff, and you can trigger "Retry Now" manually once the underlying issue is fixed.