Importing limited user-provided data
This alert means the uploads include only events that carry both user-provided data, such as email or phone, and a Google identifier such as a GCLID. Leads with user data and no GCLID are being left out. Import every event that has user-provided data, even without a GCLID, standardize the data before hashing, and set up the tag where it is missing.
At a glance
- Where it shows
- The enhanced conversions for leads diagnostics report, which shows this alert.
- What stops
- Leads that have user-provided data but no GCLID never reach Google, so they cannot count.
- How serious
- Moderate. Uploaded conversions still count, but the leads left out of the file give enhanced conversions nothing to match.
What it means
Enhanced conversions for leads match hashed user data, such as email and phone, to ad clicks. The alert says the import is sending only the events that also carry a Google identifier, such as a GCLID, and leaving out the ones that have user data alone.
The page's advice is to import all events that have user-provided data, including events without a GCLID. The user data is what lets Google match those leads, so filtering them out of the file is the cause, not a fix.
What actually triggers it
An import filtered to rows with a GCLID
A file or integration built for plain offline imports, where every row needed a click id, keeps dropping the leads that have none. The alert names that case: events with user data and no Google identifier are missing from the upload.
Leads that arrive without a click id
Calls and forms do not always carry a GCLID. In one real account, most calls from the ads' call button over three months arrived without a Google click id. Leads like these can only be matched by their user data, so they are the ones an import filtered to GCLIDs leaves behind.
Data hashed without standardizing first
The page lists email, phone number, first name, last name and street address as the fields to hash, and country, state, city and zip code as fields not to hash. Before hashing, trim leading and trailing spaces, lowercase the text, format phone numbers to E.164, and remove periods before the domain in gmail.com and googlemail.com addresses.
Fix it in this order
- Open the enhanced conversions for leads diagnostics report and read which events the alert covers.
- Import every event that has user-provided data, including the events without a GCLID.
- Keep the GCLID on every event that has one. The page calls GCLIDs required when no tag collects the user data, and says to import existing GCLIDs even when a tag does.
- Standardize the data before hashing: trim spaces, lowercase the text, format phone numbers to E.164, and remove periods before the domain in gmail.com and googlemail.com addresses.
- Set up enhanced conversions for leads through Google Tag Manager or the Google tag, using the setup guides the alert links to.
Check the report again after the next leads arrive. The page gives no fixed time for the alert to change.
Often confused with
Tag not firing on your website forms
A tag problem, where a form never sends the conversion. This page is about conversions that arrive with too little data, which can happen even when the tag fires.