You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The project I'm working on is using Partytown to achieve two goals:
Improve page-load speeds
Avoid scripts being automatically blocked by browsers
The first part is working fine. The second part is mixed.
When integrating Google Tag Manager, the requests for www.googletagmanager.com are sent through the resolveUrl callback configured on the frontend, but when using Google Analytics, there's a request sent out to https://region1.google-analytics.com/g/collect which doesn't pass through the callback and so cannot be proxied.
It still works, but it is vulnerable to browser blocking which I'd like to avoid.
Reproduction
N/A
Steps to reproduce
Follow the guide for Google Tag Manager integration.
Add Google Analytics stream with GTM.
Browser Info
Firefox, Chrome
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Could you post your configuration settings and resolveUrl function?
I tested routing /g/collect through resolveUrl the other day and it worked fine. I don't think anyone will be able to help without further information.
Describe the bug
The project I'm working on is using Partytown to achieve two goals:
The first part is working fine. The second part is mixed.
When integrating Google Tag Manager, the requests for
www.googletagmanager.com
are sent through theresolveUrl
callback configured on the frontend, but when using Google Analytics, there's a request sent out tohttps://region1.google-analytics.com/g/collect
which doesn't pass through the callback and so cannot be proxied.It still works, but it is vulnerable to browser blocking which I'd like to avoid.
Reproduction
N/A
Steps to reproduce
Follow the guide for Google Tag Manager integration.
Add Google Analytics stream with GTM.
Browser Info
Firefox, Chrome
Additional Information
No response
The text was updated successfully, but these errors were encountered: