Skip to main content
New Introducing Mosaic Learn more
CMS integration

Framer + Conversion

Capture page visits and Framer form submissions in Conversion for workflows and segments.

Framer
Into Conversion
Conversion

How Conversion works with Framer

Conversion connects to Framer through its tracking script and Forms SDK, added in your site's custom code settings, plus a code override on each form. The tracking script records page visits and ties them to a contact once the visitor identifies, and the override sends each form's fields to a Conversion form, where an email creates or updates a contact. From there, a Framer visit or submission works like any other in Conversion: it can start a workflow or qualify a contact for an audience.

What you can do

Forms stay in Framer

The withConversionForm override attaches to the parent form element and sends its fields to Conversion, so the form keeps the design you built in Framer.

One override per form

Each override file sends to one Conversion form. Naming the file after that form keeps every Framer form easy to trace back to its source.

Page visits that start workflows

Start a workflow when someone lands on a high-intent Framer page, and narrow it by URL, UTM parameters, referrer, or traffic type.

Anonymous visits, attributed later

Visitors who haven't identified themselves still build a visit history. The first time they submit a form, that history joins their contact record.

What syncs

Data Direction Details
Page visits Into Conversion Recorded by the tracking script with UTM parameters and referrer, and linked to the contact once they identify.
Form submissions Into Conversion Sent by a code override on each form to a Conversion form by field ID. Submissions with an email create or update a contact.

How to connect Framer

  1. 1 In Framer, open Site Settings > General > Custom Code and add the Conversion tracking script and Forms SDK script at the end of the head tag, then publish.
  2. 2 In the Assets panel, create a code override file for each form, with that form's Conversion form ID and field IDs.
  3. 3 Select the form on the canvas and apply the withConversionForm override to the parent form element.
  4. 4 Publish, submit a test entry, and confirm it appears in the form's Submissions tab in Conversion.
FAQ

Framer integration FAQ

Yes. Conversion connects to Framer through its tracking script and Forms SDK, added in your site's custom code settings, plus a code override on each form. The tracking script records page visits and ties them to a contact once the visitor identifies, and the override sends each form's fields to a Conversion form, where an email creates or updates a contact. From there, a Framer visit or submission works like any other in Conversion: it can start a workflow or qualify a contact for an audience.

Yes. The name set on each Framer form field must match the key the override reads, such as Email or Name. The override then sends each value to Conversion under that field's ID.

Yes. An override file sends to one Conversion form, so create one per form and name it after the Conversion form it feeds.

On the form's Settings page in Conversion, under Submit the form programmatically, which shows the form ID and field IDs to paste into the override.

See Conversion with Framer

Book a demo and we'll walk through the Framer integration on a stack that looks like yours.