Hi guys,
We created a Property named it GCLID, and added it to a form as a hidden field, but is not appering to the be working what am I missing?
Many thanks
Hi guys,
We created a Property named it GCLID, and added it to a form as a hidden field, but is not appering to the be working what am I missing?
Many thanks
Hi @DGGoldstein,
How exactly are you testing it? I assume the “GCLID” property has the internal property label “gclid”. If so, the URL you’re accessing when you submit the form would have to contain “gclid=” followed by the value.
Best regards
Hi Karsten, thank you for replying to my question.
It for sure has the label “GCLID” in capitals, not sure if that makes a difference.
I just checked that the UTM was carried over to the page, which according to the header in the network section of Chrome Developer tools it was.
The only thing that I noticed was that the utms are lowercase and the property label is upper, is that what you think the issue is?
Kindest regards,
Darren
Hi @DGGoldstein,
You’re mentioning a utm parameter but HubSpot will only autopopulate a hidden field if the parameter matches exactly the internal label of the field. It must say “gclid=” in the url. Is that the case?
Best regards
Thank you Karsten, so to confirm the UTM contatins “gclid=” so I am assuming based on your last answer I need to change the property label from GCLID to gclid in order for it to work?
Hi @DGGoldstein,
I’m not 100% if capitalization matters but usually HubSpot puts internal property labels into lower case anyway.
Still, I’d recommend checking what the internal property label is. Navigate to the property settings, open the GCLID property, then click on the </> to see the internal label.
Next, I’d recommend creating another form, for testing, where the soon-to-be hidden GCLID field is not hidden. To the form URL, append a ?gclid=loremipsum and check if the field populates.
If it does, check whether it also works as a hidden field.
If it does, check the same thing on your other form. If it doesn’t, something’s wrong about the form.
Lastly, use an actual live parameter and see if the entire thing works.
The error is very likely somewhere in between these steps.
Best regards!
Hi Karsten,
I tried it on a test form, both visible and hidden, as you suggested, and the ones I tested worked.
I will see if the same works when the live traffic comes in.
Thank you again ![]()