Add agentface to your site
Agents leave when they can't get through. One line lets them finish. People see nothing new.
For your privacy notice: What the agentface snippet stores
For developers
What works on a complicated site
A page the server sends complete works. These are the other kinds of site.
| Kind of site | Support | What to expect |
|---|---|---|
| The page changes its address without loading again | Works | agentface stays on the page, and so do back and forward. What an agent does is counted on the address showing at that moment. A site that only changes the part after a hash keeps every count on the path before the hash. The text of the page still shows the full address, hash included. |
| A page behind a sign-in | Partly | On the page that is open, an agent sees what the signed-in visitor sees, including its forms. Opening a different address sends no sign-in, so a members-only page comes back as the signed-out page. Anything made for the site alone is still built with nobody signed in, so it is not made for members-only screens. |
| Several subdomains of one business | Partly | The www address and the bare domain are one site, and what happens on either is counted for it. Any other subdomain, such as a shop, is its own site and is added on its own. A count is only for the site whose address it came from. A tag copied onto a different address is counted for nobody. |
| Pages filled in by scripts | Partly | On the page that is open, text and forms added after it opened are included, and so is what a web component draws where the page can see it (an open shadow tree), including text placed into it. A search form drawn that way is found. A closed shadow tree is not read, because the page does not hand it over. A frame on the page is not read or filled from the outside. When that frame is itself a page of the site, it has its own tag for what is inside it. Opening a different address reads the HTML and does not run its scripts, so anything a script adds after that page opens is missing. An open shadow tree the HTML itself writes is still part of that read. |
| A strict content security policy | Works | Add https://cdn.agentfacehq.com to script-src, so the page can load the tag, and to connect-src, so what an agent does can be counted. If the policy names script-src-elem, change that rule instead of script-src. The command and the check read the policy on the live homepage and, when it blocks the tag, print the lines to change. Use those lines. A shorter version of this note can miss a stricter rule. The check then fails until those lines are published. Without connect-src, an agent can still use the open page and the browser drops the counts. |
| A policy with strict-dynamic | Works | A policy with strict-dynamic ignores the hosts in its list. The tag runs when it carries the same nonce as the page's own scripts, or when a script that already has that nonce adds the tag. Without one of those, the tag does not run. connect-src is still needed for the counts. Running the command again keeps a nonce already on the tag. |
| Installed with Google Tag Manager | Works | A Custom HTML tag that holds the script line, set to run on every page, is enough once the container is published. On a strict-dynamic policy, give the Tag Manager code already on the page the page's nonce. The tag it then adds is allowed. |
Works means that happens. Partly means it happens with the limit named here.