Measure the journey from a Framer landing page

Prepare the destination and consent controls

Create an Analytics website for the published domain. Copy the generated tracking and consent setup from website settings. The website ID is public, but server API keys and payment secrets must never be pasted into Framer custom code.

Add the script through Framer custom code

Framer documents a Custom Code area in Project Settings. Add the generated snippet in the appropriate site-wide placement. The consent-required example below does not begin recording until your consent setup grants permission.

Configure it to load once rather than installing duplicate script instances on each navigation. Publish the site and test its actual routes and custom domain. Access to custom-code settings depends on your Framer setup.

Separate the landing page from checkout

A Framer page may link to checkout on another origin. Install the browser tracker where you can and follow the payment metadata instructions for the checkout you control. A normal outbound link alone does not establish a verified payment match.

Review one complete journey

Open a tagged campaign link on the published site. Check consent, navigation and a meaningful goal, then verify the supported payment connection. If you cannot change the external checkout or its metadata, expect incomplete attribution rather than a guaranteed match.