Improve Traffic Source Attribution for Embedded Meetings When UTM Parameters Are Present
Traffic source attribution for contacts created through embedded HubSpot meetings is not correctly reflecting the original acquisition channel when valid UTM parameters are present in the URL.
When a visitor arrives from a paid campaign (such as LinkedIn ads) and UTM parameters are preserved throughout the journey from landing page to meeting booking page, HubSpot still often records Original and Latest Traffic Source as Direct after the meeting is booked using the embedded scheduler.
Although meeting-related properties may capture UTM values correctly, these values are not reflected in the main traffic source properties.
The expected behavior is that when valid UTM parameters exist and persist during the session, HubSpot should use them to accurately assign traffic source attribution across all relevant properties, including Original Traffic Source and Latest Traffic Source, even for conversions completed through embedded meeting flows.