Roadmap

What shipped, what's being considered.

All ten server-side channels are live. Hybrid Mode runs on nine of them. The live dashboard, health score, anomaly detection and multi-currency reporting are all in production. The list below is what already shipped, plus three candidates being weighed against customer demand for the next major version.

Shipped: last six months

Live2026 H1

Four new server-side channels: Pinterest, Snapchat, Reddit, X Ads

All four shipped with full server-side dispatch, vendor-specific dedup keys (event_id for Pinterest and Snap, conversionId for Reddit, conversion_id for X), commerce-funnel coverage and admin Test-Event button. Total channel count is now ten.

Hybrid Mode rollout: nine of ten channels

Same-origin browser pixel that shares the server's event_id for vendor-side deduplication. Active for Meta, TikTok, Pinterest, Snapchat, Reddit, X Ads, LinkedIn (Insight Tag) and Microsoft Advertising (UET) plus Google Ads (gtag.js Audiences-only mode). Default off, opt-in per channel.

Live dashboard, health score, anomaly detection

Per-channel ringbuffer (last 50 events), 30-day per-channel-per-day counters, 0-10 health score (Configured + Active 7 d + Stable CoV<1), daily cron that mails on a 50 percent drop or 4x spike. All from two autoload=false options, no new wpdb table.

Multi-currency auto-conversion

ECB Daily Rates pulled once per day, normalises value and items[].price into the customer's target currency before fan-out. Original currency stays on the event for transparency in the Live-Dashboard recent-events table.

Hybrid Mode mirror for WooCommerce purchase + Fluent + Kadence forms

Server-side CAPI dispatch is mirrored to every loaded browser pixel with a shared event_id for vendor-side deduplication. WooCommerce purchases reuse the stable per-order bcnr_purchase_<order_id> id; form submissions inject a random bcnr_event_id hidden field at submit-time so the server picks up the same id from the form payload. Closes the Hybrid Mode gap for the three launch-verified integrations.

Polar-webhook pre-check: instant cancel and refund handling

A subscription-revoked or order-refunded webhook lands a KV marker on the broker within seconds. The plugin picks it up at the next hourly cron tick or instantly on a manual recheck. Latency from cancel to block dropped from up to 24 h to under 1 h.

Google Ads OAuth-broker: no developer-token wait

Beaconry's central broker on oauth.beaconry.app carries the developer token. Customers connect their Google Ads account in two clicks via OAuth and start uploading conversions the same day. DMA-Consent block included on every upload (EU-mandatory since 2024-03).

Public beta: ships in v1.0, customer feedback drives stabilisation

Beta2026 H1

Five more form-plugin adapters: Contact Form 7, Elementor, Gravity, Ninja, WPForms

All five ship fully implemented in v1.0 with the same submission-hook + PII-hashing pattern as Fluent and Kadence. They await end-to-end validation with real submissions plus match-quality checks before losing the Beta badge in the plugin UI. Customer bug reports drive the order. Fluent and Kadence remain the launch-verified pair.

Easy Digital Downloads + SureCart commerce adapters

Both adapters cover the standard commerce funnel (view_item, add_to_cart, begin_checkout, purchase, refund) with line items + customer PII hashing into the user_data block of every channel. WooCommerce is the launch-verified path; EDD and SureCart are flagged Beta in the UI until a real customer order with match-quality reporting has run through them.

Under consideration

Customer-feedback driven2026 H2 / 2027

Agency mode: central dashboard across customer sites

Optional roll-up dashboard for agencies running Beaconry on multiple customer installs. Per-site health score, central anomaly alerts, plugin-version-fleet view. License-tier gated.

Server-side audience sync

Direct Customer-Match (Google Ads) and Custom-Audience (Meta) uploads of hashed first-party PII from WooCommerce, EDD and SureCart customer lists. Currently the browser-side tag handles audience cookies. This would let server-side replace tag-only audiences entirely.

WP-CLI commands

wp beaconry health, wp beaconry test-event <channel>, wp beaconry backfill-orders. Useful for agency rollouts and CI smoke-tests on staging environments.

Custom-Events JS API for the Custom-Tracking tab

Public bcnr.track('event_name', {…}) entry point for theme + plugin developers. Same server-side fan-out path as Click-Tracking — any third-party integration can fire a typed conversion event without touching wp_remote_post. Click-Tracking (v0.19.56) was step one; this is the formal API.

Outbound auto-tracking per domain pattern

Configure a pattern like *.amzn.to/*affiliate_click in the Custom-Tracking tab — every visitor click on a matching outbound link fires the event automatically, no per-link class needed. Useful for content sites with hundreds of affiliate links across legacy posts.

Auto-event toggles + engagement thresholds

Granular off-switches for each nl-data auto-sensor (page-view, scroll, video, file-download, form-start, contact, outbound, user-engagement). Plus configurable thresholds: 10 s default for the engagement gate, scroll-percentage triggers, video-progress milestones. Lets customers tune the signal volume per site without forking the engine.

"Under consideration" items are weighed against customer feedback. Order and inclusion depend on demand. They move out of consideration into "In progress" only when work actually starts. Got an opinion? Tell us.

Ready to start collecting first-party conversions?

Ten channels are live today, nine of them with Hybrid Mode dedup. The roadmap is what's next, not what you wait for.