Skip to content
FORMO.
On this page

Getting startedUpdated 12 Aug 2026

Install per platform

Exact click-paths for Shopify, WooCommerce, Squarespace, Webflow, and other HTML sites.

View product page →

The script tag is the same on every platform. Only the place you paste it changes. Copy it from Dashboard → Setup first.

Shopify#

Theme liquid (recommended)

  1. In Shopify admin, open Online Store → Themes.
  2. On the live theme, click … → Edit code.
  3. Open Layout → theme.liquid.
  4. Paste the Formo script immediately above the closing </body> tag.
  5. Click Save.
  6. Open the live storefront once so Formo can mark the site Connected.

Custom Liquid (Online Store 2.0)

  1. Online Store → Themes → Customize.
  2. Open a footer section group (or add a section).
  3. Add a Custom Liquid block.
  4. Paste the same script snippet.
  5. Save, then load the storefront once.

Do not put the script only on a draft theme if you expect Connected to flip from the live shop.

WooCommerce (WordPress)#

  1. In WordPress admin, open Appearance → Theme File Editor. Prefer a child theme.
  2. Open footer.php (or the footer template your theme uses).
  3. Paste the Formo script before </body>.
  4. Update the file.
  5. Load any storefront page once.

If your host blocks theme file edits, use a header/footer plugin and paste the script in the footer code box, then load a public page once.

Squarespace#

  1. Open Settings → Advanced → Code Injection.
  2. Paste the Formo script in the Footer box.
  3. Save.
  4. Open the live site once (not only the editor canvas).

Webflow#

  1. Open Project settings → Custom code.
  2. Paste the Formo script in Footer code.
  3. Publish the site (custom code does not run in the designer).
  4. Load a published page once.

Other / plain HTML#

  1. Paste the script on every page where chat should appear, just before </body>.
  2. Serve those pages from a host listed under the site’s allowed domains.
  3. Load the page once.

Heavy CSS / page builders#

The widget renders inside a closed shadow root. Host theme CSS cannot restyle it, and widget CSS cannot leak out. If a builder strips <script> tags, use the platform’s official custom-code or liquid slot instead of a rich-text field.