Documentation FAQ
Longer answers than the homepage FAQ, organised by topic.
Licensing and billing
What does each tier include?
- Solo ($69): 1 production website. Lifetime updates. Email support.
- Studio ($149): 5 production websites. Lifetime updates. Priority email support.
- Agency ($349): unlimited production websites. Lifetime updates. Priority support and roadmap input.
Dev and staging activations are unlimited on every tier. Local builds, staging subdomains and pre-launch URLs do not count against your seat.
What's the refund policy?
14 days, no questions asked. If Beaconry doesn't work for your site, email us at info@beaconry.app and we refund via Polar.
How do plugin updates work?
Beaconry has a built-in self-hosted updater. After purchase, your license key is validated against Polar and the plugin polls a manifest at www.beaconry.app/downloads/beaconry.json for updates. Updates appear in the standard WordPress Plugins screen. No GitHub login, no FTP, no marketplace required.
Can I move a license to a different site?
Yes. Open Beaconry → Dashboard → License → Deactivate on the old site. The seat is freed within 1 hour. Activate the same key on the new site.
GDPR and privacy
Is Beaconry GDPR-compliant?
Beaconry gives you all the building blocks: consent gate, server-side hashing, no third-party tracker domains, encrypted credentials. GDPR compliance always depends on your full setup. You're responsible for your privacy notice, cookie disclosure and the lawful basis for processing.
What Beaconry handles for you:
- The bundled
nl-data-gateconsent banner respects EU "no implicit consent" rules. No event leaves the browser until the visitor accepts analytics. - PII fields sent to Meta, TikTok, Google Ads, LinkedIn (email, phone, name, ZIP, city) are SHA-256 hashed before transmission, per each platform's matching guidelines.
- Server access logs are kept 14 days max for security purposes only.
What data flows where?
From the browser:
- Consent state (
nl_prefcookie) and click-IDs (nl_extcookie) stay on your domain. - Event metadata (URL, page title, user agent, referrer, scroll depth) gets sent to your WordPress install.
From WordPress to platforms:
- Event metadata, hashed PII, and the per-channel click-ID (fbclid for Meta, ttclid for TikTok, etc.) are sent to the configured platform's official API.
- Each channel only receives data if you configured credentials for it. Disabled channels receive nothing.
What never leaves your WordPress:
- Raw email addresses or phone numbers (always hashed first).
- Your platform access tokens (encrypted in database, only sent server-to-server in HTTPS request headers).
- Your visitors' IP addresses are not transmitted to Beaconry's central servers (Beaconry does not have a central server that receives event data).
What does Beaconry's central worker know about my visitors?
Nothing. Beaconry's central Cloudflare Worker handles license validation and Google Ads OAuth proxying only. It never sees event data, never sees visitor info, never sees your platform credentials.
Where does my data live?
- WordPress database (your hosting): consent state, click-IDs, event log, encrypted platform tokens.
- Platform APIs (Meta, TikTok, Google, LinkedIn, Google Analytics): their normal storage. Subject to each platform's data-processing agreements.
- Beaconry's central worker: only your license key and site URL.
Infrastructure
What versions of WordPress and PHP are supported?
WordPress 6.4 or newer, PHP 8.3 or newer. Beaconry uses modern type-hints and enums, older PHP versions will fail activation.
Does Beaconry work with WooCommerce?
Yes. If WooCommerce is active, hooks for add_to_cart, begin_checkout and purchase register automatically. Order events include line items, currency and value. Purchase events use a stable per-order event_id for browser-pixel deduplication.
Which form plugins are supported?
Kadence Blocks Form and Fluent Forms are auto-detected. Submissions fire as generate_lead events with hashed PII for matching. Other form plugins (Contact Form 7, Gravity Forms, WPForms) can be wired up via the JS API: nlc.track('lead', {form_id: '...', email: '...', phone: '...'}).
Can I run Beaconry alongside Google Tag Manager?
You can, but it's usually counter-productive. GTM serves the same purpose Beaconry serves — Beaconry replaces GTM. Running both means double tracking and adblockers will block your GTM-served pixels anyway.
Recommended: pick one. Beaconry if you want adblock-immune server-side dispatch, GTM if you have an existing tag-template setup you can't migrate.
Does Beaconry work in WordPress multisite?
Yes. Activate per-site (not network-wide) and configure each site's credentials independently. Each multisite blog counts as one activation against your tier seat count.
Roadmap and feedback
What's coming next?
See the roadmap. Live conversion dashboard and health-score per channel are in progress for Q3 2026. Microsoft Advertising follows in Q4. Pinterest and X (Twitter) Conversions API are in concept for Q1 2027.
How do I influence the roadmap?
Agency-tier customers have a direct line via email. Solo and Studio customers can email info@beaconry.app with feature requests — items that come up across multiple customers go to the planned bucket faster.
Is there a public changelog?
Yes, beaconry.json always reflects the latest published version with version notes. The WordPress Plugins screen shows the same notes when an update is offered.