/resources/umbraco-wordpress-migration/
What We Do
Digital Platform MigrationsKey SolutionsManaged ServicesStaffing SolutionsIndustriesProducts
OnePress
Unify multiple brands on one governed WordPress platform.
Design & UI/UX
Gutenberg-native UX, UI, and design systems for visitors and editors.
WordPress Modernization
Modernize WordPress for better performance, architecture, and AI readiness.
WordPress as a DXP
WordPress as a composable DXP when monolithic systems no longer cut it.
Headless WordPress
Omnichannel content delivery without sacrificing marketing autonomy.
Frappe/ERPNext
Build scalable ERP and custom applications, from implementation to ongoing support.
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 Umbraco to WordPress migration guide: Costs, risks, and when it’s worth doing
Topics
On this page
- Umbraco to WordPress migration guide: Costs, risks, and when it's worth doing
- Migration process, timeline & team
- Pre-migration setup
TL;DR
Why teams leave Umbraco
Reason #1: The upgrade path is a rebuild
Reason #2: Routine editorial work requires development tickets
Reason #3: Narrow supplier pool
When staying on Umbraco is the right call
The cost of staying on Umbraco
Build your own 5-year comparison
The main migration risk is in how you leave
The risk of not migrating
How to prepare: the 8 weeks before migration
How the migration usually runs
What about AI?
Migrate with a partner you trust
FAQ
What happens when Umbraco 13 reaches the end of life?
Is Umbraco 13 still supported right now?
We are still on Umbraco 8. How urgent is this?
Should we upgrade to Umbraco 17 or migrate to WordPress?
How much does Umbraco cost per year?
How much does an Umbraco to WordPress migration cost?
How long does an Umbraco to WordPress migration take?
Will we lose SEO rankings when we migrate?
Is WordPress secure enough for enterprise?
Last updated on Sep 22, 2026
Umbraco to WordPress migration guide: Costs, risks, and when it’s worth doing
Most teams running Umbraco 13 have 14 December 2026 marked in their calendars. Feels like there’s still plenty of time left before the EOL comes, but it’s not quite right.
Umbraco 13 stopped receiving bug fixes in December 2025 and has been on security patches only ever since, so the version has already spent 8 months without maintenance. What’s more, .NET 8 loses Microsoft support in November 2026, a month before Umbraco. So the window is shorter than suggested.
Another surprise is the upgrade quote. Umbraco 14 replaced the entire back-office architecture, so custom property editors, dashboards, and extensions built for version 13 have to be rewritten.
These are just some reasons companies consider migrating from Umbraco. If you’re one of them and are evaluating WordPress as an alternative, this guide covers everything you need to know. You’ll see what Umbraco costs vs WordPress, how long a WordPress migration takes, and the migration risks you should know about upfront.
TL;DR
- Umbraco 13 loses security patches on 14 December 2026. It has been on security-only support since December 2025, and .NET 8 underneath it loses Microsoft support a month earlier, in November 2026.
- 3 options if you are on Umbraco: buy Extended Long-Term Support in 6, 12 or 24-month blocks, upgrade to Umbraco 17 LTS, or change platform.
- The upgrade to Umbraco 14 is basically a rebuild. Umbraco 14 replaced the backoffice architecture, so custom property editors, dashboards, and extensions built for version 13 have to be rewritten.
- Umbraco gets expensive at thresholds. Cloud Starter is €45 ($55) a month and includes no staging or SLA. Standard is €280 ($330). Forms, Workflow, Commerce, and Engage are separate annual licences, and support plans run €11,000 (
$13,000) to €18,800 ($22,200) a year. - Stay on Umbraco if you already run a Microsoft estate with an in-house .NET team, you depend on multilingual variants in a single installation, or you have already moved to Umbraco 17.
- Migration risk is execution risk. Traffic loss comes from incomplete redirect maps and dropped metadata that are completely avoidable. VinSolutions moved off Kentico with every SEO page rank preserved and Core Web Vitals up 48%.
- The typical migration timeline is 3-4 months from discovery to post-migration period. See the full phase-by-phase breakdown for more detail.
Why teams leave Umbraco
Umbraco is a well-engineered .NET CMS. So why do companies leave it? Here are the 3 main reasons.
Reason #1: The upgrade path is a rebuild
Umbraco has shipped two major versions a year since version 9. Standard-term releases get 12 months of life in total, and only every 4th release is an LTS, on a schedule that follows Microsoft’s .NET cycle instead of your roadmap.
Version 14 replaced the editing interface outright, swapping AngularJS for Web Components and removing the controller routes under /umbraco/api, so every custom property editor and dashboard built before it had to be rewritten.
That means the path from 13 to 17 is a rebuild for any implementation with custom work. Naturally, if you are funding the work either way, why not migrate to another platform?
Reason #2: Routine editorial work requires development tickets
Document types are defined through the back office by developers. There is no drag-and-drop page building in the core. Adding a field or changing a layout is typically a ticket, and the quality of editing depends entirely on how much care the original build team invested in it.
Dealertrack ran into the same constraint on Adobe Experience Manager, where nearly every content change required a developer. After migrating to WordPress VIP with a visual editing setup, the time it took to get a landing page live dropped by half.
Reason #3: Narrow supplier pool
.NET talent concentrates inside enterprise Microsoft estates rather than on the open market, and Umbraco specialists are a subset of that subset. For comparison, Umbraco runs on under 0.1% of all websites, while WordPress runs on 40.7% and holds 58.9% of the CMS market, according to W3Techs in August 2026.
Source: W3Techs in August 2026
Supply determines how long a role stays open, how many suppliers can credibly bid on your work, and how much leverage you have at renewal. When the one person or the one agency that understands your implementation leaves, the replacement search is hard, and that is one of the migration triggers.
But of course, there are cases when staying is worth it. Here are some of them.
When staying on Umbraco is the right call
Here are the situations where Umbraco is the correct answer and a migration would be a waste of budget:
- You already run a Microsoft estate. If Azure, SQL Server, Active Directory and an in-house .NET team are already in place, most of the infrastructure and talent argument disappears. The CMS is consistent with everything else you own.
- You need to be multi-site and multilingual in a single installation. Field-level language variants with fallback behaviour and independent content trees with domain routing are first-class in Umbraco.
- You value a zero-licence core. Umbraco’s core is MIT-licensed regardless of traffic, seats or API calls, with content in a standard SQL database. Self-hosting removes vendor dependency entirely.
- You recently moved to Umbraco 17 LTS. That version runs on .NET 10 and is supported until 27 November 2028. The trigger is 2 years away, and there is nothing to decide yet.
If 2 or more of these describe your company, the best decision might be to stay on Umbraco. But before deciding on it, let’s analyze the cost of it.
The cost of staying on Umbraco
Umbraco isn’t expensive at the start. It becomes expensive at thresholds, and most enterprises cross several of them within the first 2 years.
5 typical thresholds on UmbracoThresholdWhat it costsYou need staging and an SLAUmbraco Cloud Starter is €45 ($55) per month and includes neither. Multiple environments and the website and delivery API SLA begin at Standard, €280 ($330) per month. You need dedicated performanceCloud Professional runs €730 ($900) per month. Self-hosting instead means SQL Server plus Windows and ASP.NET-capable hosting or containers, where a modest Azure App Service, Blob Storage and Azure SQL configuration runs around £200 ($255) per month.Marketing asks for a capabilityForms is licensed at €100 ($120) plus €65 ($80) per extra domain. Workflow is **€2,800 ($3,300)** a year, Commerce €2,800 (~$3,300) a year. Personalisation, segmentation, A/B testing and on-site analytics all require Umbraco Engage.You want guaranteed supportProfessional support is €11,000 (~$13,000) a year. Standard Enterprise support is €18,800 (~$22,000) a year.An LTS version reaches end of lifeExtended Long-Term Support in blocks of 6, 12 or 24 months, or a funded upgrade, or a platform change.
Cloud tier prices ($55/$330/$900) are Umbraco’s US-facing rates as published at umbraco.com/pricing. Add-on and support-plan USD figures are estimates based on Umbraco’s EUR list prices plus the ~18% US premium Umbraco applies on its Cloud tiers; actual invoiced amounts should be confirmed at checkout on umbraco.com.
Prices adjust every 1 January. The 2026 round moved Cloud Professional from €700 ($850) to €730 ($900) a month, Commerce from €2,520 ($3,000) to €2,800 ($3,300) a year, and Forms from €170 ($200) to €200 ($235).
Umbraco tiers as of 2026. Source: Umbraco.com
Assembled, a mid-sized estate on Cloud Standard with Forms, Workflow and a professional support plan is into 5 figures annually without development work.
Build your own 5-year comparison
Fill in the left column against your contract. The right column shows a mid-sized estate for reference.
Budget lineYour figureExampleHosting or Cloud tier over 60 months€280 ($330) per month, €16,800 ($19,800)Add-on licences over 5 years, with annual escalationForms, Workflow and Engage, roughly €45,000 (~$53,000)Support plan over 5 years€11,000 ($13,000) a year, €55,000 ($65,000)Major upgrade or rebuild events in the windowOne version 13 to 17 rebuildDevelopment hours spent maintaining the platform rather than building on it0.5 full-time engineer(~$67,000/year, $335,000 over 5 years)Publishing delay: campaigns and pages waiting on developer capacityYour estimateFive-year total**€116,800** ($137,800) before rebuild, FTE, and delay costs
If your 5-year total looks like another reason to migrate, you have to consider the main migration risk: lack of preparation.
The main migration risk is in how you leave
Migration itself is not a risk, but an uncontrolled migration sure is. Poorly executed migrations typically lose between 10% and 30% of organic traffic, with recovery measured in months.
But each of these has a countermeasure:
RiskWhy it happensCountermeasureContent mapping errorsDocument types, nested content, and block grids rarely map one-to-oneMapping sheet completed during discoverySEO lossMeta titles, descriptions, alt text, and structured data don’t transfer automaticallyComplete URL inventory, field-by-field metadata mapping validated against source, redirect chain validation, canonical preservation, and a full crawl simulation Custom functionality with no equivalentRazor macros, custom property editors and .NET components have no direct WordPress analogueDecide rebuild, replace or retire for each item before development startsData lossMedia is in Azure Blob Storage, form entries in Umbraco Forms, and revisions and author records in the databaseFull backup with a rehearsed restore. Batch migration with a validation gate at each stageIntegration breakageCRM, marketing automation, analytics and DAM connections get rebuilt late in the projectIntegration inventory in week one, then rebuild and test against production traffic volumes before cutoverEditorial rejection at launchThe team is trained after go-live instead of before itTraining during user acceptance testing, documentation as a delivery item, and 30 days of hypercare after launch
If you doubt that it will solve the issue, there are multiple examples in our team’s experience of how companies preserve all ratings during migrations.
VinSolutions moved from Kentico to a WordPress VIP multisite with every SEO page rank preserved and Core Web Vitals improved by 48%. FleetNet America moved off Drupal 9 and Acquia in a matter of weeks with SEO preserved. The PageSpeed score nearly doubled, from 48 to 93, while Core Web Vitals improved from Failed to Passed.
Such outcomes came from mapping the URLs before writing code. And let’s not forget that in many cases no migration is a risk itself.
The risk of not migrating
The risk is not that Umbraco stops working on 15 December 2026, as it will keep serving pages. However, maintaining an ageing implementation takes a growing share of the roadmap.
- Unsupported versions stop receiving security patches, and that becomes a problem. If a vulnerability is disclosed in January 2027, there will be no patch for Umbraco 13 without Extended Long-Term Support.
- Umbraco 13 has been security-only since December 2025, so the bug-fixing stopped long ago.
- Every major upgrade requires custom code and package compatibility checks. The more customization you have, the larger the budget will be.
- On a legacy implementation, an upgrade is closer to modernisation than to maintenance, which opens the platform decision anyway.
There is one more consideration. Umbraco holds ISO 27001 certification but doesn’t currently pursue SOC certification. In healthcare, financial services, and the US public sector, this can end a conversation independently of product quality. Meanwhile, rtCamp is SOC 2 compliant and ISO 27001 certified, and WordPress VIP carries its own compliance coverage.
How to prepare: the 8 weeks before migration
The quality of a migration is settled before anyone writes code. 4 things need to happen first, and they run comfortably in 2 months.
- Take inventory. Export the full URL list from server logs, your XML sitemap, and Google Search Console, then reconcile all three. At the same time, pull the document type list with a count of how many content nodes use each one, and list every custom property editor, macro, Razor view and installed package with a decision against it: rebuild, replace or retire. Do the same for integrations, naming an owner and an authentication method for each, and locate your media assets physically, including anything sitting in Azure Blob Storage behind a CDN.
- Set a baseline. Without one, there is no way to defend the project 6 months later. Record Core Web Vitals per template from field data, organic sessions and your top 100 ranking URLs, and conversion rate on the top 20 commercial pages. Then record the time from content request to published page across the last 10 requests.
- Make the scoping decisions. Choose whether this is a lift-and-shift, a redesign, or a phased move. Preserve the existing URL structure unless there is a documented reason to change it. Decide what to retire, since most Umbraco estates carry 20% to 40% of pages nobody has opened in a year. Agree who can publish what, and who owns the component library after launch.
- Name people and stand up environments. Migrations stall on unresolved decisions far more often than on technical problems. Build a development environment that mirrors production with Git-based deployment and CI/CD, take a full backup of the database, media, and custom code, and rehearse the restore.
Our pre-migration setup guide covers each of these in full, including the content-mapping sheet and the pre-migration SEO checklist. Here’s how it typically runs when you migrate from Umbraco to WordPress.
How the migration usually runs
Most enterprise migrations run 3 to 4 months.
PhaseWeeksWhat happens****What you getDiscovery and analysis1–2Audit of frontend templates, backend logic, integrations, content types and media structureA discovery report and migration blueprintApplication design2–4Umbraco features mapped to WordPress equivalents, theme architecture, content models, workflow mappingSigned architecture and content modelDevelopment and unit testing3–8Block library, custom functionality, role-based permissions, third-party integrationsA working platform in stagingMigration script development2–8Document types to post types, parent-child hierarchies preserved, media and metadata transformedA repeatable import that can be re-run without manual cleanupSystem integration testing5–11Frontend components, backend logic and third-party systems tested togetherIntegration sign-off and early visibility of performance gapsContent migration7–12Bulk migration in validated batches with editorial review of layouts, embeds, linking and metadataConfirmed content parityUser acceptance testing10–13Stakeholder testing of workflows and backend usability, plus editorial trainingSign-off and a team that already knows the systemDeployment13–15Cutover, DNS coordination, delta content syncLive siteHypercare15–16 and beyondMonitoring, regression testing, bug resolution, documentation handoverStable operation and an internal team that can run it
The work runs in one line: audit the current estate, agree the architecture, build alongside the live site, migrate content in batches, cut over with a rollback ready, then stabilise and hand over.
rtCamp runs that sequence as the Delivery Model, which includes Audit, Pilot, Phased Build, Enablement, Hypercare, Evolution. We cover the process end-to-end with discovery, migration scripting, integration rebuild, SEO preservation, editorial training and 30 days of hypercare inside the same engagement.
In our separate guide, we cover the full process, week-by-week timeline, and team structure, in case you’re interested to learn more. Finally, let’s cover the last question companies can’t avoid: AI readiness.
What about AI?
Umbraco markets itself as the most agent-ready CMS, and parts of that claim are earned. The Umbraco.AI Foundation is a governance layer with profiles, guardrails, and logging, and the developer-facing MCP is live today.
But there are 2 things worth noting:
- The editor-facing MCP is still listed as coming soon; what ships today is tooling for developers. WordPress 7.0 shipped on 20 May 2026 with the AI Client, the Abilities API, a connectors hub, and an MCP adapter in core, across roughly 40% of the web.
- Assistants are only as fluent as the code they have seen, and a platform running on under 0.1% of the web is thinly represented in every public corpus. WordPress doesn’t have that problem.
Here’s how Umbraco compares to WordPress feature-wise:
CapabilityUmbracoWordPressAI governance layer (profiles, guardrails, logging)✅❌Bring your own API key, no vendor markup✅✅Developer MCP, agent access✅✅Editor-facing AI tools (drafting, alt text, translation)❌✅AI capability registry every extension can join❌✅AI ecosystem and public resources❌✅
What the table doesn’t show is that every row on the WordPress side depends on the same foundations a migration is rebuilding. Here we mean content architecture, structured data, and a governed platform. That’s why AI readiness belongs inside the migration.
If you are looking for an experienced migration partner, rtCamp can be the right fit. We contributed 3 AI connectors to WordPress 7.0, and cover strategy, architecture, and implementation in one scope.
Migrate with a partner you trust
rtCamp is an enterprise engineering company. We have delivered 500+ enterprise WordPress engagements, including migrations off Adobe Experience Manager, Sitecore, Kentico, Drupal, SharePoint, custom systems, and legacy .NET platforms. We are SOC 2 Type II compliant, ISO 27001 certified, a WordPress VIP Gold Partner and an Automattic Premier Partner.
You own the infrastructure, while we handle the engineering. WordPress core is open source, so you are not tied to a CMS license renewal. You can choose a managed hosting platform such as WordPress VIP, with hosting and platform costs based on the service you need.
Start with 20 hours of free discovery. We’ll map your current Umbraco architecture, identify the constraints, and help you build the internal business case before any contract is signed. If the audit shows that upgrading to Umbraco 17 is better in your situation, we’ll tell you that.
FAQ
What happens when Umbraco 13 reaches the end of life?
Umbraco 13 will stop receiving security patches on 14 December 2026. Your site keeps serving pages, but any vulnerability disclosed after that date goes unpatched unless you buy Extended Long-Term Support. For enterprises with audit obligations, cyber insurance requirements or contracts specifying supported software, that is a compliance problem.
Is Umbraco 13 still supported right now?
Only partially. Umbraco 13 moved to security-only support in December 2025, so it has not received a bug fix since then. Separately, .NET 8, the runtime it depends on, loses Microsoft support in November 2026, a month before Umbraco.
We are still on Umbraco 8. How urgent is this?
Umbraco 8 has been unpatched since February 2025 and Umbraco 7 since September 2023. Both are already exposed. The version 8 to version 9 jump moved the platform from .NET Framework to .NET Core, which means you have to rebuild regardless.
Should we upgrade to Umbraco 17 or migrate to WordPress?
It depends on how much custom backoffice work your implementation carries. Version 14 replaced the backoffice architecture, so custom property editors, dashboards, and extensions have to be rewritten. A near-standard implementation upgrades cleanly and at a low budget. An implementation with custom extensions costs more.
How much does Umbraco cost per year?
The core is MIT-licensed and free. Umbraco Cloud runs $55 a month for Starter, $330 for Standard and $900 for Professional, with staging environments and the delivery SLA beginning at Standard. Add-ons are separate: Forms as a ~$120/year subscription per license, Workflow at ~$3,300 and Commerce at ~$3,300. Personalisation and analytics require Umbraco Engage. Support plans run $13,000 to $22,000 a year. A mid-sized estate reaches five figures annually before any development work.
How much does an Umbraco to WordPress migration cost?
Depends on site count, integration count and the volume of custom .NET functionality. For a specific estimate, book a free discovery audit.
How long does an Umbraco to WordPress migration take?
Most enterprise migrations run 3-4 months from discovery to hypercare, with roughly 8 weeks of preparation.
Will we lose SEO rankings when we migrate?
Not if URL mapping is completed before development. Traffic loss during migration comes from incomplete redirect maps, dropped metadata and untested crawl paths, all of which are preventable. For example, VinSolutions moved from Kentico to WordPress VIP multisite with every SEO page rank preserved and Core Web Vitals improved by 48% at the same time.
Is WordPress secure enough for enterprise?
Yes. WordPress VIP carries enterprise compliance coverage, and rtCamp is SOC 2 Type II compliant and ISO 27001 certified. For comparison, Umbraco holds ISO 27001 and doesn’t offer SOC 2, a HIPAA business associate agreement or FedRAMP authorisation.
Migration process, timeline & team
NEXT
Credits
Aviral Mittal
Author
Aviral Mittal
Author
Aviral Mittal is the Chief Marketing Officer at rtCamp, where he established and leads the marketing function, building and growing a team of 20+ specialists across content, SEO, design, and growth…
Contributions and Updates: Usama 
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
_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
cookies.js_dtest
This cookie determines whether the browser accepts cookies.
session
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