Splitworthy documentation
WordPress installation
Install, pair, update safely and handle optimisation and consent plugins.
Install Experiment Connector
Download the ZIP from Overview or your website installation page. In WordPress open Plugins → Add New → Upload Plugin, upload the ZIP and activate it. Open Settings → Experiment Connector.
For an upgrade, upload over the existing plugin and choose replacement; do not delete it first. This preserves connection and privacy settings. Confirm the ZIP and installed version before testing. The current repository source is 0.5.0; older production downloads can differ until the platform is republished.
Pair and prove domain ownership
Generate a fresh pairing code from your website page and enter it in the plugin. Codes expire after 15 minutes and are single-use. The platform calls the plugin verification endpoint on the registered HTTPS domain; simply entering a site ID does not connect it.
A failed attempt may consume the code. Check the domain, HTTPS, public REST API access and published platform availability, then generate a new code. The private installation secret stays on the WordPress server and must never be copied into page source.
Connect your consent manager
Statistics consent is required by default. WP Consent API statistics allow/deny events are supported. For other banners, call the public methods only in response to the banner’s actual consent state. Visitors without required consent are not included.
// In your consent-manager callbacks, after the SDK exists:
window.expcon?.grantConsent(); // statistics accepted
window.expcon?.revokeConsent(); // rejected or withdrawnCaching, delayed scripts and first test
Purge page caches and optimisation caches after installation or updates. Autoptimize and LiteSpeed can serve HTML generated before the plugin was installed. Exclude expcon-sdk from delayed execution and check the resulting page source.
The engine is embedded early in the public page head. It is skipped in admin, previews, feeds and the Customizer. Slow consent/configuration or script optimisers can still cause a visible swap or missed exposure; zero flicker is not guaranteed.
Create a content experiment against the exact existing text on the chosen pathname. Confirm one matching element, consent, assignment, recorded exposure and goal. Test the local emergency switch and the website-level disable in your account.