LeadSource
Lead source attribution data.
Attribution uses three complementary signals:
- UTM params: which campaign/channel drove the lead
- referrer: the page that linked to the booking (for embeds, the host page URL)
- booking_link_id (on Call): which funnel the lead entered through
LeadSourceFields
Derived ad platform (meta, google, tiktok, …) from click IDs or utm_source
Ad-platform click IDs (fbclid, gclid, fbc, …) for conversion APIs
IP-derived geolocation captured with the lead
Originating landing-page URL (host + pathname). Preserves the page path that referrer loses when the scheduler is embedded cross-origin, so pages sharing one booking link and identical UTMs stay distinguishable.
The full address of the page the lead landed on, query string included. Recorded by the Aura embed loaders with credentials removed. Like the UTM fields it is visitor-supplied attribution, not a verified address; a value supplied through the REST API as metadata.landingUrl is stored as sent. Null when the lead has none.
HTTP referrer URL. For embeds, this is the host page where the booking widget was displayed. For direct visits, this is the traffic source URL.
UTM tracking parameters (source, medium, campaign, term, content, id)