My understanding is that if we used the Browser SDK along with the Marketing Analytics SDK, we would get attribution tracking (e.g. UTM params) and the ability to turn on automatic pageview events.
However, given discussion in my other question and the benefit of more specific events in amplitude reports, we are implementing custom events for each page view in our site and thus disabling automatic pageview events in the Marketing Analytics SDK. All good so far.
Our custom events are making it through to our development project in Amplitdue but but I’m surprised to see that there are properties missing that I expect to be there like page_path, page_domain which you do get on the automatic generic pageviews if we left that feature on.
I then looked at custom events for click tracking we are doing on some buttons and see that they are also missing context of domain and path.
No web analytics platform I’m aware of fails to add these properties automatically (which I’d consider essential). I can’t imagine Amplitude would make every customer with the web SDK have to pass these event properties in manually with every track call, when their pageviews collect it automatically.
Our track calls couldn’t be simpler which is why I’m confused. e.g.
amplitude.track(“View Pricing Clicked”)
amplitude.track(“Mktg Homepage Viewed”)
Given this I’m thinking it must be our own error that’s causing these properties to be missing. what could it be? Or do we really have to set page_path and page_domain (along with other basics) in event props for all custom events?
Best answer by dangraingerView original