Enhanced conversions for leads depend on first-party data, click IDs, consent context, and a stable lead record. If WPForms sends only an email notification, the later Google Ads upload may not have enough data to match or prove the conversion.
Use this for WordPress lead generation sites that use WPForms, Google Ads, GTM, CRM stages, offline conversion uploads, or a custom lead-quality workflow.
Quick answer
WPForms Enhanced Conversions for Leads Checklist should be handled with a narrow evidence-first workflow: add hidden fields, store lead id, normalize user data, then verify the result before making broader changes.
What to check first
- Add hidden fields for GCLID, GBRAID, WBRAID, UTM values, landing page, form ID, and consent state.
- Create a lead ID at form submit time and store it in the entry, CRM, and upload queue.
- Normalize user-provided data before hashing it for enhanced conversions when policy allows.
- Send qualified lead events from the CRM, not every raw form submission.
- Keep accepted and rejected upload rows available for audit.
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 |
|---|---|---|
| Add hidden fields | Add hidden fields for GCLID, GBRAID, WBRAID, UTM values, landing page, form ID, and consent state. | A test form entry includes click IDs, landing page, consent state, and lead ID. |
| Store lead ID | Create a lead ID at form submit time and store it in the entry, CRM, and upload queue. | The CRM record keeps the same lead ID as the WordPress entry. |
| Normalize user data | Normalize user-provided data before hashing it for enhanced conversions when policy allows. | Only qualified lead events are uploaded to the high-value conversion action. |
| Map CRM stage | Send qualified lead events from the CRM, not every raw form submission. | Google Ads diagnostics show accepted uploads or clear rejection reasons. |
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
wpforms_hidden_fields:
gclid: {query_var:gclid}
landing_page: {page_url}
consent_state: granted
lead_id: wpforms-{entry_id}
upload_event:
conversion_action: qualified_lead
source: CRM
match_keys: email_hash, phone_hash, gclid
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.
- Add hidden fields
- Store lead ID
- Normalize user data
- Map CRM stage
- Audit uploads
Production verification checklist
- A test form entry includes click IDs, landing page, consent state, and lead ID.
- The CRM record keeps the same lead ID as the WordPress entry.
- Only qualified lead events are uploaded to the high-value conversion action.
- Google Ads diagnostics show accepted uploads or clear rejection reasons.
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, set up WPForms enhanced conversions.