https://linen.dev logo
Join Slack
Powered by
Hi, I just realized that our website does not send...
# general
m
Hi, I just realized that our website does not send any data to rudderstack until visitors have clicked accept on the cookie consent banner. This means we lose utm referers and website hit unless they click "accept" first thing on the website. I need information on how to set up rudderstack so that we can collect GDPR compliant data on users that did not click the banner. You must be allowed to count website visits without cookies right? Any resources you could share?
m
It sounds like your site uses a "track only if allowed" type of compliance, you can try using "by default track unless consent declined"
h
You can record hits before consent, just rotate the user_id for each event sent and throw away ip_address etc
you can delete the cookies that rudder creates
m
@hundreds-lifeguard-65770 That seems to be what Google analytics does.
you can delete the cookies that rudder creates
How does this work? You use JS in the browser to delete cookies Rudder automatically creates?
@miniature-iron-53243
you can try using "by default track unless consent declined"
Isn't that illegal according to GDPR. I mean isn't the whole point that you have to ask for concent but looking at rudderstack.com that is how they do it.
h
correct just iterate all cookies, delete the rl_ prefixed ones
we keep all ours first party too by proxying all the rudder js/sourceConfig and event calls
m
Is there some advantage to having first party cookies only?
h
yes they stay longer and adblock doesnt get involved
m
I see. Thanks for you help. very useful!
👍 1
@hundreds-lifeguard-65770 Can I ask you another thing. I realize your solution has one issue for me in that I need to persist the UTM tags of the first page load until the user signs up to do sign-up attribution. Any idea if this can be done without cookies?
h
you can always persist them in the url
so they are always available until they sign-up
m
Thanks, good idea
Hmm, but won't there be a problem since every new pageload will have a new anonymous_id but the same utm parameters. This making it impossible to know if there is one user browsing 5 pages and then signing up or 5 users browsing one page and one of the users signing up?
h
you dont have to rotate the last anonymous_id if they sign up, you can use an identity call now that you have their email and stitch them to the last anonymous_id
and yeah your unique users increase with gdpr
m
Yeah but say the user rotated 4 anonymous_id before that. How do I know that they are the same
h
so you want to retrospectively track them after sign up
m
I notice that many "consent-free" analytics tools handle this by hashing request or ip-adress with a daily salt
h
you can do that in a transform for sure
m
Most important is to know number of uniques incoming per campaign and how many of them sign up
h
we use fingerprintjs which helps us with uniques
m
Is that taking into account ip adress too?
h
it does a multitude of things, device capabilities etc
ip is often not enough
m
Good suggestion, It doesn't seem to use ip but I guess you can combine it with whatever you want.
h
the pro version will (it involves a serverside call for bot/fraud detection too)
Open in Slack
PreviousNext
Powered by