Hello, I have a problem with the assignment of my source origin. The attribute information source origin 1 is always set up on API even if my user is from direct URL or organic search. The hubspotutk cookie is on my home page, when the user click on the button order, he lands in a landing page located on a sub-domain which also have the hubspotutk cookie. When the user send the form, a contact is well created on hubspot but the origin source are always on API. Is anyone having a solution about that ?
At this point I check HubSpot and I could see contact ID: 13322951 was created. However no data relating to page views or original source was showing. I then opened the console window of the browser and executed the following code:
*abc@gmail.com isn't the actual address I submitted. It's my personal one I wanted to hide from this forum 🙂 Just check for the contact with ID: 13322951
This then correctly associated the cookie to the contact. You will see this if you view the contact in HubSpot. Screenshot below:
Are you using the Contacts API or the Forms API? For example on this page I am using our v3 forms endpoint. On submission the cookie is associated to the contact and the original source accurately reflects the source of the visit. Please see below:
So the issue here is that our Contacts API is designed to be used for "offline contacts". Integrators will typically use this endpoint to create contacts when building integrations between an external CRM and HubSpot for example.
The original source of a contact is determined by the cookie (hutk) that was dropped on the users browser the first time they visit the site and the tracking code fires. The only way it can be associated to a contact record is via a form submission using our API. This is because the Forms API facilitates the passing of the "hs_context" parameter which contains meta data relating to the submission itself.
when the user send the form but it doesn't work, I still have offline source fom API in origin when my contact is created. Do you have any other idea ?
Would you mind sharing the link to page that you've implemented this on so I could take a look and see if I can identify where the issue might reside?
The offline source that is appearing at the moment is definitely due to using the Contacts API but the identify function should indeed associate the cookie and correctly update the original source.
At this point I check HubSpot and I could see contact ID: 13322951 was created. However no data relating to page views or original source was showing. I then opened the console window of the browser and executed the following code:
*abc@gmail.com isn't the actual address I submitted. It's my personal one I wanted to hide from this forum 🙂 Just check for the contact with ID: 13322951
This then correctly associated the cookie to the contact. You will see this if you view the contact in HubSpot. Screenshot below:
I use Google Tag Manager to fire the pixel, I think that I should re-check how it it fires, it should work as I set it up to fires when the form is sent, but I will try another way
My tags didn't fires because the form is in Ajax, the PreventDefault stop the action of the form. The solution is to add some Javascript to your page to communnicate with GTM to tell him that your user is clicking on validate.
I'm not entirely sure what would be causing that. I'm guessing the "Source origin" is the metric on the Google side correct? Originally my understanding was the issue with the "Original source" of the contact in HubSpot.