A row of technographic data states that a technology was observed on a company's website between two dates. This post sets out what a row of Technology Stack holds in the marketing stack dataset, what each kind of evidence on it means, how its dates read, and how adoptions, removals and platform migrations are recorded in Technology Changes. After it you can open any row of Technology Stack and say what it tells you, and choose the right dataset for a question about state or a question about change.
What a row of Technology Stack holds
Technology Stack has one row per company website and technology, refreshed daily to weekly. Every row carries the company ID, so each technology is tied to an identified company and joins to every other Fokals dataset.
| Field | What it holds |
|---|---|
| Website | The domain the technology was observed on |
| Company | The company the website belongs to, by its stable company ID |
| Technology | The technology's name and its category |
| First seen | The first observation that showed the technology |
| Last seen | The latest observation that showed it |
| Evidence | The kinds of evidence that showed it |
| Removal marker | Set on a technology whose removal is awaiting confirmation |
The catalogue recognises 6,324 technologies in 69 categories: advertising pixels and conversion tags, tag managers, web and product analytics, consent management, commerce and content platforms, marketing automation, CRM, chat and support, payments, and on through JavaScript libraries, web servers and domain verifications with software vendors, to the stance a website states towards AI crawlers and agents. Additions to the catalogue are listed in the changelog of the methodology.
What each kind of evidence means
The evidence field says what kind of fact a row records, and seven kinds can appear on it.
| Evidence | What it tells you |
|---|---|
| Page content | A tag, pixel or platform marker in the pages a site serves |
| Scripts | A tag the site loads through its scripts, including those it manages in a tag manager |
| Network requests | A service a page calls when it runs |
| Response headers | A server or platform the site names in its responses |
| DNS records | The mail provider of a domain and the software vendors it has been verified with |
| robots.txt | The AI crawlers a site keeps out, and the uses of its content it allows or refuses |
| llms.txt | The guide to the site that a company writes for AI assistants |
Three points help in reading it.
- DNS records. A company's MX records exist so that its email is delivered, and its TXT records are how it proves to a software vendor that it owns the domain. A service shown by a DNS record alone, such as a workspace, an email provider or a domain verification, is a relationship between the company and the vendor.
- Account identifiers. Some technologies expose a public account identifier, such as an advertising pixel or an analytics property. The identifier is kept beside the technology, and a new account under a tool already in place is recorded as its own kind of event, so it is never counted as an adoption.
- AI access. robots.txt and llms.txt show the stance a website states towards AI: the AI crawlers it keeps out, the uses of its content it refuses, and what it publishes for AI assistants. The guide to AI readiness signals shows how to read them.
The sourcing statement sets out the rules of collection.
First seen, last seen and the baseline
Two dates carry the timing of a row.
- The first-seen date is the first observation that showed the technology.
- The last-seen date is the latest observation that showed it.
Both are observation dates, which is what makes the dataset usable point-in-time. A first observation of a website sets its baseline and is never counted as a change. A tool already in place carries the first-seen date of the baseline and writes no event to Technology Changes, so the record never mistakes an existing tool for a new adoption. An adoption you can date is one with an adoption event, because every event is a change that was observed to happen.
Take Acme Robotics, an illustrative company whose website was first observed on 23 September 2026.
| Technology | First-seen date | Evidence | Adoption event | How to read it |
|---|---|---|---|---|
| An analytics tool | 23 September | Page content, scripts | None | Part of the baseline: in place when the website was first observed |
| An email provider | 23 September | DNS records | None | Part of the baseline: in the domain's records at the first observation |
| A CRM tool | 30 September | Page content | 30 September | An adoption: observed to arrive, and dated by its event |
Adoptions, removals and platform migrations
Technology Changes is the change record: one dated event for every adoption and every removal, each with its observation time. Three properties make it a record to build on.
- A removal is confirmed before it is written. Tags come and go with consent banners and tests, so a removal event marks a tool that has stayed away.
- A platform migration is one event. When a commerce or content platform gives way to another, the pair is recorded as a single platform migration, with the platform before and the platform after.
- Every event carries its observation time. The time is when the change was observed, which makes the feed safe to use point-in-time: a query as of any past day returns what was known that day.
The two datasets answer different questions. For what a site runs, read Technology Stack. The query below returns the current stack and leaves out any technology whose removal is awaiting confirmation, which gives a strict list.
select domain, technology_name, technology_category,
first_seen_at, last_seen_at, seen_via
from company_technologies
where missing_since is null
order by domain, technology_category;For what changed, and when, read Technology Changes. The query below returns the adoptions and removals of technologies, those recognised from DNS records included, from a time you set.
select company, technology_name, change, observed_at
from company_tech_events
where category in ('technology', 'dns')
and change in ('added', 'removed')
and observed_at >= timestamp '2026-10-01 00:00:00'
order by observed_at;The guide to spotting churn risk when a customer removes your technology puts removal events to work.
How to read a row
Four points about the data decide how to use it.
- A row shows presence on the website. It states that a tool is there, between its first-seen and last-seen dates. Presence is the measure behind a fit rule, a competitive displacement list and an installed-base estimate.
- The evidence says what kind of fact it is. A tool shown by DNS records alone means that a company verified its domain with a vendor or routes its mail through one. A tool shown in page content or scripts is a tag running on the site.
- State and change are separate questions. Technology Stack answers what a company runs, with the dates between which each technology was observed. Technology Changes answers what it adopted or dropped, and when.
- Website and postings are two views of one stack. Technology Stack shows the customer-facing stack: advertising, analytics, commerce and marketing tools. The hiring dataset adds the tools each company names in its job postings, where internal systems tend to appear, and both views sit on the same company ID.
The marketing stack dataset delivers Technology Stack and Technology Changes with Website Profile, which holds the markets, languages, currencies, apps and key pages of each website. The data dictionary defines every field named here.
Frequently asked questions
What does first seen mean in technographic data?
It is the first observation that showed the technology on a site, which can be later than the day the company adopted it. A tool already in place when a site was first observed belongs to the baseline and takes that date. In Fokals data an adoption event in Technology Changes marks an adoption that was observed to happen, so use the event when you need the date of an adoption and the first-seen date when you need the state.
How do you know when a company stopped using a tool?
One absence is weak evidence, because tags come and go with consent banners and tests. Fokals confirms a removal before it is written, so a removal event in Technology Changes marks a tool that has stayed away, and the last-seen date in Technology Stack gives the latest observation that showed it. Together the two date the end of a tool's presence on a website.
What does the evidence on a technology row mean?
It says what kind of fact the row records. Seven kinds can appear: page content, scripts, network requests, response headers, DNS records, and the two files a site publishes for crawlers and AI assistants. A tag shown in page content or scripts is running on the site's pages, while a service shown by DNS records alone is declared in the domain's records, so a reviewer can tell the two apart on every row.
Can DNS records show what software a company uses?
Yes, for the services a domain declares. Companies publish MX records for email delivery and TXT records to verify ownership of their domain with software vendors, so DNS shows an email provider, a workspace and the vendors a domain has been verified with. Read a DNS record as a relationship between the company and the vendor, and a tag on the website as a tool running on the site.
How often is website technology data updated?
Fokals refreshes Technology Stack daily to weekly. Every adoption, removal and platform migration is written to Technology Changes as a dated event with its observation time. The feed of website changes runs oldest first from a time you set, so a scheduled pull keeps a warehouse current and the last cursor is the bookmark for the next run.
The queries and code on this page are examples to adapt. Test them in your own environment before you rely on them.