Installing the tracking code on our landing page worked perfectly, and we are able to track user statistics.
We use Cookiebot as our consent management tool. The scripts are found and enabled/disabled correctly.
We have one problem. After running a Cookiebot scan report, there is an issue because HubSpot does not seem to provide information about the country where the data is sent.
Example:
Cookie Name: __cf_bm
Provider: hubspot.com
...
Data is sent to: Unknown (not adequate)
Is there a way to get this information, or do I have to activate something in the settings?
These would actually be HubSpot cookies, there's more info on these here.
If you need to know specifically where your data is going, there's a great guide on this here.
If you need this information added to the cookies though that's not possible at the moment but would be worth checking in with HS support to see if it's something they could consider adding in!
Tom Mahon Technical Consultant | Solutions Engineer | Community Champion Baskey Digitial
Dez 12, 20245:37 AM - bearbeitet Dez 12, 20245:38 AM
Mitglied
Tracking Scripts Unknown country (not adequate)
lösung
I contacted support, and the response at the end was:
"Those that start with 'cf' are set by our subprocessor Cloudflare. While it is not possible to say exactly where the data goes, according to the information provided by Cloudflare, it is always sent to the nearest server location. For example, when a visitor accesses the website from a location in the EU, the data is most likely sent to a server in the EU."
Regarding HubSpot scripts:
"The other cookies contain a 'eu1' in the URL, which is unique to the HubSpot server in the EU. While Cookiebot was not able to determine where the data goes, this URL provides the relevant information. Our server in the USA cannot process URLs containing this 'eu1' part, and therefore it is guaranteed that the data goes to the server in the EU (near Frankfurt) or the backup server near Dublin (in case the main server is offline)."
The conclusion was that the information is not sent automatically, but we have to "trust" their explanation about the locations.
We decided to wait and see if the scripts get blocked.
Hey @fabianhohly This is actually a cloudflare cookie. HubSpot uses cloudflare as it's content delivery network. It seems cloudflare uses this as bot protection. You wouldn't be able to change anything on this on your end from what I can see. It might be worth raising a ticket with HubSpot support on this to see if their contacts at cloudflare can resolve this as if it's critical it would need to be updated.
Tom Mahon Technical Consultant | Solutions Engineer | Community Champion Baskey Digitial
Cookie purpose description: Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes.
Data is sent to: Unknown (not adequate)
Cookie Name: __ptq.gif
Cookie purpose description: Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels.
These would actually be HubSpot cookies, there's more info on these here.
If you need to know specifically where your data is going, there's a great guide on this here.
If you need this information added to the cookies though that's not possible at the moment but would be worth checking in with HS support to see if it's something they could consider adding in!
Tom Mahon Technical Consultant | Solutions Engineer | Community Champion Baskey Digitial
I contacted support, and the response at the end was:
"Those that start with 'cf' are set by our subprocessor Cloudflare. While it is not possible to say exactly where the data goes, according to the information provided by Cloudflare, it is always sent to the nearest server location. For example, when a visitor accesses the website from a location in the EU, the data is most likely sent to a server in the EU."
Regarding HubSpot scripts:
"The other cookies contain a 'eu1' in the URL, which is unique to the HubSpot server in the EU. While Cookiebot was not able to determine where the data goes, this URL provides the relevant information. Our server in the USA cannot process URLs containing this 'eu1' part, and therefore it is guaranteed that the data goes to the server in the EU (near Frankfurt) or the backup server near Dublin (in case the main server is offline)."
The conclusion was that the information is not sent automatically, but we have to "trust" their explanation about the locations.
We decided to wait and see if the scripts get blocked.
Spending some more time on this today.....the explanation above states the Hubspot cookies "contain a 'eu1' in the URL". Forgive my ignorance, but can someone explain how to examine this on the web pages in my domain being flagged by Cookiebot?
If I go into Chrome's Developer tools, I can inspect them under the Application settings, but I do not see anything giving me the full URL.
How can I examine these?
RELATED QUESTION - is the "eu1" in the URL set based on the visitor's IP address or tied in any way to where I asked Hubspot to host my data (US vs EU)
Really wish I could stop these warnings in Cookiebot each month for Hubspot cookies being flagged.