Description
NeuTarget is a hosted acquisition-to-outcome analytics service. This plugin connects your WooCommerce storefront to your NeuTarget website so you can review website activity alongside recorded financial outcomes.
The browser tracker measures permitted storefront activity without setting analytics cookies. The separate server integration sends payment and refund receipts to NeuTarget. A valid payment remains reportable when optional attribution context is missing; it is then shown as unattributed rather than assigned to an invented visit.
The integration provides:
- Storefront tracking using the public NeuTarget browser SDK.
- Merchant-server payment and refund reporting with exact currency minor units.
- Optional checkout context for classic checkout and Checkout Blocks.
- Durable delivery through WooCommerce Action Scheduler, with receipt status and operator retry.
A NeuTarget account and configured website are required. The plugin connects to the NeuTarget service; reports and account features are provided there under your service plan. Review current plans at https://www.neutarget.com/pricing before enabling the service. Installing this plugin does not purchase a subscription or enable paid add-ons.
External services
This plugin connects to NeuTarget, operated at https://www.neutarget.com. Configure the integration only if you authorize the following service connections.
When storefront tracking is enabled and a valid Website ID is configured, the plugin loads https://cdn.neutarget.com/script/v1/nt.min.js. That public SDK sends permitted website activity and browser or campaign context to https://api.neutarget.com according to your NeuTarget website collection settings and applicable consent choices. It runs on storefront pages, not the WordPress admin.
When financial receipts are enabled, WooCommerce payment or refund activity queues an authenticated request to https://api.neutarget.com/api/v1/financial-events. The receipt includes the website ID, stable event identity, order reference, amount in currency minor units, event kind and occurrence time. It can also include the consent state and an opaque session identifier. For registered customers who granted consent, a website-scoped opaque customer hash can be included. The plugin does not send the order’s billing address or customer email to NeuTarget.
The private website API secret authenticates server-to-server requests over HTTPS. It is never placed in browser markup or sent by the checkout scripts. Browser context is optional; the financial receipt can still be delivered without it.
Service terms: https://www.neutarget.com/legal/terms
Service privacy policy: https://www.neutarget.com/legal/privacy
Installation
- Install and activate NeuTarget: Analytics & Revenue Tracking for WooCommerce from the WordPress Plugin Directory, or upload its installation ZIP. The directory slug is
neutarget-analytics-for-woocommerce. WooCommerce 8.2 or later and PHP 8.0 or later are required. WooCommerce Action Scheduler must be available for receipt delivery. - Add your store as a website in NeuTarget. Open WooCommerce → Settings → Integration → NeuTarget Analytics and enter that website’s public Website ID and private API secret. The secret is encrypted using WordPress salts. Alternatively, define
NEUTARGET_WEBSITE_IDandNEUTARGET_API_SECRETinwp-config.php; these constants take precedence over saved settings. - Choose whether to enable storefront tracking and financial receipts. Configure your consent manager to call
window.neutarget.setConsent('granted')orwindow.neutarget.setConsent('denied')as appropriate. The plugin does not decide which consent requirements apply to your store. - Visit the storefront and verify an observed pageview in NeuTarget. Place a test paid order through your intended gateway and check that a financial receipt is accepted. A saved configuration or a thank-you page alone does not verify financial delivery.
- Inspect WooCommerce → Status → Scheduled Actions for jobs in the
neutarget-financialgroup. After correcting a credential or delivery problem, use the affected order’s NeuTarget: retry pending receipts action. Integration settings show the last accepted receipt and the latest order requiring review. - Keep WordPress cron running. On low-traffic stores, use a system cron to invoke
wp-cron.php. A bounded repair scan runs every 15 minutes and revisits up to 25 pending orders per run if the queue lost a job. If delivery remains unavailable, inspect Scheduled Actions and WooCommerce logs with sourceneutarget.
FAQ
Does this plugin verify payment settlement with the gateway?
No. These are merchant-server receipts. WooCommerce and the selected payment gateway assert the event; NeuTarget does not independently verify settlement through this plugin. Review captures against your source records for the reporting interval you rely on.
Which payments and refunds are reported?
Online captures are queued when WooCommerce emits woocommerce_payment_complete. Changing an order’s status to processing or completed does not declare payment. The built-in cash on delivery, bank transfer and cheque methods are excluded from that automatic gateway path. For an offline payment already received, an authorized operator can use the order action NeuTarget: record confirmed cash payment.
Gateway API refunds are reported when WooCommerce marks the refund as refunded through its payment API. Manual refunds are excluded unless you explicitly enable Manual refunds after confirming your operators create them only after returning money. Chargebacks and gateway-specific settlement checks require a separate supported integration. Evaluate partial-capture gateways against the reported WooCommerce order total before production use.
What happens if attribution context is missing?
An eligible financial receipt is still sent. Optional session context is carried from classic checkout or Checkout Blocks only when available and permitted by the applicable collection policy. Missing context leaves the receipt unattributed. A browser interaction is not converted into a financial receipt.
What happens if NeuTarget or the delivery queue is unavailable?
A queued receipt retains its stable event identity and exact payload while Action Scheduler retries temporary failures. A periodic repair scan can recover a payload left behind by a queue failure. Invalid credentials or conflicting receipts require operator review. Inspect delivery status and retry after resolving the cause; do not change event identities to bypass an error.
How are privacy requests handled?
The plugin adds suggested WordPress privacy-policy text and a personal-data eraser for its checkout context. Erasure removes optional context from unsent payloads while retaining the financial amount for delivery. Already delivered receipts follow your NeuTarget website’s retention and erasure controls. Review both systems when fulfilling a data request. Changing the WordPress authentication salts also prevents decryption of the stored API secret; configure it again if those salts are rotated.
Does it support HPOS and Checkout Blocks?
Order access uses WooCommerce CRUD, and the plugin declares HPOS compatibility. Checkout Blocks use Store API extension data; classic checkout uses optional hidden context fields. Validate your actual checkout and gateway on a staging store before relying on reports. Include an accepted capture, refund delivery, duplicate callbacks, missing attribution and a temporary API failure in that acceptance check.
Where do I get help?
Use https://www.neutarget.com/contact or create an authenticated support case from your NeuTarget account. Include the plugin version and the relevant delivery status. Do not send your private API secret or customer records in a public support thread.
Changelog
1.1.2
- Update the plugin display name and short description to clarify its analytics and revenue tracking purpose.
1.1.1
- Align the text domain and release metadata with the approved WordPress.org directory slug.
- Declare the WooCommerce plugin dependency and clarify external service connections.
- Correct HPOS detection in the bounded pending-receipt repair scan.
- Improve checkout input sanitization and clarify translation placeholders.
1.1.0
- Replaced legacy revenue calls with durable financial-events receipts.
- Added exact currency scales, consent handoff, Blocks Store API metadata, gateway/refund gating, Action Scheduler retry and repair, encrypted secret storage, privacy eraser, and truthful delivery status.
- Removed fabricated attribution and automatic-payment claims.