SignalBridge- Install
- Site settings, Custom code, Head code, then publish
- Needs
- An active Webflow Site plan, or a Core, Growth, Agency or Freelancer Workspace, so custom code is available
- Page events
- Page views on every published page
- Lead events
- Form submissions, with the email, phone and name used for matching when the form collects them
- Ecommerce
- Purchase on the Webflow Ecommerce order confirmation page
- Coexists with
- Your existing Meta Pixel, Google tag and TikTok pixel
- Custom events
- sb_track() for anything the script does not detect
- Not included
- Refund and cancellation events, which need order data from Webflow
How it works
The script loads from the head
Webflow adds the head code to every published page. The script starts as soon as the page loads, stores the visitor's landing page, campaign parameters and ad click IDs, and sends a page view.
Forms are read when they are submitted
When a visitor submits a form, the script classifies it from its action URL and its fields. Webflow forms have no action URL, so a form with an email field is reported as a Lead and a form without one is not reported. The email, phone number and name are read from the form and attached to the event.
Ecommerce purchases are captured on the confirmation page
On a Webflow Ecommerce store, the visitor lands on the order confirmation page after paying. The script recognises the page, reads the order total and any order identifiers it can see, and sends one Purchase.
Existing pixels are mirrored
If your Meta Pixel or TikTok pixel fires an event, SignalBridge mirrors it to the server with the same event ID, so the platform counts the browser and server copies once. Webflow's own Meta Pixel setting counts as your Meta Pixel here. The Google tag's ecommerce events are mirrored when the page has no Meta Pixel.
The server delivers it
Consent is applied, then each connected platform receives the event through its own queue with retries, matched back to the ad click captured on arrival.
What the script captures on a Webflow site
Webflow has no data feed for SignalBridge, so events come from the pages and forms visitors use.
| Event | Detected from | Notes |
|---|---|---|
| PageView | Every published page | Includes the page type where it can be inferred. |
| Lead | Form submissions | Any Webflow form with an email field. It is recorded when the visitor submits, and once per browser session in any hour. |
| ScheduleCall, BookConsultation | Booking forms and calendar embeds | Calendly and Cal.com embeds are recognised. |
| ViewContent, AddToCart, InitiateCheckout | Webflow Ecommerce pages | Inferred from product, cart and checkout pages, or taken from your pixels. |
| Purchase | The order confirmation page | Needs the order total to be visible on the page. |
| Anything else | sb_track() | Send your own events with their values and user data. |
Requirements
- A Webflow site with an active Site plan, or a Core, Growth, Agency or Freelancer Workspace, because custom code is not available otherwise.
- Permission to edit Site settings and publish the site.
- A SignalBridge pixel and the ad platforms you want to connect.
- Optionally, a subdomain for first-party tracking, with access to your DNS.
Set up Webflow
Copy the snippet
Open your pixel in SignalBridge, choose Install, select the Webflow tab and copy the snippet. It uses your custom domain automatically when one is active.
Paste it into Head code
In Webflow open Site settings, then Custom code, paste the snippet into Head code and save the changes.
Publish the site
Custom code does not run on your live site until you publish. Publish to every domain you serve the site from, including any staging or subdomain you track.
Connect your ad platforms
In the pixel's settings connect Meta, Google Ads, TikTok or any other destination you use.
Test a form and an order
Submit a form on the live site, and on an Ecommerce store place a low-value test order. Check the event stream for each.
Verify it works
Look at the page view
Open the published site and check that a PageView appears in the event stream with the correct page URL.
Check the form event
Submit a form with a test email. A lead-type event should appear with the form ID, and the email should be recognised as present for matching.
Check the Purchase
After a test order, look for one Purchase with the correct value and currency, and confirm that it appears only once.
Troubleshooting
Nothing appears after pasting the code
Confirm the site was published after saving. Custom code shows up in preview mode, but it only goes live on your domain after publishing, and it does not run in the Designer's expand canvas view. Test on the published domain.
Form submissions are not recorded
Check that the form has an email field and that the visitor submitted it on a page where the script loaded. A form without an email field is not reported. Only one Lead is sent per browser session each hour, so test in a fresh session. If you use a third-party form embed, send the event with sb_track on success.
The Purchase has no value
The script reads the order total from the confirmation page. If your design labels or hides it unusually, send the purchase yourself with sb_track and the value, currency and order ID.
Purchases appear twice
Make sure the script is added once. Do not paste it into both Site settings and a page-level custom code block.
Only some pages report
Head code in Site settings applies to every page, but code placed inside an individual page applies to that page only. Use the site-wide location.
Conversions fall short of what Webflow records
Buyers who pay and close the page before the confirmation loads are not seen by the script. Compare over several days and treat small gaps as normal.
What to know before you rely on it
Where this integration stops, so the numbers you see are read correctly.
- There is no Webflow order feed. Refunds, cancellations and orders created in the Webflow dashboard are not seen.
- A purchase is only captured when the buyer reaches the confirmation page in a browser that runs the script.
- Order details depend on what your confirmation page shows. Check value and currency on your own design.
- Custom code needs an active Site plan or a qualifying Workspace plan, and it only runs after the site is published.
- Visitors who have not agreed to marketing tracking are not sent to ad platforms where consent applies.
- Webflow notes that on an Ecommerce site, scripts you add are outside its control and can create PCI DSS obligations of your own. Assess that for your store before adding any tracking code.
Questions about this integration
Do I need a paid Webflow plan?
Yes. According to the Webflow Help Center, custom code is available with an active Site plan or with a Core, Growth, Agency or Freelancer Workspace. Check your plan in Webflow if the Custom code tab is missing.
Does it work with Webflow Ecommerce?
Yes, for purchases that end on the order confirmation page. It is a script-based setup, so test an order on your own design to confirm the value and currency come through.
Will Webflow forms be tracked?
Standard forms are detected when they are submitted. The email, phone number and name from the form are used for matching when they are present.
Can I use it alongside my Meta Pixel and Google tag?
Yes. SignalBridge mirrors the events your Meta Pixel and TikTok pixel fire and reuses their event IDs, so those platforms count each conversion once. Keep one copy of each pixel on the page: Webflow's Help Center says to remove a Meta Pixel embedded as custom code before you add the Pixel ID in Site settings.
Why do I need to publish?
Webflow only serves custom code on the published site. Saving it in Site settings is not enough.
How does my cookie banner connect to SignalBridge?
The script does not read a cookie banner on its own, apart from Silktide's. Your banner has to tell it: call sb_consent(true) when a visitor accepts marketing cookies and sb_consent(false) when they decline. Set window.SB_REQUIRE_MARKETING_CONSENT = true before the SignalBridge snippet if visitors who have not chosen yet must not be tracked. Without that setting, a visitor with no recorded choice is treated as allowed. Decline once on a test device and confirm that no ad platform event appears.
Can I track a button or a custom action?
Yes. Call sb_track with an event name and properties from a custom code embed or an interaction.
Does it work with a custom domain on Webflow?
Yes. Publish to the domain you want to track. Separately, you can serve the SignalBridge script from your own subdomain for first-party loading.
Does it replace Webflow's analytics?
No. It sends conversion events to your ad platforms and your SignalBridge dashboard. Keep Webflow analytics or your own analytics tool for the rest.