As new Amplitude users we noticed a weird pattern in our attribution data where Facebook.com and accounts.google.com were being attributed as referrers for a significant number of our registration events.
We quickly realised that when our users opted to authenticate via Google or Facebook’s social sign-in, they were temporarily leaving our domain to go to the respective site to give us permission to authenticate. When they come back to our domain, despite it still being the same session, Amplitude is overwriting the true attribution data e.g. referrer, referring domain, UTMs, etc, with either facebook.com or accounts.google.com.
We’ve excluded accounts.google.com as a referrer which neatly solves that one. Annoyingly as visitors who come from Facebook appear as facebook.com regardless of whether they clicked on a link, or came via the authentication page there’s no way to exclude that domain without losing attribution on genuine organic FB registrations.
We’ve been speaking with Amplitude support but hit a wall, so I’m reaching out here in the hope that there’s a community solution out there for us!
- Has anyone else faced this issue? Am I missing an obvious solution??
- Is there any way to set attribution to only write user properties once per session?
- Is there any way to stop Amplitude rewriting attribution data at a URL subfolder level e.g. domain.com/register/
Best answer by Patrick HilleryView original