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

Enhancing fallback referrer #300

Open
raphaelbernhart opened this issue Nov 26, 2021 · 1 comment
Open

Enhancing fallback referrer #300

raphaelbernhart opened this issue Nov 26, 2021 · 1 comment

Comments

@raphaelbernhart
Copy link

Problem
As many apps refer via a referrer parameter in the url called ref but ackee uses source as the parameter this leads to many refs untracked.

Solution:
Create a alias of the source param called ref so if any app referrs via the ref param it will also get tracked.

Ik that there is a fallback referrer but this does not catch all refs.

I see if I have some spare time to create a PR. :)

@electerious
Copy link
Owner

We already had support for ref, but I've removed it: #169 (comment)

The problem was that it's overwriting the referrer, but I agree that supporting ref is a good idea. Especially because some browsers are sending an empty referrer. I need to check how the current implementation works. It should still use referrer even available. ref shouldn't be able to overwrite referrer.

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

No branches or pull requests

2 participants