Skip to content

Integrations

A short list, and an honest one. Everything below works today; anything not below does not exist yet, and is named rather than implied.

Available now

  • Any website, via HTML and JavaScript

    A container element and one script tag. That works on WordPress, Squarespace, Wix, Webflow, Shopify, a static site, or anything hand-built — because it is not a plugin for any of them, it is the standard mechanism all of them support. There is no per-platform integration to wait for.

  • An iframe runtime

    The calculator renders inside an iframe, so its CSS cannot affect your page and your page’s CSS cannot affect it. The frame reports its height and resizes to fit, so there is no inner scrollbar and no height to guess. If you would rather place the iframe yourself than use the script, you can.

  • Call-to-action handoff

    Three destination types: url, phone, email. A link to a page you own, a phone number, or an email address. The visitor goes to your destination; nothing is captured in between.

  • Engagement reporting in the dashboard

    Views, starts, calculations and click-throughs per calculator, site and embed, with no visitor financial data recorded. Available in the product, not as an API.

Not available

None of the following exists. They are listed because their absence is easier to plan around than to discover.

  • CRM integrations

    There is no Salesforce, HubSpot, Pipedrive or other CRM connector, and no partnership with any of them. The call to action can point at a form on your own site that feeds your CRM, which is the available path today.

  • Outbound webhooks

    Nothing is posted to a URL you nominate when a visitor uses a calculator. The one webhook in this system is inbound, from the payment provider, and is unrelated.

  • Native lead capture

    There is no enquiry form in the widget and no lead database behind it. That is a deliberate architecture rather than a missing feature: no name, email or phone number a visitor might type is stored here, because there is nowhere for it to go.

  • A public API

    No REST or GraphQL API for calculations or reporting. Configuration is done in the dashboard.

  • Zapier, Make, or automation platforms

    No connector exists for any of them.

Third-party analytics

The widget loads no third-party analytics of any kind. No Google Analytics, no Meta Pixel, no session recorder, no external tag. Nothing about your visitors is sent to a company neither of us has a relationship with.

Your own analytics on your own page still work exactly as they always did — the widget is an iframe on your page, and it neither adds to nor interferes with your tags.

What is recorded, and what is not

Next