Reliable Methods to Identify Events on Landing Pages

Hi Elena M., Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋

Yes, you can reliably identify whether an event occurred on the landing page by using event properties that capture the URL or path of the page where the event was triggered. When using Mixpanel’s JavaScript SDK with Autocapture enabled, each event includes properties such as $host (the hostname), $pathname (the path portion of the URL), and $current_url (the full URL, if configured). By filtering events based on these properties, you can determine if an event happened on your landing page (e.g., $pathname equals /landing-page or similar) Autocapture event properties.Additionally, in Mixpanel’s Flows and Sessions reports, you can break down or filter by the “Current URL” or “Page Name” property to analyze user actions specifically on the landing page or to identify the most common landing pages for sessions Sessions use cases.So, as long as your events include the relevant URL or path properties (which is automatic with Autocapture or if you manually include them), you can reliably identify landing page events.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Let me check the knowledge base for you again. One moment! 📚

You're correct—any page can be a landing page, depending on where a user first enters your site. Mixpanel helps you identify which page was the landing page for each session by using the Session Start event. The Session Start event automatically inherits properties from the first event in the session, including the Current URL. By breaking down Session Start events by the Current URL property, you can see which pages are most commonly used as landing pages for sessions. This approach allows you to reliably identify the landing page for any given session, regardless of which page it is Sessions use cases.If you want to know whether a specific event occurred on a user's landing page, you can compare the event's URL properties (like $current_url or $pathname) to the Current URL property of the Session Start event for that session. If they match, the event occurred on the landing page.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Let me check the knowledge base for you again. One moment! 📚

To identify events that did not happen on the landing page, you can use Mixpanel’s session properties and event properties together: - The Session Start event captures the landing page for each session via the Current URL property. - For other events in the same session, compare their Current URL (or similar page property) to the Current URL of the Session Start event. - If the event’s URL does not match the Session Start’s URL, then the event did not occur on the landing page.However, the knowledge sources do not explicitly describe a built-in Mixpanel feature or formula to automate this comparison directly within the UI. You would need to use breakdowns and filters to analyze events by their page properties and session context, or export the data for more advanced comparisons.In summary: You can identify events not happening on the landing page by comparing the event’s page property to the Session Start’s page property, but Mixpanel does not provide a direct, out-of-the-box filter for this scenario in the UI according to the available documentation Sessions use cases Session properties.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.