I'm having issues figuring out why the utm custom properties I created aren't being populated. They've been added as hidden fields to our form and I see that the original source drill down fields are being populated. I'm wondering if this could be due to the fact that when a user clicks on a contact us CTA, they are redirected to a separate page where they fill out the form where on this page the utm parameters aren't being carried over?
Correct, if the contacts moves from one page to another, the parameters are lost. If the contact accepted HubSpot cookies, the source information is stored there and HubSpot can determine the source upon form submission, even if the parameters don't show in the URL anymore.
If you want utm parameters to persist between pages, you would have to look into ways to pass these parameters through, e.g. through JavaScript. Using ChatGPT, you can get the steps and code for this laid out pretty neatly for a solution that:
Captures UTM parameters from the URL on page load.
Stores them in localStorage for persistence across pages.
Appends them to internal links so they're carried to the next page .
Best regards
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
Correct, if the contacts moves from one page to another, the parameters are lost. If the contact accepted HubSpot cookies, the source information is stored there and HubSpot can determine the source upon form submission, even if the parameters don't show in the URL anymore.
If you want utm parameters to persist between pages, you would have to look into ways to pass these parameters through, e.g. through JavaScript. Using ChatGPT, you can get the steps and code for this laid out pretty neatly for a solution that:
Captures UTM parameters from the URL on page load.
Stores them in localStorage for persistence across pages.
Appends them to internal links so they're carried to the next page .
Best regards
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer