Elementor Forms often submit without a full page reload. If Google Consent Mode, GTM triggers, thank-you redirects, and enhanced conversion data are not aligned, Google Ads can miss or misclassify leads.
Use this for Elementor lead forms where Google Ads conversions fire inconsistently, fire before consent is granted, or do not include the first-party data needed for enhanced conversions.
Quick answer
Elementor Forms Consent Mode and Google Ads Conversions should be handled with a narrow evidence-first workflow: map submit behavior, check consent state, fix gtm trigger, then verify the result before making broader changes.
What to check first
- Confirm whether the form uses AJAX success message, redirect, or a custom action.
- Check consent state before the Google Ads conversion tag fires.
- Use a trigger that matches the real Elementor success state, not just a pageview.
- Capture email, phone, form ID, landing page, and click IDs only when privacy rules allow it.
- Test denied, granted, and missing consent states in GTM preview.
Diagnostic table
Use this table to keep the work practical. It connects the symptom to evidence and a verification step.
| Action | Evidence to collect | How to verify |
|---|
| Map submit behavior | Confirm whether the form uses AJAX success message, redirect, or a custom action. | The conversion tag fires once per valid Elementor submission. |
| Check consent state | Check consent state before the Google Ads conversion tag fires. | Denied consent does not send restricted advertising data. |
| Fix GTM trigger | Use a trigger that matches the real Elementor success state, not just a pageview. | Enhanced conversion fields are normalized before hashing. |
| Capture lead fields | Capture email, phone, form ID, landing page, and click IDs only when privacy rules allow it. | Google Ads and GA4 show the same test lead path. |
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
dataLayer.push({
event: 'elementor_form_submit',
form_id: 'consultation_form',
consent_state: 'granted',
lead_id: 'entry_18422',
conversion_action: 'google_ads_lead'
});
Safe fix order
Do the work in a sequence that makes each result easy to prove. Stop if a step produces new evidence that changes the incident scope.
- Map submit behavior
- Check consent state
- Fix GTM trigger
- Capture lead fields
- Test all consent states
Production verification checklist
- The conversion tag fires once per valid Elementor submission.
- Denied consent does not send restricted advertising data.
- Enhanced conversion fields are normalized before hashing.
- Google Ads and GA4 show the same test lead path.
Mistakes to avoid
- Do not judge the fix by one browser or the homepage only.
- Do not delete evidence before recording usernames, file paths, timestamps, and response headers.
- Do not add a cache, security, or tracking plugin while the original problem is still unclear.
- Do not leave test users, temporary debug logs, or broad API keys active after verification.
When HandL WP should help
Bring in help when this affects leads, checkout, search visibility, malware risk, paid media reporting, or a client production site. HandL WP can trace the issue through WordPress, hosting, cache, tracking, and Search Console, then verify the workflow after the technical fix.
If this is active on a production site, fix Elementor Google Ads tracking.
Test consent and conversion requests before the Elementor redirect
Run the Elementor consent update and redirect race test in Tag Assistant when same-tab or new-tab navigation can interrupt or duplicate lead requests.
Helpful references
Verify the consent event order in Tag Assistant
After configuring the banner, run the Elementor Consent Mode v2 Tag Assistant test to compare default and update signals, form conversion timing, cached pages, regions, and returning visits.
Choose and test one consent behavior model
Before changing GTM triggers, use the Elementor basic versus advanced Consent Mode matrix to document defaults, denied requests, granted submissions, enhanced conversion fields, and regional behavior.