/handbook/onepress/shared-plugin-stack/
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 Introducing OnePress Shared plugin stack
Topics
On this page
- Introducing OnePress
- Shared content hub
- Shared plugin stack
- Shared design system
- Centralized media management
- Share features across brands
- Centralized user access management
- Shared Martech stack
- Centralized personalization
- Network-wide multilinguism
- Get started with OnePress
- Frequently Asked Questions
Plugin centralization varies across OnePress deployments
1. A single plugin repository + selective activation
2. Centralized deployment with feature flags
3. General-purpose custom plugins
What does all this look like in practice? A real-world example
The real impact of a shared plugin stack with OnePress
SEO plugins
Forms plugins
Checkout plugins
Subscription management plugins
Marketing plugins (like email autoresponders)
OnePress plugin centralization: A few core themes
Plugin stack standardization: Your plugin policy, enforced
Your plugin stack managed like software
Controlled divergence: flexible where it counts
Conclusion
Last updated on Apr 1, 2026
How OnePress centralizes plugin management across all your brand sites
At the heart of OnePress is a centralized approach to plugin management. It’s built on the idea that managing plugins across brand sites shouldn’t mean duplicating effort. But centralization doesn’t mean rigidity.
And so OnePress doesn’t hardcode plugin management, it’s built to flex. The system is engineered to support multiple governance models, allowing you to centralize where it makes sense, and diverge where it’s needed.
And while individual implementations vary, some core principles remain the same: plugin stack standardization, software-style lifecycle management with DevOps-friendly pipelines, and controlled, policy-driven divergence.
This chapter unpacks how OnePress enables all of this.
Plugin centralization varies across OnePress deployments
OnePress isn’t hardcoded, it’s open, adaptable, and flexes to fit. As such, there’s no single right way to centralize plugin management across a network of sites. In other words: If OnePress is implemented for 10 clients, plugin centralization can take 10 different approaches. That said, here are just a few ways to go about plugin management with OnePress.
1. A single plugin repository + selective activation
Some setups use a common plugin repository where all plugins live, and brands enable what they need through central plugin loaders. These are usually accompanied by actions and filters that allow site-specific tweaks without forking the entire plugin.
2. Centralized deployment with feature flags
Another approach is to push the same plugin code to all sites, and use feature flags (configurable per brand or per environment) to toggle functionality on or off. This ensures a single source of truth and simplifies deployments, updates, and debugging. It’s a clean solution when you want to maintain strict plugin version control, but still need to customize what’s “on” for each site.
3. General-purpose custom plugins
Custom plugins, especially when built for a single brand, are often approached with future-proofing in mind. By writing modular logic and using filters/actions extensively, the plugin remains portable, even if initially built for one brand, it can be adapted and deployed elsewhere without a rewrite. OnePress generally encourages this mindset in platform builds: write like you’ll use it again, even if you never do.
What does all this look like in practice? A real-world example
When a OnePress client wanted to implement a centralized design system across their network of WordPress sites, we built a custom plugin. This plugin is centrally managed and “downstreamed” to the entire network of sites, powering its uniform design.
The real impact of a shared plugin stack with OnePress
Consistent brand experiences, repeatable compliance, faster time to market, and dramatically less technical debt. Here’s what that looks like for some of the most commonly shared plugin categories in a OnePress environment:
SEO plugins
Shared metadata structures, schema markup, and sitemap generation mean your entire network is search-optimized out of the box. No brand site needs to reinvent SEO foundations, they just inherit a strategy that works, and is centrally improved over time. Analytics are set up consistently too, making performance benchmarking across brands possible.
Forms plugins
Marketers across brands can spin up high-converting, brand-aligned forms in minutes (from lead gen to surveys) all pulling from pre-integrated CRM connectors. Meanwhile, local teams retain the ability to tweak field logic or language without breaking design or data structure.
Checkout plugins
Whether it’s a particular payment gateway integration plugin or regional options, centralized integration and management ensures all sites deliver a secure, compliant checkout experience that’s trusted and familiar. You’re not re-auditing the same plugin five different ways, you’re doing it once, and scaling that assurance everywhere.
Subscription management plugins
Instead of building separate access controls per site, you enforce membership logic from a shared system (the same plugin). That means global teams can roll out new gated features, pricing tiers, or customer flows without touching five different codebases. Less duplication, faster launches.
Marketing plugins (like email autoresponders)
When email automations like welcome series, cart abandonment nudges, or renewal reminders are handled via shared systems, you gain consistency in customer communications, but still allow for per-brand tone, language, or timing. Personalization on the edge, automation at the core.
OnePress plugin centralization: A few core themes
As such, OnePress approaches plugin management with an adaptive, context-driven approach.
However, across these varied implementations, certain core themes consistently emerge: a focus on plugin standardization to ensure consistency, a DevOps mindset that emphasizes quality deployments, disciplined governance to enforce policies, and flexible configurations that allow controlled site-specific variations.
This balance of flexibility and control enables OnePress to adapt to different environments while maintaining a reliable, scalable plugin management framework.
Plugin stack standardization: Your plugin policy, enforced
After working with a couple of OnePress clients, we’ve seen that most multi-brand large-scale WordPress setups already lean toward a “standard” plugin stack across their brand sites. The stack might not be shared (yet!) but it’s standardized, especially when it comes to key plugins.
So step one is generally building a curated baseline. Typically, every OnePress plugin centralization phase starts with a curated and approved list of plugins for, say, SEO, forms, payments, email triggers, subscription handling, analytics, and more.
These are vetted, secured, and aligned with your enterprise stack. Think of it as your global plugin policy, implemented technically.
Technically, OnePress addresses this by creating a shared plugin repository: your enterprise-wide “plugin commons” that serves every site in your multisite network or connected installations.
Your plugin stack managed like software
With plugin standardization in place, it’s time for management (customizations, updates, and more).
For these, OnePress treats your plugin stack like enterprise-grade software.
So you’re looking at:
- CI/CD pipelines that automate coding and deployment across your WordPress ecosystem
- Phased rollouts minimize risk and downtime
- Central dashboards provide real-time visibility into plugin health, usage, and updates
And more.
Controlled divergence: flexible where it counts
While the plugin base is shared, activation and config can diverge by site, based on what’s allowed:
- A regional site may use a different payment gateway
- A campaign microsite might activate specific tracking plugins
- Local teams can override default settings, within limits
OnePress supports this divergence with guardrails, so teams get what they need, but within defined boundaries.
Conclusion
Whether you’re standardizing a global plugin stack or managing selective feature rollouts, OnePress ensures that every plugin decision is scalable, secure, and sustainable across your entire network.
Credits
Disha Sharma
Author
Disha Sharma
Author
Disha Sharma is a Content Writer at rtCamp with over a decade of experience at the intersection of technology, digital marketing, and enterprise content strategy. Her WordPress roots run deep, her …
Shreya Agarwal
Editor
Shreya Agarwal
Editor
Shreya Agarwal is a Growth Engineer at rtCamp, she brings active, hands-on WordPress development credentials to everything she writes and reviews. A WordPress Core Contributor with merged pull requ…
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