Is Beaconry GDPR-compliant?
Yes — by design. Beaconry ships with a built-in two-button consent banner (nl-data-gate): until the visitor accepts analytics, no events leave the browser and no requests are made. Consent state is stored in a first-party nl_pref cookie. PII fields sent to Meta CAPI (email, phone, name, ZIP, city) are SHA-256 hashed before transmission per Meta's matching guidelines. Server access logs are kept 14 days max for security purposes only — see our Privacy Policy. Note: GDPR compliance always depends on your full setup; Beaconry gives you all the building blocks (consent gate, hashing, no third-party domains, encrypted credentials), but you're responsible for your privacy notice and cookie disclosure.
Will adblockers block this?
No, by construction. The endpoint is /wp-json/beaconry/v1/event on your own domain. An adblocker that blocks /wp-json would break WordPress itself. The payload shape is custom JSON, not Meta-Pixel or GA4 wire format, so content-based filter lists cannot identify it as tracking either.
Do I need Google Tag Manager or Stape?
No. The whole point of Beaconry is to replace those. You only need a Google Analytics 4 property (Measurement ID + API Secret) and a Meta Pixel with a Conversions API access token. Both are free to create.
Does Beaconry work with WooCommerce?
Yes. If WooCommerce is active, hooks for add_to_cart, begin_checkout, and purchase are registered automatically. Order events include line items, currency, and value for revenue attribution. Purchase events use a stable per-order event_id for deduplication if you also run the browser Meta Pixel.
How is consent handled?
Beaconry ships with a two-button consent banner (nl-data-gate). Until the visitor accepts analytics, no events leave the browser and no requests are made. The banner is fully accessible (role="dialog", focus management, keyboard navigation) and respects EU "no implicit consent" rules.
Are credentials stored securely?
Yes. The GA4 API Secret, Meta CAPI access token, and license key are AES-256-CBC encrypted using your WordPress auth salts before being stored in the database. Power users can keep credentials out of the database entirely by defining BCNR_GA4_API_SECRET, BCNR_META_CAPI_TOKEN, etc. as constants in wp-config.php.
Which forms plugins are supported?
Kadence Blocks Form and Fluent Forms are auto-detected. Submissions fire as generate_lead events with hashed PII (email, phone, first/last name, ZIP, city) for Meta CAPI matching. More form plugins are on the roadmap.
What's the refund policy?
14 days, no questions asked. If Beaconry doesn't work for your site, email us and we'll refund via Polar. See the Terms of Service for the full refund clause.
Are there activation limits per license tier?
Solo covers one production site, Studio covers five, Agency covers unlimited. Dev and staging activations are unlimited on every tier — local builds, staging subdomains, and pre-launch URLs do not count against your seat. Polar issues one license key per purchase; you decide how to distribute it across the seats your tier covers.
How do plugin updates work?
Beaconry has a built-in self-hosted updater. After purchase, your license key is validated against Polar; the plugin polls a manifest at www.beaconry.app/downloads/beaconry.json and offers updates via the standard WordPress Plugins screen. No GitHub login, no FTP.
Still have a question?
Email info@beaconry.app — we usually reply within a working day. Polar handles checkout and licensing as Merchant of Record, so VAT and refunds run cleanly via your order page.