1. Track the landing page URL as an event property
If you're using the Mixpanel JavaScript SDK, the referrer and current URL are available client-side. You can explicitly track the landing page URL (e.g., $current_url or a custom landing_page property) on your first event or as a super property. For server-side implementations, you'd need to extract this manually from the request. [Server-side best practices]
2. Use $referrer / $referring_domain properties
Mixpanel's JS SDK automatically tracks Initial Referrer and Initial Referring Domain — the URL a user came from before arriving at your site. These are stored in the Mixpanel cookie on first visit and appended to events. You could use these as a breakdown in an Insights or Funnels report filtered to your "Funding Application Submitted" event. [Web attribution]
3. Break down by URL/landing page separately from Attribution
Since Attributed by... can only be used as a breakdown (not combined with a second breakdown in the same dimension), a practical workaround is:
Build a Funnels or Insights report filtered to users attributed to "Google Non-Branded Search" (using a filter on utm_source / utm_medium / utm_campaign event properties).
Then break down by $current_url or your custom landing page property to see which URLs were associated with the "Funding Application Submitted" event.
4. Use Flows to trace the path
The Flows report can show you what events (including page views, if tracked) users performed before submitting a Funding Application. If you track page views as events with a URL property, you can filter by your attribution segment and trace back to the originating landing page. [Flows report]
