Add GetFoxChat to your Framer site

Easiest: the GetFoxChat plugin for Framer

Add the GetFoxChat plugin to your Framer project, paste your Site ID into its one field, press Turn on the chat and publish. No code to paste.

Get the plugin on Framer

Prefer to add the line yourself? The steps below do the same thing by hand.

Watch it first

▶ Watch how

The line to add

Yours has your own site ID in place of YOUR_SITE_ID.

How do you add GetFoxChat to Framer, step by step?

1. In GetFoxChat, open the install step for your site and copy your snippet. It already has your site ID in it. No account yet? Create one free.
2. Open Project Settings (Site Settings) in your Framer project. source
3. Select the Custom Code tab from the left sidebar. source
4. Click Add Script, or the + icon if you already have code there, and name it GetFoxChat. source
5. Paste the snippet and choose the end of the body as its placement, on all pages. source
6. Choose how often it runs: Run on every page visit, or Once. source
7. Publish the site and open the live page in a browser to check the chat bubble appears. source
8. Back in GetFoxChat, press Check my site. The chat switches on once GetFoxChat finds the snippet on your live pages.

Framer's own guide: Framer Help: how to add custom code. Checked 2026-09-30; if Framer renames a menu, its guide has the current wording.

Framer gotchas

• Framer does not run custom code in the canvas or editor preview. Publish and check the live site. source
• Custom code in site settings applies to the whole site; code in a single page's settings only loads on that page. source

How do you remove it later?

Open Site Settings, Custom Code, delete the GetFoxChat entry, then publish the site again.

The Framer help article says Open Project Settings; the Framer Academy lesson and the Google Tag Manager article say Site Settings, so step 1 names both. The help article says 'Choose where the code should be placed' without listing the options in text; the exact dropdown label for end of body is not in any fetched page (the GTM article shows 'Start of <head>' and 'Start of <body>', and the Academy lesson says positions exist at the start or end of the head and body), so the step says 'the end of the body' rather than quoting a label. No fetched Framer page states a plan requirement for custom code, so needs is null. Which run option is right for GetFoxChat (Once versus every page visit) is not answered by the docs; Framer sites change pages without full reloads, so a live test is needed.