/handbook/headless-wordpress/glossary/
What We Do
Digital Platform MigrationsKey SolutionsManaged ServicesStaffing SolutionsIndustriesProducts
Discovery
Strategic consultancy & project roadmap
Growth Services
On demand development & consultation
Site Maintenance
Annual maintenance. Done for you
QE Services
Testing across SDLC for assured quality
Hosting Migration
Move to a performant hosting with zero downtime
WooCommerce
Enterprise commerce delivered without lock-in
AI
Unlock real use cases and integrations
All Services
A suite of services for any need
Technology STACK
eCommerce
Scale your e-commerce with WooCommerce, integrations, and custom extensions for growth.
EasyEngine
Server management tool that makes using WordPress on Nginx easy.
Web Auditor
Performance Audit & Insights for your Website.
rtMedia
A complete media management plugin for WordPress.
Resources
About Us
CLEAR
Resources When to go Headless? Key concepts & terms
Topics
On this page
- When to go Headless?
- rtCamp’s philosophy & principles
- How to run a Headless discovery
- Key concepts & terms
API Contract & Schemas
CDN – Content Delivery Network
Code Standards & Code Quality
Composable Architecture
Decoupled Architecture
DX – Developer Experience
Future-proofing / Feature-proofing
Maintainability
Project KPIs – Key Performance Indicators
Rendering Strategy
ROI – Return on Investment
Separation of Concerns
Source of Truth
TCO – Total Cost of Ownership
Tech Debt
Type Safety
UX – User Experience
Workflow Automation
Last updated on Apr 1, 2026
Key Concepts & Terms
API Contract & Schemas
APIs define how different isolated structures can exchange data. The API Schema defines the specific structure for the exchange.
As long as the data source adheres to the API Contract by returning the data specified in the schema, projects that consume that data (and the developers who work on them) don’t need to know anything else about the internals of that source. A breaking schema change is a violation of that contract, and may require code refactoring.
CDN – Content Delivery Network
A CDN is a distributed network of servers that caches content or assets for the user instead of delivering them directly from a central server. Edge Computing takes this further, allowing you to even execute code from the “Edge”.
When implemented correctly, CDNs can improve website speed (by delivering assets more quickly), performance (by generating assets more efficiently), and costs (as a function of both). Headless and Decoupled architectures provide more opportunities to implement a CDN as part of your overall strategy, but you still must be able to justify whether a CDN is the best way to achieve your goals.
Code Standards & Code Quality
Code Standards are a set of enforceable – and hopefully autofixable – rules for how code in a project should be written. Code Quality refers to how well code adheres not just to those standards, but best practices around performance, security, maintainability, and more.
Projects with stricter code standards and quality requirements make it easier for developers (human and AI alike) to onboard and contribute to a project. They provide guardrails for juniors and free up code reviewers, allowing everyone to better spend their time on “higher order” concerns. Care, however, should be taken to ensure these rules aren’t so overly strict as to get in the way of developers and become a costly bottleneck themselves.
As the costs and complexity of Headless WordPress is higher than traditional tech stacks, the importance and value of strict, autofixable rulesets is significantly more as well.
Composable Architecture
Composability is an approach to building systems by combining smaller, independent services together. Composable architecture minimizes the surface area between various Separation of Concerns, so individual pieces can be updated, removed, or replaced without disrupting huge swaths of the codebase. This both helps lower maintenance costs over the long term, and acts to increase longevity and mitigate risk by allowing for portions of the project to be reused or upcycled.
Composability is central to rtCamp’s approach to Headless WordPress as it is a tool to deliver at scale across different enterprise clients.
Decoupled Architecture
Decoupled architecture is where the presentation layer (the “head”, or “frontend”) is separated from the data layer (or “backend”). This separation of concerns is usually managed via an API.
Headless WordPress (or any Headless CMS ) is a type of decoupled architecture, where WordPress in its entirety is severed from its built-in presentation layer, but decoupled patterns are used even in traditional WordPress more and more frequently.
DX – Developer Experience
DX refers to the overall experience and effectiveness of developers working on a particular tech stack or project. Broadly speaking, the better the DX, the easier it is to contribute quality code to the project.
A lesser concern in smaller projects, DX has cost implications on training, maintainability, scalability, and ROI on complex and enterprise projects. However, DX should serve those specific goals, and is not a goal in and of itself.
Due to its stack flexibility, Headless WordPress offers many opportunities for improved DX in comparison to traditional WordPress but the choice to “use Headless WordPress” alone does not guarantee improved DX and must be consciously planned.
Future-proofing / Feature-proofing
Future-proofing is the process of minimizing the effects and risks potentially caused by future changes in a project’s stack of dependencies. Feature–proofing is the process of maximizing the opportunity to benefit from those changes at minimal cost.
Both provide outsized benefits for Headless WordPress projects due to the increased costs involved. Headless WordPress can also be used as a strategy for future adaptability by maintaining strict separation of concerns and using composable architecture.
Maintainability
Maintainability is the ease in which a component or project can be modified to fix bugs or adapt to changes in its dependencies.
Maintainability is a huge focus in Headless WordPress, where the high initial development costs need to be offset over the total life of the project. Most of the terms in the article affect maintainability in one way or another.
Project KPIs – Key Performance Indicators
A project KPI – Key Performance Indicator is a specific, quantifiable measure used to track the success of a project against its specific strategic goals. Performance in this context refers to how well the goal is met, not the technical performance of a piece of code.
Headless WordPress is a tool that should always be linked to achieving specific KPIs. This ensures headless is the right tool for the job while keeping runaway costs in check and the TCO down.
Rendering Strategy
A rendering strategy is the deliberate choice of how and when a website’s content is generated and rendered into HTML for the user. On one end of the spectrum we have Server-side Rendering (where pages are built on-demand for each visitor), on the other is Static Generation (where full pages are built ahead of time), and there are many partial strategies in between.
In traditional WordPress, there is no strategy, and all pages are server-rendered – albeit potentially cached first. Headless WordPress provides you the ability to choose the particular strategies that work best to meet your project KPIs, provide a better User Experience and lower your overall TCO by ensuring that server resources are used efficiently or when absolutely necessary.
ROI – Return on Investment
ROI – Return on Investment is a performance measure used to evaluate the efficiency or profitability of a project. It directly compares the financial gain or benefit of a project to how much it cost.
Because Headless WordPress projects often have higher upfront development costs than their traditional counterparts, calculating a clear ROI is not just a formality; it’s essential for project approval and success. Defining specific Project KPIs from the outset ensures that the investment is directly tied to a tangible and positive business impact.
Separation of Concerns
Separation of Concerns is a design principle for breaking a system down into distinct sections, where each section addresses a self-contained responsibility. The goal is to ensure that a change in one section will have little to no effect on any other.
This principle is the foundation upon which all Decoupled Architecture is built. In a traditional monolith, concerns are mixed; a change to a plugin could accidentally break the visual layout. In Headless WordPress, the “concern” of content management is strictly separated from the “concern” of frontend presentation.
This separation is what enables parallel workstreams for frontend and backend developers, reduces the risk of unintended side effects, and is a key driver for long-term Maintainability. Enforcing a strict separation of concerns is the single most important factor in lowering the TCO of a complex headless project.
Source of Truth
A Source of Truth is the single, authoritative location that is responsible for a specific piece of data.
In a traditional WordPress monolith, WordPress itself is the default source of truth for nearly everything. When using Decoupled Architecture, however, you must be deliberate about defining your sources of truth. While WordPress may be the source of truth for article content, customer data might come from a CRM, and product inventory managed in your ERP.
Establishing clear and distinct sources of truth is a critical early step in any headless project. It prevents data conflicts, simplifies the API Contract, and is foundational to achieving low-cost Maintainability by ensuring every piece of the system knows exactly where to get the correct information.
TCO – Total Cost of Ownership
TCO – Total Cost of Ownership refers to all the direct and indirect costs incurred during the entire lifecycle of a product or system, from initial purchase to termination.
While Headless WordPress projects typically have higher upfront costs than traditional builds, we can use many strategies to achieve a lower TCO over the long run. Factors like improved Maintainability, a better DX that leads to more efficient development, and composable architecture that lets you salvage parts of a project for reuse are just a few strategies that can be used to reduce the TCO and improve the project’s ROI.
Tech Debt
Tech debt refers to the implied long-term costs caused by choosing an easy or limited solution now instead of a better, more sustainable approach that would take longer to implement.
While all projects accumulate some tech debt, the stakes are higher in Headless WordPress, where the increased complexity and initial costs mean that early shortcuts – like a poorly designed API Contract or inconsistent Code Standards / Quality can create exponentially more expensive problems later on.
A thorough discovery is essential to avoiding the poor planning decisions that lead to costly tech debt, while taking the time to structure the project intentionally and adopting automated workflows will keep the TCO predictable and under control.
Type Safety
Type safety is the ability of a programming lange to prevent errors by ensuring that the data being used is of the correct type and shape, such as by trying to do math on a text string or to access an object property that isn’t defined.
Type safety is a critical feature to prevent developers from shipping accidental bugs, as they alert you to any usage issues before they arise and without the need to write specific usage tests. They’re a great form of Code Quality guardrails to keep the overall TCO down.
In Headless WordPress, type safety allows for the strict adherence to the API Contract needed to manage our separation of concerns effectively, making sure that any schema changes are intentionally applied and alerting us to incompatibilities with the existing code.
UX – User Experience
User Experience refers to the way a person interacts with a product or website.
A primary driver for choosing Headless WordPress is the opportunity to deliver a superior UX. Freed from the constraints of a traditional WordPress theme, development teams can choose and iterate with modern technologies to deliver experiences that users expect from enterprise-level properties.
Specific UX requirements should be linked to Project KPIs to justify our overall use of Headless WordPress, along with explanations as to why the ROI would be lower if implemented using Traditional WordPress.
Workflow Automation
Workflow Automation is the process of using technology to automatically and repeatably execute a series of tasks. For Enterprise projects, workflow automation is usually integral for CI/CD, with its value increasing in accordance to the complexity of the project it is introduced to.
In Headless WordPress, both the impact and opportunities to adopt automated workflows are greater. Automating tasks like code reviews and complex deployments eliminates repetitive manual work, reduces the risk of human error, and frees up developers to focus on high-value problems.
How to run a Headless discovery
PREVIOUS
Credits
David Levine
Author
David Levine
Author
David Levine is a Senior WordPress Engineer and Product Lead at rtCamp with a background that few engineers in the WordPress space can claim. A WordPress Core Contributor across multiple releas…
Good Work. Good People.
Industry partnerships
Compliance certifications
United States India
© rtCamp Inc. since 2009. All rights reserved.
Terms of Service · Privacy Policy · Trust Center
Company
Solutions
Subscribe to our newsletter and get a few email updates every month.
United States India
© rtCamp Inc. since 2009. All rights reserved.
Terms of Service · Privacy Policy · Trust Center
Cookie Consent
We value your privacy
We use cookies to give you the best possible experience. By clicking “Accept,” you consent to our use of cookies to improve site functionality, analyze usage, and personalize content and communications. Your privacy matters to us, and we are committed to handling your data responsibly and transparently. Please check our Privacy Policy for more details.
Manage PreferencesDon’t AllowAllow All
Why do we use cookies?
×
By clicking "Accept" or "Decline All" at the bottom, you consent to the use of cookies and other tools as described in our Cookie Policy in accordance with your settings and accept our Terms of Service.
Toggle EssentialEssential
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Geolocation Config
This cookie is used to store the consent settings based on the visitor's location.
30 days
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
30 days
Toggle CloudFlareCloudFlare
CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
Service URL: developers.cloudflare.com (opens in a new window)
Name
Description
Duration
cf_clearance
Whether a CAPTCHA or Javascript challenge has been solved.
session
Toggle CommentsComments
These cookies are needed for adding comments on this website.
Name
Description
Duration
comment_author
Used to track the user across multiple sessions.
Session
comment_author_email
Used to track the user across multiple sessions.
Session
comment_author_url
Used to track the user across multiple sessions.
Session
Toggle GodamGodam
GoDAM" is primarily a specialized WordPress plugin and media management service designed to enhance video hosting, marketing, and asset management directly within the WordPress dashboard.
Service URL: godam.io (opens in a new window)
Name
Description
Duration
user_image
Temporarily stores the path to the user's avatar or profile picture for quick rendering in the website header.
session
user_id
Stores the numerical ID of the logged-in user to maintain session continuity and basic site operations.
session
full_name
Stores the logged-in user's display name to personalize the site interface without needing database queries.
session
system_user
First-party cookie used to store basic application state identifying the current system user role.
session
sid
A generic session ID cookie used to maintain user state and functionality as the visitor navigates through the site.
session
Toggle Google reCAPTCHAGoogle reCAPTCHA
Google reCAPTCHA helps protect websites from spam and abuse by verifying user interactions through challenges.
Name
Description
Duration
_GRECAPTCHA
Google reCAPTCHA sets a necessary cookie (_GRECAPTCHA) when executed for the purpose of providing its risk analysis.
179 days
Toggle Google Tag ManagerGoogle Tag Manager
Google Tag Manager simplifies the management of marketing tags on your website without code changes.
Name
Description
Duration
cookiePreferences
Registers cookie preferences of a user
2 years
td
Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator.
session
Toggle StatisticsStatistics
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Toggle Factors AIFactors AI
Factors.ai is a B2B account intelligence and marketing analytics platform that helps Go-To-Market (GTM) teams identify anonymous website visitors, track buyer journeys, and measure the ROI of marketing campaigns.
Service URL: www.factors.ai (opens in a new window)
Name
Description
Duration
_fuid
It is sent to capture session details and track user behavior across your website to provide behavioral data and intent signals.
1 Year
Toggle Google AnalyticsGoogle Analytics
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Service URL: policies.google.com (opens in a new window)
Name
Description
Duration
FPGSID
Stores a session or user identifier to track how visitors interact with a website. This helps Google Analytics measure website performance, user engagement, and usage patterns.
Session
FPLC
Used by Google Analytics to link visitor interactions and sessions across multiple related domains.
20 hours
FPID
A server-side Google Analytics cookie used as an alternative user identifier when third-party cookies are restricted.
2 years
_ga
ID used to identify users
2 years
_ga_
ID used to identify users
2 years
Toggle Jetpack StatsJetpack Stats
Jetpack's built-in visitor analytics. It records page views, referring sites, search terms, and outbound link clicks, and also carries the shared visitor-tracking library used by Jetpack Instant Search and WooCommerce Analytics.
Service URL: automattic.com (opens in a new window)
Name
Description
Duration
tk_aip
Stores a list of anonymous visitor IDs so they can be merged into one identity once a visitor is recognized.
Up to 5 years
tk_tc
Used once per page load to work out which cookie domain the Tracks library should use, then removed as soon as it's read back.
Session (deleted immediately after use)
tk_qs
Queues analytics events for Jetpack's Tracks library so none are lost if the page closes before they can be sent.
30 minutes
tk_ai
Stores a randomly-generated anonymous visitor ID so Jetpack's Tracks analytics library can link tracking events to the same visitor.
Session in wp-admin; up to 5 years on the frontend
Toggle Microsoft ClarityMicrosoft Clarity
Clarity is a web analytics service that tracks and reports website traffic.
Service URL: clarity.microsoft.com (opens in a new window)
Name
Description
Duration
CLID
Identifies the first-time Clarity saw this user on any site using Clarity.
12 months
ANONCHK
Indicates whether MUID is transferred to ANID, a cookie used for advertising. Clarity doesn't use ANID and so this is always set to 0.
Session
_clck
Persists the Clarity User ID and preferences, unique to that site is attributed to the same user ID.
12 months
_clsk
Connects multiple page views by a user into a single Clarity session recording.
12 months
Toggle Parse.lyParse.ly
Parse.ly is a content analytics platform that helps publishers optimize audience engagement and content performance.
Name
Description
Duration
cookies.js_dtest
This cookie determines whether the browser accepts cookies.
session
_parsely_session
JSON document storing information identifying a browsing session according to Parsely’s proprietary definition
30 minutes
_parsely_visitor
JSON document uniquely identifying a browser and counting its sessions
13 months
Toggle SalespanelSalespanel
Salespanel is a B2B marketing and sales software that identifies, tracks, and qualifies website visitors and leads in real-time using first-party data. It helps businesses monitor customer journeys, score leads based on behavior, and syncs this data with CRMs (like Pipedrive or HubSpot) to improve conversion rates.
Service URL: salespanel.io (opens in a new window)
Name
Description
Duration
track_uid
Identify and tracking a lead
12 moths
Toggle MarketingMarketing
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Toggle Bing / MicrosoftBing / Microsoft
Bing, powered by Microsoft, is a search engine providing web, image, video, and map search capabilities.
Name
Description
Duration
MR
Used to collect information for analytics purposes.
6 months
ANONCHK
Used to store session ID for a users session to ensure that clicks from adverts on the Bing search engine are verified for reporting purposes and for personalisation
10 minutes
SM
Used by Microsoft in synchronizing the MUID across multiple Microsoft domains to track users for advertising.
session
MUID
Identifies unique web browsers visiting Microsoft sites. These cookies are used for advertising, site analytics, and other operational purposes.
1 year
Toggle DoubleClick/Google MarketingDoubleClick/Google Marketing
A comprehensive digital advertising platform for managing campaigns, optimizing performance, and analyzing audience data.
Name
Description
Duration
IDE
This cookie is used for targeting, analyzing and optimisation of ad campaigns in DoubleClick/Google Marketing Suite
2 years
ar_debug
Store and track conversions
Persistent
Toggle LinkedInLinkedIn
LinkedIn is a professional networking platform for job seekers, employers, and industry connections.
Name
Description
Duration
bscookie
Used by LinkedIn to track the use of embedded services.
1 year
AnalyticsSyncHistory
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries
30 days
bcookie
Used by LinkedIn to track the use of embedded services.
1 year
li_sugr
Used to make a probabilistic match of a user's identity outside the Designated Countries
90 days
lidc
Used by the social networking service, LinkedIn, for tracking the use of embedded services.
1 day
UserMatchHistory
Used by LinkedIn Ads to synchronize and match user IDs across different ad networks and data providers.
30 days
Toggle LinkedIn InsightLinkedIn Insight
LinkedIn Insight is a web analytics service that tracks and reports website traffic.
Service URL: www.linkedin.com (opens in a new window)
Name
Description
Duration
li_sugr
Used to make a probabilistic match of a user's identity.
90 days
lidc
Used for routing and session management.
24 hours
Toggle LiveIntentLiveIntent
LiveIntent provides a platform for email advertising and identity-driven marketing solutions.
Name
Description
Duration
_lc2_fpi_js
Companion cookie to _lc2_fpi used by JavaScript to facilitate cross-domain ad tracking and user identification.
1 year
_lc2_fpi
First-party tracking cookie usually associated with LiveRamp to identify users across devices for targeted advertising.
1 Year
_li_ss
Sets a unique ID for the visitor, that allows third party advertisers to target the visitor with relevant advertisement. This pairing service is provided by third party advertisement hubs, which facilitates real-time bidding for advertisers.
1 month
lidid
Collects data on visitors' behaviour and interaction - This is used to make advertisement on the website more relevant. The cookie also allows the website to detect any referrals from other websites.
2 years
Toggle Cookie PolicyCookie Policy
You can find more information in our Privacy Policy.
Allow AllDecline All
Accept