Resolve a context from the domain
Domain Context Router exposes a context through PHP filters on one installation with several domains. Your developer configures DNS, HTTPS and caching. Data and users remain shared; no settings screen is provided.
Compare uses
Domain Context Router exposes a context through PHP filters on one installation with several domains. Your developer configures DNS, HTTPS and caching. Data and users remain shared; no settings screen is provided.
Campaign Overlay Manager connects a schedule and contexts to a closable dialog. Hypothetical example: announcing a temporary closure. Frequency depends on sessionStorage; contexts require configuration and Woo transactional pages are excluded by default.
Consent-Aware Domain Analytics waits for your manager’s statistics choice before loading Google tag or GTM. You provide the banner and Google configuration. GTM remains blocked on recognised receipts and private routes; no anonymous collection or universal compliance is promised.
The Event Outbox stores emitted events, shows attempts and allows retries. A developer connects emission and the receiver, which must deduplicate. Up to ten delivery attempts precede the retryable failed state; remote delivery is not guaranteed.
WordPress 6.3+ and PHP 7.4+ are required. Check each product’s dependencies. Choosing several modules adds no automatic integration or included external service.
Separate extensions
Open the relevant product pages to compare features, limits and installation.
The checkout review currently opens in French. Contact us in English if you need help before purchasing. Written support is available in English and French.
The router is optional; without it, the default context is used.
Your developer defines the events to emit and configures their destinations.
Novelience
Developed and maintained by Novelience