Technical Snippet Documentation

Last updated: 13 July 2026

This page is a plain-language reference for the one-line JavaScript snippet that FAIND (leif ventures UG) provides for embedding on a customer's own website. It is written for technical implementers, SEO agencies, and data-protection officers who want to understand what the snippet does, what it stores, and how to install it. For the data-protection and legal classification of this processing, see Snippet Data Statement; for step-by-step setup and hosting options, see Implementation Guide. The snippet is served in the clear and can be read in full at its source URL.

1) What the snippet is

The snippet is a single, small, asynchronous JavaScript file that a customer embeds on the pages of their own site. It supports the FAIND product by keeping the AI-optimized Knowledge Graph (a static mirror of the customer's public pages) current when the source pages change. It is not an analytics beacon in the conventional sense and it builds no visitor profiles.

Install it with one line in the page's HTML:

• Install tag: <script async src="https://app.getfaind.com/geo/snippet.js.php?d=DOMAIN_ID&t=TOKEN"></script>
• Validation: the tag carries your domain ID (d) and token (t). If they are invalid, the snippet does nothing further (a no-op).

2) What it does

The snippet performs a small set of well-defined jobs:

• Change detection: it derives a technical content fingerprint from the page's own visible content so FAIND can tell when a source page has meaningfully changed and the Knowledge Graph mirror needs to be refreshed. This keeps the mirror current without you having to notify us manually.
• Measuring AI-driven visits: it measures visits that originate from AI systems and classifies traffic as bot vs. human. This produces aggregated counters, not per-visitor records.

3) DOM behavior

What the snippet reads from the page:

• Reads its own page's main content: it reads the page's own rendered main content (its headings and body text) to derive the change-detection signals described in §2. It excludes navigation, footers, ads, and cookie/consent UI.
• Reads NO user-entered data: it reads no form inputs and no field values. It never touches anything a visitor types.

What the snippet writes into the page:

• Nothing that stores data on the visitor's device. The snippet injects no content that reads from or writes to the visitor's browser storage, and it adds no third-party tags. It is async and non-blocking, and fails closed under a strict Content-Security-Policy.

4) Device storage: none

The snippet reads nothing from and writes nothing to the visitor's device. Specifically:

• No cookies.
• No localStorage, no sessionStorage, no IndexedDB.
• No device or browser fingerprinting.

Because the snippet neither stores information on nor reads information from the visitor's terminal equipment, it does not require consent under §25 TDDDG. See Snippet Data Statement for the full legal analysis, including the data categories it transmits, the purposes, the proposed legal basis, and retention.

5) Load impact

• Asynchronous and non-blocking: a single small script; it does not block rendering.
• Deferred: its work runs after the page has loaded, and every network call is bounded by a short timeout.
• Fails closed under strict CSP: if a strict Content-Security-Policy blocks the snippet, it fails closed and the rest of the page is unaffected.

6) Security posture

• No credentials to your systems: the snippet holds and uses no credentials for the customer's own systems; it authenticates only its own domain-ID/token pair against FAIND.
• Readable source: the script is served in the clear and can be read and audited in full at its source URL.
• No user input read: as noted in §3, it reads no form inputs or values.
• No third-party tags: it loads no third-party tags and builds no visitor profiles.

7) Install

• Script tag (required): place the one-line install tag from §1 on the pages you want covered. That is the only mandatory step.
• CNAME (optional): to serve the Knowledge Graph on a subdomain that FAIND provides, point a CNAME at FAIND. Details in the Implementation Guide.
• Google Tag Manager: the snippet can be deployed through GTM. Create a Custom HTML tag containing the one-line async install script from §1 and set it to fire on All Pages.
• robots.txt: no special robots.txt changes are required for the snippet itself; your existing crawl rules are unaffected.

8) Further reading

For the data-protection and legal view of what the snippet processes — legal bases, the classification of the transmitted metadata, and retention — see Snippet Data Statement. For hosting, CNAME, and setup details, see Implementation Guide. Related documents: Privacy Policy, Data Processing Agreement, Terms of Service, and Imprint.

Questions about this documentation: leif ventures UG (haftungsbeschränkt), Karl-Marx-Str. 250, 12057 Berlin, Germany · Email: privacy@getfaind.com