Launching the Adbris WordPress plugin

We've shipped the Adbris WordPress plugin to the WordPress.org directory. Five minutes from install to live revenue, including header bidding and ad-block recovery. Here's what's in it and what we learned building it.

Why a plugin and not a snippet

"Just paste this script tag in your header" works fine for static sites and Next.js, but WordPress publishers expect plugins. Their workflow is: search the WP admin, install, configure, ship. Three of those steps fail with a raw script approach: discovery, slot configuration, and updates.

What the plugin does on activation

• Scans the active theme for known ad-slot positions (header, sidebar, in-content, footer)
• Writes a slot config back to your Adbris dashboard via our public API
• Renders the slots invisibly until ads arrive (no layout shift)
• Pre-loads our Prebid wrapper from the CDN, lazy-bound to viewport

The 5-minute install path

Apply to Adbris → get approved → install plugin → paste API key → done. Real-time average across the last 30 days of installs: 4m 47s from plugin activation to first impression served.

What surprised us building it

The hardest part wasn't the technical integration with WordPress — that's well-documented. It was the long tail of theme compatibility. Some themes (looking at you, page builders) use shortcode-based ad-zone systems that expect specific markup. We shipped a shortcode-level override so power users can place slots exactly where they want, but the auto-detect path covers ~85% of WP sites we tested.

What's next

• Gutenberg block for inline ad placement (Q3 2026)
• AMP-compatible ad units (Q3 2026)
• WooCommerce-aware slots (skip ads on checkout, etc.)

Where to get it

Search the WordPress plugin directory for "Adbris", or grab the self-hosted zip from your Adbris dashboard once you're approved. Free, always. The plugin is just the install surface — all revenue economics are governed by your Adbris account settings.