As shown in the figure below, by creating and arranging "views" of various analysis axes, you can check at a glance the difference in user behavior between overall and specific conditions.

Create a view that specifies "Mobile" as the device and a view that specifies "Desktop, Tablet, Other" as the device.
By specifying "http included" in the second page URL, you can extract sessions that have migrated.
<aside> 🔗
The second page URL is the URL that the user visited after the landing page.
</aside>
<aside> 🤖
Amethyst recognizes the second page if it has a different page_location parameter.
</aside>
By specifying the conversion event as a filter, you can extract the sessions where conversions occurred.
By setting "google" as the referrer and "organic" as the media, you can extract sessions of users who visited your website from Google's natural search results.
By setting the event "first_visit", you can identify and analyze the sessions of users who visited your website for the first time.
This is recommended when there are multiple landing pages.
After filtering landing pages with high CVR, you can create a view for each second page URL to analyze which migration paths are generating results.