SignalHost for Webflow: install the app, publish once, and see your first visit arrive

• A Webflow site on a paid site plan, or in a paid workspace. Webflow runs custom code only there; on a free site the app is accepted and nothing appears on the published page.
• A SignalHost account. The free plan is enough to try it: 10,000 requests a month and one container. You can create the account during the install.
• Site owner or admin rights in Webflow, because the app asks Webflow for access to that site.

Open SignalHost in the Webflow Marketplace and press Install. Webflow shows its approval screen: which site the app may use, and what it may do there. Choose your site and approve. If you cancel instead, nothing is installed and a SignalHost page says so.

Webflow then sends you to SignalHost. Sign in, or create a free account.

The next screen lists what the app will and will not do on your site, and asks which container the site should send its data to. A container is your own tagging server: a Tag Manager web container and server container, built in your own Google account, so they stay yours.

Pick an existing container, or choose New container and go through the short wizard. Building a new one takes a few minutes; you can connect the site straight away, and the tracking is added the moment the container is ready. Press Connect.

Webflow runs custom code only on the published site, so nothing changes for your visitors until you publish. The screen after Connect shows three steps — Connected, Tracking added, and Publish your site in Webflow — and the last one turns green by itself a few seconds after you publish.

Open Webflow from that screen and publish as you always do. There is also a Publish now button, which publishes through Webflow for you. It warns first that it publishes your whole site, including any changes you have not published yet. The app never publishes on its own.

Once the site is live, the same screen offers Test it. Press Open your site, look around for a moment, and send your contact form if the site has one. Each visit and form appears on that screen within about 15 seconds, by name: page views, scrolls, and the form as a lead. That is the proof the whole path works, from your visitor's browser through your tagging server.

Back to Webflow returns you to the Designer. Test it works on every plan, the free one included. From the Pro plan up, the container page also shows each event as it arrives under Live event monitoring, beside your statistics and the ad platforms you send to.

Two scripts, both registered through Webflow's custom code API, so nothing is pasted by hand:

• SignalHost, in the head: the Google Tag Manager loader, pointed at your own tagging address instead of googletagmanager.com. It loads your Tag Manager container from there.
• SignalHostEvents, in the footer: a versioned file with an integrity hash that turns what happens on the page into analytics events — a form's success message becomes generate_lead, a Webflow User Accounts sign-up becomes sign_up, and on a Webflow Ecommerce site, product pages, add to cart, the checkout and the order confirmation become view_item, add_to_cart, begin_checkout and purchase.

Prices and order totals come from Webflow itself, through your tagging address; they are never read off the page. The script never reads what visitors type into forms, and never a customer's name, email address, phone number or address.

Every request leaves the browser in a form ad blockers do not recognise, and your tagging server forwards it to Google Analytics 4 and to the ad platforms you set up on the container page: Google Ads, Meta, TikTok and others. The tracking follows your cookie banner through Google Consent Mode; a visitor who declines is counted only as Google's cookieless ping.

Your container starts on an address under signalhost.io. On the container page you can set up a subdomain of your own site instead, such as metrics.yoursite.com, which survives filter lists and keeps click cookies first-party. When it goes live, the app switches your Webflow site over by itself. The change reaches visitors with your next publish, and the old address keeps working until then.

Open app on SignalHost in Webflow, or Manage on the container page, opens your site's screen: its status, Test it, Back to Webflow and Disconnect. Settings, Connected sites lists every connected site as well.

Disconnect asks once, then takes both scripts off the site and deletes the webhook the app created. Like everything in custom code, the removal reaches visitors with your next publish. Your container and its statistics stay, and you can connect again at any time by installing the app once more.

If you uninstall the app in Webflow instead, Webflow removes the app's custom code with your next publish, and SignalHost notices that its access has ended and marks the site disconnected. Disconnecting first is the tidier order, because SignalHost then removes everything itself while it still can.

• Published, but the tracking is not on your site: the site is on a free Webflow plan, where custom code does not run. Move it to a paid site plan or workspace and publish again.
• Adding tracking to your site keeps spinning: a new container is still being built, which takes a few minutes. If its build failed, the screen says so; open the container to see why and try again.
• Nothing appears under Test it: make sure you opened the published address the button links to, not the Designer's preview, which runs no custom code. A browser that declined your cookie banner still sends a cookieless ping, so it should still show up.
• Publish now says to try again in a moment: Webflow allows one publish a minute.
• Anything else: write to hello@algorithmo.de with your site's address.

SignalHost is an independent product of Algorithmo GmbH and is not affiliated with or endorsed by Webflow, Google, Meta or TikTok. Google Analytics, Google Ads and Google Tag Manager are trademarks of Google LLC; Meta is a trademark of Meta Platforms, Inc.; TikTok is a trademark of ByteDance Ltd.; Webflow is a trademark of Webflow, Inc.