Website analytics
All analytics plansReview pageviews and sessions alongside acquisition sources. Understand which pages people visit and how they engage.
NeuTarget features
Follow acquisition through website behaviour to recorded outcomes. Cookieless measurement and built-in AI help your team investigate performance and decide what to do next.
14-day website analytics trial with limited NeuIntel use. No payment card required.
40 capabilities across 6 product areas
Standard plan access is shown below. Setup requirements and usage allowances apply. See current plans
Follow website behaviour and measure the outcome each campaign is meant to achieve.
Review pageviews and sessions alongside acquisition sources. Understand which pages people visit and how they engage.
Choose an exact completion event or a purchase outcome for each campaign. Campaigns retain their pinned outcome definition when the website default changes.
Revenue results require ROAS access.
Record a decision and set its follow-up period. Review subsequent observations against the selected campaign revision and outcome.
Build tracking links and review available campaign context. Keep personal saved links private or explicitly share a snapshot with a campaign.
Instrument named actions such as a completed signup or booking. Use exact event names when defining an action outcome.
Define funnel steps and investigate recorded drop-offs. Use available journey and friction observations to decide what needs closer attention.
Review return activity for declared, site-scoped customer identities. Requires permitted identity setup; anonymous network groups are not customer cohorts.
Compare first-touch and last-touch credit, or use linear attribution across eligible recorded touchpoints. Attribution credit describes observed journeys, not incremental impact.
See recently active sessions and their reported pages. Available acquisition context follows the normal collection and processing window.
Explore available browser and device context alongside visitor geography. Detail depends on collection settings and the location evidence received.
Explore journeys for visitors your site identifies through a permitted, site-scoped identity. Requires identity setup; a login alone does not identify visitors automatically.
Compare selected metrics with built-in industry reference ranges. These are indicative benchmarks rather than a live peer cohort.
Reconcile recorded outcomes with acquisition spend while keeping financial coverage visible.
Receive authenticated financial events through a supported integration or your backend. Review attribution coverage while valid receipts without campaign context remain visible.
Compare recorded spend with revenue after refunds. Review available acquisition-cost metrics while keeping each currency separate.
Record campaign spend for a defined period. Retain the source and actual currency when reconciling it with outcomes.
Import permitted campaign spend and map it to recorded campaign context. See mapped and unmapped spend before interpreting ROAS.
Import historical spend through a validated CSV. Keep backfilled records and other advertising channels in the same spend ledger.
Observe supported checkout and payment-link interactions as browser activity. A payment click does not confirm a purchase.
Inspect calculated findings and use built-in AI to investigate the evidence behind a change.
Ask follow-up questions in plain language. Keep the website and reporting context in view, with links to the figures supporting an answer.
Request an explanation for a selected reporting period. Review suggested next steps before choosing an action.
Review calculated findings and their coverage limits, then investigate possible contributors. AI interpretation stays distinct from recorded facts.
AI access and usage follow the source report and your plan.
Receive eligible weekly interpretations of recorded performance. Generation uses the current analysis allowance and recipient settings.
Add an AI interpretation to a shared report for its selected interval. The calculated report remains available separately.
Follow important changes with configured email alerts and scheduled performance summaries.
Compare eligible metrics with a historical baseline. Inspect unusual changes and the available evidence before deciding what to investigate.
Set supported metric thresholds and snooze known issues. Revenue rules retain the selected currency and reporting interval.
Rule allowances vary by plan. WhatsApp alerts are unavailable.
Receive eligible daily summaries in the workspace reporting time zone. Optional AI context depends on availability and recipient settings.
Receive a scheduled summary of recorded performance. AI context is optional; provider acceptance remains distinct from inbox delivery.
Review triggered rules with their recorded metric values. Inspect notification status when delivery fails or remains incomplete.
Make deliberate collection choices and manage access to the data your workspace retains.
Measure permitted website activity without setting analytics cookies. Session state and optional declared identities remain subject to your collection choices.
Use the dedicated privacy controls to request account data or erasure. Follow the request’s scope and completion status.
Configure optional context and identity collection for your website. Applicable privacy obligations depend on the deployment and audience.
Export supported analytics records for offline analysis. Keep this reporting capability distinct from an account data-access request.
Authorized billing administrators can review available documents and configured tax fields. Applied details follow the billing profile and transaction.
Measurement and setup
The browser SDK records permitted activity and available context. Named actions need instrumentation; optional diagnostics follow your collection settings.
A supported commerce integration or your authenticated backend supplies financial events. Browser clicks alone do not confirm payment.
Choose your setup
Start with your website or supported commerce connection. Add authenticated outcomes and ad spend when you need revenue reporting.
Browser SDK
Install the SDK where you control script loading, including HTML and modern web frameworks. Add named events for the actions you want to measure.
Dedicated commerce integration
Follow the documented app setup for storefront activity and supported order/refund events. Verify received data through the guided setup.
WooCommerce plugin
Connect the store with the plugin and verify order/refund delivery. Check compatibility for your checkout path.
Authenticated financial-events API
Send authenticated financial events from your backend. Retain the actual currency and stable event identifiers for retry-safe delivery.
Guided account connections
Connect accounts with the required reporting permissions. Growth imports eligible spend for campaign mapping and reconciliation.
Manual entry or CSV import
Bootstrapper includes manual spend entry. Growth adds validated CSV imports for historical records and other advertising channels.
Guided setup verifies received data after configuration. Find the right NeuTarget setup
Start with website analytics. Connect the outcome that matters to your team.
Explore the sample workspace