Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Security concern: Exposing GA4 measurementId in mint.json file #53

Open
perisicnikola37 opened this issue Jan 30, 2025 · 2 comments
Open

Security concern: Exposing GA4 measurementId in mint.json file #53

perisicnikola37 opened this issue Jan 30, 2025 · 2 comments

Comments

@perisicnikola37
Copy link

Problem Description:

Currently, I have defined the measurementId in the mint.json file, which exposes it in the client-side code.

Question:
Is it possible to set the GA4 measurementId without exposing it in the client-side code? If so, what are the best practices to protect against potential abuse and data manipulation?
@perisicnikola37 perisicnikola37 changed the title Use variables for integrations Security Concern: Exposing GA4 measurementId in Client-Side Code Jan 30, 2025
@perisicnikola37 perisicnikola37 changed the title Security Concern: Exposing GA4 measurementId in Client-Side Code Security concern: Exposing GA4 measurementId in mint.json file Jan 30, 2025
@kont395
Copy link

kont395 commented Jan 30, 2025

Problem Description:

Currently, I have defined the measurementId in the mint.json file, which exposes it in the client-side code.

Question:
Is it possible to set the GA4 measurementId without exposing it in the client-side code? If so, what are the best practices to protect against potential abuse and data manipulation?

@perisicnikola37
Copy link
Author

perisicnikola37 commented Jan 30, 2025 •
edited
Loading

Problem Description:
Currently, I have defined the measurementId in the mint.json file, which exposes it in the client-side code.
Question:
Is it possible to set the GA4 measurementId without exposing it in the client-side code? If so, what are the best practices to protect against potential abuse and data manipulation?

?

You know or no?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@perisicnikola37 @kont395