Thread Starter
Vye
(@leinteractive)
Sorry to be a pest…we REALLY need to see the source data…is this possible to configure in the plugin?
Hey, Sorry for the delay.
I thought we answered this somewhere else, too… But the HubSpot tracking cookie gets attached to the form submission. I have no control over WHAT aspects of the cookie go with it, so I’ve never been able to see reasons for this not sending the Source Data… Unless you have explicitly told it to not send the HubSpot cookie on the Feed page for this form, then it’ll always send the (full) cookie.
There’s a hook that you can use to review the data before it gets sent, but I do leave certain aspects out of the filter (like the cookie)
add_filter('gf_hubspot_data_outgoing', 'yourFunctionHere');
I also allow override of the PageName and the PageURL in case you don’t like what they are by default, with the filters gf_hubspot_context_url and gf_hubspot_context_name
However, I don’t allow manipulation of the Cookie that gets sent at this time, as that would be too unreliable.
Thread Starter
Vye
(@leinteractive)
Thanks, Chris.
The checkbox on the feed page just allows for multiple contacts to be created from the some device. But, I don’t have that checked.
Where can I see that hook to review the data? Can this be modified or extended?
From what I’ve read in the HubSpot API documents, the source data is NOT sent over by default since it’s not required to make a new form submission.
Thanks.
Hey,
From HubSpot’s Form API: "While the hutk value is not required for the submission to be accepted, this token is used to associate analytics data with a contact record, so without this you will not see any page views or analytics source data for the contact record."
It seems like the hutk (the Hubspot Tracking Cookie) is what ties the form submission with the analytics source data… so as long as that cookie is being sent (which it should be), that should resolve that.
Perhaps doing a <?php var_dump($_COOKIE['hubspotutk']); ?> on a page, to make sure there is indeed something in that cookie?
I am reading over the documentation more to see if I’ve somehow missed something.
Thread Starter
Vye
(@leinteractive)
Thanks, Chris.
From what I understood, the hutk must be specified when passing a form submission in through the API – if not, then the source or pageview data will not come through.
Unfortunately, we don’t have access to the source code on this website, so we can’t do a var_dump, though I can request that the 3rd party who built the site do that for us.
Thanks!
Yup, the HUTK is required for that kind of data, and is included with all form submissions.
I will try to spend some time to confirm this, but that’s how existing functionality has always worked, and was the purpose of the checkbox on the Feed page (some users wanted to be able to disable the cookie from being sent, so analytics would get ignored).
If the cookie was not being sent, then hubspot’s analytics would never notice that the form submission is from an existing user.
Let me know if you have any more questions, but for the sake of functionality and if this is working as expected, I am marking this ticket as resolved.
Thread Starter
Vye
(@leinteractive)
I know it’s working as expected, but it could work much better by also passing along the source information – which it currently is not sending. This would give access to page view history as well.
I’ve asked the dev team who built the site to do a var_dump of the cookie. I’ll post back here if there’s anything important in it.
Thanks.
Thread Starter
Vye
(@leinteractive)
Hi Chris,
We have it working now. Filtered IP addresses won’t show the analytics data, including source and pageview history. Once we tested from a non-filtered IP, that data come over flawlessly.
So yeah…it works great, and as expected. The oversight was on our end!
Thanks.
So glad you figured it out!
I’ll keep that in mind for the next time someone has a similar issue. I also really appreciate you taking the time to update me on this π
-Chris.