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.

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

Security for the tracking script #84

Open
codasana opened this issue Jul 24, 2024 · 1 comment
Open

Security for the tracking script #84

codasana opened this issue Jul 24, 2024 · 1 comment
Assignees
Labels
feature request New feature request triage Triage

Comments

@codasana
Copy link

Describe the feature you'd like to request

Is there a way to add security for the tracking script. Right now, I can add script to any number of sites and it will record data from everywhere. So, someone can embed the script in any website and it will record events. Is there a way in Tinybird to implement some security so that data from only predefined websites is recorded. I don't want to do this in the script itself as that can easily be modified.

Describe the solution you'd like

Add security so only verified domains can send data. Otherwise someone can misuse the script and send unwanted data.

Describe alternatives you've considered

No response

@codasana codasana added feature request New feature request triage Triage labels Jul 24, 2024
@alejandromav
Copy link
Member

Hey there @codasana 👋

As of today, we don't have any mechanism in this starter kit to avoid that. Some options that come to my mind are:

  1. Filter the undesired hits in your Tinybird workspaces, by adding a clause in your pipes
    image

  2. Deploy the middleware to Vercel Functions as described here, and modify this function in your own for with the implementation you prefer.

Would any of these alternatives work for you?

Thanks for your feedback

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature request triage Triage
Projects
None yet
Development

No branches or pull requests

3 participants