Referrals on Webflow, Framer, Bubble, Wix

Where the referral tag goes on Webflow, Framer, Bubble, Carrd, Squarespace and Wix, how Stripe Payment Links pick up the partner's code, and how signups reach your program. The whole setup, builder by builder, is in Referrals on a site built without code; this page is the part that differs between builders.

Each builder's menus and plans below were read on its own help pages on 27 October 2026, and each section says what could not be confirmed there. None of this was tried on a live blank site, so check the first referral end to end with Send a test sale and a test purchase of your own before you announce the program.

The tag

One line in the builder's site-wide head code, on every page:

<script src="https://boltclaw.ai/referrals/v2.js" defer
        data-welcome="auto" data-payment-links="auto"></script>

• data-welcome="auto" draws the friend's welcome (the bar, or the style you chose on the program's Welcome tab) when somebody arrives through a partner's link. Leave it out for no welcome. See The friend's welcome.
• data-payment-links="auto" adds the partner's code to every Stripe Payment Link and Buy Button on the page.
• The tag keeps the code in a first-party cookie on your own domain. If your cookie banner must ask before that, add data-consent="required" and have the banner call BoltClawReferral.consent(true) when the visitor accepts.

Stripe Payment Links

With data-payment-links="auto", every buy.stripe.com link on the page gets the code as client_reference_id (and the friend's discount code, when the program gives one), and every Buy Button gets it as client-reference-id. Connect Stripe on the program's Setup tab and those sales, renewals and refunds are credited with nothing else to do.

The tag changes the links that are on the page when it loads. A builder that draws a page in the browser after that (Framer and Wix when a visitor moves between pages of the site, and Bubble always) shows Payment Links the tag never saw, and those carry no code. Put the Payment Link on the page partners link to, check one with a test purchase, and on Bubble pass the code yourself (below).

Signups

A signup is a lead sent with your key, and a key must never be in a page. So a signup goes from the builder's form to something that holds the key: the Zapier app's Record a Lead, a Make or n8n webhook, or the builder's own server-side workflow. If people only buy, skip signups.

The partner's code has to travel with the form. This, in the builder's end-of-body code, adds it to every form on the page as a hidden field named boltclaw_ref:

<script>
  document.addEventListener("DOMContentLoaded", function () {
    if (!window.BoltClawReferral) return;
    document.querySelectorAll("form").forEach(function (form) {
      BoltClawReferral.attach(form);
    });
  });
</script>

Map boltclaw_ref to the lead's referral code, and use the person's own id or email address as the customer, so their later sale is credited to the same partner. Whether a builder sends a field it did not draw is its own business: check one submission and look for boltclaw_ref in it.

Webflow

• Head code: Site settings, Custom code, Head code (and Footer code for the end of the body). It runs only on the published site, not in the Designer.
• Plan: custom code needs an active Site plan (Basic is the cheapest) or a paid Workspace plan (Core, Growth, Agency or Freelancer). A free Starter site cannot have it.
• Payment Links: Webflow pages are whole pages, so links on every page get the code.
• Signups: a Webflow form, sent to Zapier with Webflow's Form submission trigger, or to a Make or n8n webhook from Site settings, Apps & integrations, Webhooks. Webflow Logic was retired in June 2025 and Webflow's own user accounts ended in January 2026, so there is no sign-up event of Webflow's own.
• Not confirmed: Webflow's help centre refused a direct read, so its wording was read through search results; whether a form webhook needs a paid plan.

Framer

• Head code: Site Settings, Custom Code, Add Script, placed at the end of the head, on all pages. One of Framer's help pages calls the menu Project Settings, another Site Settings, Code: it is the same place.
• Plan: none of Framer's pricing or help pages limits custom code to a plan; a custom domain needs a paid one.
• Payment Links: a Payment Link on the page a visitor lands on gets the code; one on a page reached by clicking within the site may not (above).
• Signups: a Framer form's Send To, Webhook, to a Make or n8n webhook (or a Zapier catch hook). Framer can sign it with a secret of your own.
• Not confirmed: which menu name Framer shows today; whether a Framer form sends the boltclaw_ref field the snippet adds.

Bubble

• Head code: Settings, SEO / metatags, Script/meta tags in header. The end-of-body field beside it is Script in the body.
• Plan: a live app, with your own domain, needs a paid plan (Starter is the cheapest).
• Payment Links: Bubble draws its buttons in the browser and they are not links, so data-payment-links="auto" has nothing to change. Read the code with BoltClawReferral.clientReferenceId() (with a plugin that runs JavaScript) and add it to the Payment Link's address as client_reference_id.
• Signups: a backend workflow when a user is created, calling the API Connector with the key in a header marked Private (Bubble then adds it on its server, never in the browser). Backend workflows are switched on in Settings, API. The body is in Referrals on a site built without code.
• Not confirmed: whether the header fields and backend workflows are on Bubble's Free plan (only a forum post says the header is not).

Carrd

• Head code: Carrd has no site-wide field. Add an Embed element with Type Code, Style Hidden and the location Head; a second one at Body End for the form snippet. An embed shows nothing in the builder: publish to see it.
• Plan: embeds need Pro Standard or higher.
• Payment Links: a Carrd site is one page, so a Payment Link button gets the code.
• Signups: a form of type Custom with Send to URL, or Send to Zapier, Make or n8n, needs Pro Plus. Point it at the automation's webhook, never at Bolt Claw with your key: Carrd's custom headers may be sent from the visitor's browser.
• Not confirmed: whether Send to URL leaves from Carrd's server or the browser; whether a Carrd form sends the boltclaw_ref field.

Squarespace

• Head code: the Pages panel, Custom Code, Code Injection, Header (and Footer for the end of the body). On version 7.0 sites it is under Website Tools.
• Plan: Core, Plus or Advanced, or a legacy Business or Commerce plan. On Basic, code injection is switched off.
• Payment Links: links on every page get the code. Checkout pages run no injected code, which does not matter here: the code is on the link before the visitor leaves.
• Signups: a form block's Storage, Zapier, then Zapier's New Form Submission trigger and Record a Lead. Squarespace runs no server code of its own.
• Not confirmed: whether Squarespace's form sends the boltclaw_ref field; whether injected code also runs while you are signed in to the editor.

Wix

• Head code: the site's dashboard, Settings, Development & integrations, Custom Code, Add Custom Code: place it in Head, on all pages, and load it once. It runs only on the published site.
• Plan: custom code needs a published site with a connected domain, which needs a Premium plan (Light is the cheapest). Changing the primary domain deletes the snippets. Wix Harmony sites run no site code at all.
• Payment Links: as on Framer, a link on the landing page gets the code; one drawn after moving between pages may not.
• Signups: an Automation on Visitor signs up to your site with Send HTTP request to a Make or n8n webhook (Wix documents no header for it, so never send it to Bolt Claw with your key), or Velo backend code with the key in the Secrets Manager, sending the lead with wix-fetch from wixMembers_onMemberCreated.
• Not confirmed: whether Wix's frontend security rules of December 2025 affect the tag (it uses only its own cookie, local storage and, with the welcome on, one request to Bolt Claw; none of that is in Wix's list of what they block); whether a Wix form sends the boltclaw_ref field.