Technical Documentation

Content Revenue Engine (CRE) is a rule-based monetization engine for WordPress designed to turn editorial content, premium articles, reports, research, newsletters and knowledge assets into revenue through deterministic access logic.

CRE combines a metered paywall, granular access rules, Pay-Per-Post monetization, integrated subscriptions through Access+, dynamic CTA rendering, editor-level controls, licensing infrastructure and builder-safe frontend behavior within a single system.

Rather than stacking separate tools for paywalls, memberships and premium content, CRE is built to evaluate access consistently across multiple monetization models — reducing conflicts, duplicated logic and unpredictable behavior.

This technical documentation explains the current architecture, access evaluation flow, plugin structure, data model, Pay-Per-Post logic, Access+ integration, licensing layer, frontend rendering behavior, compatibility considerations and developer extensibility.

Table of Contents

  1. Overview
  2. Free and Pro Editions
  3. Architecture
  4. Plugin Structure
  5. Data Storage Model
  6. Access Evaluation Flow
  7. Metered Paywall Engine
  8. Counter Logic and Visitor State
  9. Notice and CTA System
  10. Exemptions Engine
  11. Unlimited Access and Bypass Logic
  12. Paid Memberships Pro (PMPro) Compatibility
  13. Pay-Per-Post (PPP) – Pro
  14. Deterministic Price Resolution
  15. Access+ Subscriptions
  16. Editor Integration and Post-Level Controls
  17. Shortcodes and Frontend Monetization Blocks
  18. Elementor and Builder-Safe Rendering
  19. Licensing, Validation and Billing
  20. Frontend Rendering Behavior
  21. Security and Validation
  22. Compatibility
  23. Performance Design
  24. Developer Hooks and Filters
  25. Advanced Use Cases
  26. Deployment Checklist
  27. Technical Summary

1. Overview

Content Revenue Engine is a monetization framework for WordPress built around explicit access rules rather than membership-first assumptions.

Its purpose is to determine whether content should be:

  • freely accessible,
  • counted under a metered paywall,
  • excluded from the meter,
  • sold as Pay-Per-Post content,
  • unlocked through subscription access,
  • unlocked through role or membership bypass,
  • or rendered with contextual notices and conversion CTAs.

CRE is designed for publishers and premium content businesses that need more than simple restriction rules. It provides a structured monetization layer where access, pricing and conversion work together inside one system.

Back to top

2. Free and Pro Editions

2.1 Free Edition

The Free edition focuses on the metered layer and base access control. It typically includes:

  • Metered paywall
  • Exemptions engine
  • Role-based bypass
  • Dynamic notices and CTA behavior
  • Core configuration interface

2.2 Pro Edition

The Pro edition extends CRE into a broader monetization system. It typically adds:

  • Pay-Per-Post monetization
  • Paid rules by post, category and tag
  • Integrated subscriptions through Access+
  • Licensing and validation infrastructure
  • Billing and upgrade flows
  • Enhanced admin controls and monetization workflows
  • Builder-safe premium rendering options

The architectural goal is for both editions to share the same monetization philosophy, while Pro introduces premium monetization layers and commercial infrastructure.

Back to top

3. Architecture

CRE follows a modular rule-engine architecture designed to keep monetization behavior deterministic and extensible.

3.1 Core logical layers

  • Options Manager
  • Paywall Engine
  • Exemptions Engine
  • Pay-Per-Post Engine (Pro)
  • Access+ Subscription Layer (Pro)
  • Licensing Layer (Pro)
  • Admin UI Layer
  • Editor Integration Layer
  • Frontend Rendering Layer

3.2 Why this architecture matters

By separating the meter, exemptions, pricing logic, subscription access, licensing and rendering behavior, CRE avoids many of the conflicts commonly caused by stacking unrelated plugins together.

This modular design also supports future extensibility without breaking the core monetization flow.

Back to top

4. Plugin Structure

The system is centered around the main content-revenue-engine plugin, with premium functionality loaded inside the same architecture.

4.1 Typical structure

content-revenue-engine/
content-revenue-engine.php
includes/
    class-cre-paywall.php
    class-cre-counter.php
    class-cre-licensing.php
    class-cre-admin.php
    class-cre-ui-extras.php
modules/
    access_plus/
        bootstrap.php
        includes/
            class-cre-subscriptions-addon.php
assets/
    js/
    css/

4.2 Structural principle

CRE Pro extends the same plugin architecture rather than creating disconnected monetization systems. Access+, licensing and premium logic are integrated into the core evaluation flow.

Back to top

5. Data Storage Model

CRE uses a hybrid configuration model that balances centralized rule evaluation with content-level flexibility.

5.1 Global configuration

The main global configuration is stored in a single WordPress option:

content_revenue_engine_options

5.2 Content-level overrides

Selected editorial decisions are stored through post meta, for example:

_cre2_exempt_counter
_cre2_ppp_enabled
_cre2_ppp_price

5.3 Design principle

A single global options model keeps access logic centralized, while post-level overrides remain available for editorial control where needed.

Back to top

6. Access Evaluation Flow

CRE evaluates access in a strict and deterministic order. This is one of the most important technical principles in the system.

6.1 Canonical evaluation order

  1. User has unlimited access or bypass?
  2. Content is exempt from the meter?
  3. Content requires Pay-Per-Post access?
  4. Content requires Access+ subscription access?
  5. Metered paywall limit reached?
  6. Otherwise allow access

6.2 Why evaluation order is critical

Strict evaluation order ensures predictable behavior across complex monetization models. Premium content should not be treated like generic metered content, and subscription rules should not create separate access systems.

Back to top

7. Metered Paywall Engine

The metered paywall controls how many eligible pieces of content a visitor can consume before restrictions apply.

  • Time-based limits by day, week or month
  • Progressive notice thresholds
  • Only eligible content should count
  • Previously read content should not count twice
  • Paid content should not distort the meter
Back to top

8. Counter Logic and Visitor State

The CRE counter is designed around editorial fairness and predictable monetization behavior.

  • Count only new content
  • Ignore revisits
  • Ignore exempt content
  • Ignore PPP content
  • Reset when the configured period changes

A post already read in the current period should remain accessible even after the meter is exhausted.

Back to top

9. Notice and CTA System

CRE includes a contextual messaging layer designed to support monetization without cluttering the frontend.

  • Dynamic remaining-access notices
  • Context-aware CTA messaging
  • Configurable notice states
  • Single primary conversion path per context
Back to top

10. Exemptions Engine

Exemptions prevent content from consuming the meter or being blocked by the paywall.

  • Category-based exemptions
  • Tag-based exemptions
  • Individual content exemptions
  • Post meta overrides

Exemptions are useful for SEO content, landing pages, onboarding content and strategic free layers within a hybrid monetization model.

Back to top

11. Unlimited Access and Bypass Logic

CRE supports explicit bypass logic for users who should not be restricted by the meter and, depending on configuration, by premium rules.

  • WordPress role-based bypass
  • Conditional bypass logic
  • Membership-aware bypass where configured
Back to top

12. Paid Memberships Pro (PMPro) Compatibility

CRE supports conditional integration with Paid Memberships Pro when PMPro is active.

PMPro can be used as an external membership layer while CRE continues to control monetization logic, paywall rules and premium access behavior.

This allows hybrid models such as:

  • metered access for anonymous readers,
  • PPP for premium individual content,
  • membership bypass for selected audiences.
Back to top

13. Pay-Per-Post (PPP) – Pro

Pay-Per-Post allows selected content to be monetized independently of the metered paywall.

  • Individual paid posts
  • Paid categories
  • Paid tags
  • Per-post editorial overrides

This makes CRE suitable for premium articles, reports, frameworks, research pieces and other high-value content assets.

Back to top

14. Deterministic Price Resolution

CRE uses a strict pricing hierarchy to avoid ambiguity when multiple monetization rules apply.

  1. Post-specific price
  2. Category-specific price
  3. Tag-specific price
  4. Default price

This ensures predictable results and makes monetization logic easier to audit and support.

Back to top

15. Access+ Subscriptions

Access+ extends CRE Pro with integrated subscription-based access.

Rather than creating a separate membership system outside the engine, Access+ is designed to work within CRE’s runtime so that subscription restrictions, Pay-Per-Post and metered access can coexist under one evaluation model.

  • Subscription-based content access
  • Integrated access logic
  • Plan-based restrictions
  • Upgrade path from PRO
  • Frontend notices and gated content support
Back to top

16. Editor Integration and Post-Level Controls

CRE adds monetization controls directly into the content workflow so editors can manage access without editing code.

  • Exempt from meter
  • Mark as paid content
  • Define custom price
  • Apply content-level overrides
Back to top

17. Shortcodes and Frontend Monetization Blocks

CRE supports reusable monetization blocks through shortcodes and frontend components.

These can be used in content areas, landing pages, widgets and builder-based layouts to surface premium content and monetization paths consistently.

Back to top

18. Elementor and Builder-Safe Rendering

CRE is designed to avoid layout-breaking behavior in modern WordPress sites.

  • Elementor-safe rendering
  • Minimal wrapper injection
  • No duplicated monetization blocks
  • Separation between monetization logic and visual design
Back to top

19. Licensing, Validation and Billing

CRE Pro includes a licensing layer connected to the CRE Hub.

  • License activation
  • Domain validation
  • Billing portal access
  • Addon and upgrade handling
  • Subscription-aware feature validation

This makes CRE Pro part of a managed SaaS-style product architecture rather than a static premium plugin.

Back to top

20. Frontend Rendering Behavior

CRE injects monetization logic during content rendering while aiming to preserve theme and builder integrity.

  • Notice injection
  • Blocked-content replacement
  • PPP purchase rendering
  • Subscription gating support
  • Minimal layout disruption
Back to top

21. Security and Validation

CRE includes standard safeguards for admin actions, monetization settings and commercial flows.

  • Nonce verification
  • Strict price sanitization
  • ID casting and validation
  • Role verification
  • Domain validation in licensing and billing flows
Back to top

22. Compatibility

  • Standard WordPress environments
  • Gutenberg editor
  • Classic Editor
  • Elementor-safe rendering
  • Conditional PMPro compatibility
Back to top

23. Performance Design

CRE is built to remain lightweight in the content delivery path.

  • Short-circuit rule evaluation
  • Centralized option lookups
  • Minimal unnecessary queries
  • Deterministic access decisions
Back to top

24. Developer Hooks and Filters

CRE exposes actions and filters that allow developers to extend monetization behavior without modifying core plugin files.

These extension points are intended for custom access logic, CRM integrations, analytics, payment customizations and frontend monetization enhancements.

Back to top

25. Advanced Use Cases

  • Metered editorial sites
  • Premium research publications
  • Hybrid PPP + subscription models
  • Knowledge businesses and expert content funnels
  • Builder-driven premium content sites
Back to top

26. Deployment Checklist

  1. Configure paywall rules
  2. Define exemptions
  3. Configure PPP rules
  4. Configure Access+ if used
  5. Review notices and CTAs
  6. Validate billing and licensing flows
  7. Test multiple user states
Back to top

27. Technical Summary

Content Revenue Engine is not just a paywall plugin. It is a structured monetization engine for WordPress designed to provide publishers and developers with deterministic access logic, flexible pricing models, subscription-aware access, builder-safe rendering and commercial infrastructure.

CRE separates monetization logic from presentation while still giving editors and site owners precise control over how content is accessed, sold and converted into revenue.

Content Revenue Engine
Technical monetization infrastructure for serious publishers.

Back to top