A website built on Foundation CMS tells you what people read; Scout tells you which companies they work for. Connecting the two puts Scout's company identification on every page a Foundation CMS site publishes, so a sales team can see which organisations are researching them, with a confidence score and a plain-English reason behind each match, without anyone touching tracking code when new pages go live.
Overview
This integration pairs Foundation CMS with Scout, Swarm Labs' visitor intelligence product. Foundation CMS is Swarm Labs' multi-tenant content management system on Cloudflare Workers. It holds a site's content and hands it to the site as whole, typed records, and every site runs as its own Worker with its own database and media bucket. Scout identifies the companies visiting a website and tells you what to do about it, and every match carries a transparent confidence score and a reason in plain English rather than an inflated number.
Scout is installed with a one-line snippet per domain. Because Foundation CMS never draws the page itself, that snippet lives in the site's own layout code, written once, and from then on it is present on every page editors publish.
Business Context and Core Use Case
The typical user is a business-to-business firm whose website is its main source of enquiries. Most visitors never fill in a form, so the site's real audience stays invisible. With Scout on a Foundation CMS site, the marketing team keeps publishing case studies, service pages and articles in the CMS as usual, and the sales team sees which companies arrived, how confident Scout is in each match and why. The two jobs stay separate: editors never handle tracking, and nobody in sales needs a CMS login.
The Applications Involved
Foundation CMS (Foundation CMS) holds the content and publishes the pages: editors work in an admin on the client's own hq. address that already knows their content types.
Scout (Scout) receives the visits through its snippet, matches them to companies and presents each match with its confidence and reasoning.
How the Integration Works
The site's domain is added in Scout, which issues a snippet for it. The snippet goes into the site's layout, the shared code every page is drawn with, so it loads on every page Foundation CMS serves. Scout checks that it is firing. From then on, publishing in Foundation CMS needs no extra step: a new page is drawn with the same layout and carries the snippet automatically. We load it in line with the site's privacy choices, alongside the other optional tags.
Immediate Operational Value
The first win is visibility: the organisations behind anonymous traffic appear, each with a reason the sales team can judge for itself. The second is that tracking stops being a publishing task. On many sites, a new landing page means remembering to add a tag; here the layout carries it, so campaign pages built in the CMS are measured from the moment they go live.
Security, Access, and Governance
Scout's snippet is part of the site's code, which lives in the site's own repository and is reviewed like any other change; editors cannot add or remove scripts from the CMS. Foundation CMS sites carry a privacy box that every visitor sees until they decide. Essential cookies are always on; analytics and marketing tags load only after a yes, and turning the box off means no optional scripts at all. Scout's own matching and data handling are governed by Scout's terms, and each site's privacy policy page, which the box links to, should name it.
Summary
Foundation CMS publishes the pages; Scout tells you which companies read them. One snippet in the site's layout covers every page editors will ever publish, and each company Scout identifies arrives with a confidence score and a reason rather than a guess.
Frequently asked questions
Do editors need to add Scout's code to new pages?
No. The snippet sits in the site's layout, which every page is drawn with, so anything published in Foundation CMS carries it automatically.
Can editors change tracking scripts from the CMS?
No. Scripts live in the site's own code, not in content, so they change through a reviewed code change rather than a field anyone can edit.
How does Scout decide which company visited?
Scout matches visits to companies and shows a confidence score and a plain-English reason for every match, so you can judge each one yourself.
Does Scout respect the site's cookie choices?
We load it in line with the site's privacy box, alongside the other optional tags, and the site's privacy policy should name it.
