From Acquisition Activity to Recorded Outcomes
- With the Evidence Boundaries Visible
Start with observed website behaviour, then add configured goals, authenticated financial outcomes, and ad spend. NeuTarget shows the available campaign context and keeps missing coverage visible.
Create your account, add your domain, and verify observation.
Sign up with your email and get a 14-day free trial instantly - no credit card required. Add your website domain and we'll generate a lightweight tracking script. Copy and paste one line of code into your site's <head> tag to begin browser observation. Goals, privacy instructions, authenticated outcomes, and provider connections require their own configuration and validation.
What happens behind the scenes
Permitted pageviews, configured events, and available referral context are processed after installation is verified
Sessions use a per-tab nonce and server-generated hash; weekly network groups are approximate and customer digests are pseudonymous
Page load times, device types, browsers, and JS errors are logged automatically
UTM parameters from your marketing links are tracked out of the box
The script loads asynchronously. Validate its performance and collection behaviour on your own production pages and consent configuration.
How we identify sessions without cookies
A current session is based on a per-tab nonce and site-scoped server hash, with a 30-minute inactivity window. Approximate network/browser groups are a separate weekly measurement and are not verified people.
The analytics server processes IP addresses and User-Agent information for request handling, geographic enrichment, and approximate weekly network/browser groups. Raw IP is not a field in the analytics event table, but operational access and security logs may retain it. These network groups are not verified people.
The current browser SDK first requests the site collection and privacy policy. If consent is required, it waits for the customer’s consent flow to grant collection; denying or withdrawing consent clears its session context and stops further tracking writes. Once collection is allowed, it uses a random per-tab session nonce, with a 30-minute inactivity window, and sessionStorage for session and campaign context. Storage restrictions or older tags can reduce continuity. Optional site-scoped customer digests can link declared customer activity across sessions; a 64-character hash is pseudonymous data and can remain personal data.
New websites default to minimal mode, which drops optional declared customer and advertising identifiers, diagnostic error details and precise city/region. Existing websites retain a labelled legacy mode until an admin reviews it; identified mode requires an explicit processing-instructions acknowledgement. Server controls strip URL queries/fragments, reduce referrers to origins, bound text and redact common sensitive patterns, but cannot detect every form of personal information. Paths, UTM values, referrers, click destinations, custom-event fields and error text can still contain customer information if your application puts it there. Keep names, emails, payment credentials, account tokens and sensitive information out of those fields. Hashing identifiers does not remove the need to control collection and access.
Customers choose the purposes, data fields, lawful basis and visitor notices for their deployment. Where consent is required, control loading of the analytics script and enabled integrations through your consent flow. Using no analytics cookies does not by itself establish an exemption for browser storage, identifiers or subsequent personal-data processing.
Applicable requirements depend on the audience, jurisdiction and configuration. The European Commission explains personal and pseudonymised data, and Your Europe describes online privacy and cookie requirements. India’s 2025 DPDP Rules notification provides phased commencement; publication does not mean every provision took effect at once. This product does not assign a lawful basis or certify a customer’s compliance.
Prepare campaign tracking. Choose the outcome you want to measure.
Create a campaign with its own primary outcome, then use Link Builder to prepare exact UTM identifiers for your acquisition channels. Share campaign links with authorized teammates while keeping personal saved links private. Recorded visits retain the campaign context available to the installed tracker.
What you'll see for each campaign
Review results against the campaign's pinned outcome definition. Changing the website default does not rewrite that definition.
Report confirmed revenue. Keep its source and attribution visible.
Connect a supported commerce integration or send financial events from your backend after payment confirmation. NeuTarget records captures and subsequent refunds with their event identity and currency. Available session context links outcomes to recorded campaign touches; valid receipts without a match remain visible as unattributed.
What you get
Revenue by UTM campaign, source, and medium
Compare first-touch, last-touch or linear credit across eligible recorded touches
Stable event identities prevent duplicate receipt ingestion
Authenticated financial events stay distinct from browser payment interactions
Review recorded revenue alongside refunds. Add compatible campaign spend to calculate ROAS in the same currency.
One workflow for the evidence needed to review acquisition and outcomes.
Start with traffic and your selected outcome, then investigate the pages or acquisition sources behind a change. Reporting keeps data freshness and missing measurement context available for review.
Total pageviews, sessions, unique visitors, bounce rate, conversion rate. Yesterday vs. last week comparisons with green/red deltas.
Which pages get the most traffic, ranked. Spot your best-performing content immediately.
Google, Facebook, Twitter, Direct, or that blog post someone shared. Know where your audience comes from.
Mobile vs. desktop ratio. Browser distribution. Optimize for what your users actually use.
Review observed UTM campaigns with available sessions and configured outcomes. Financial metrics require compatible evidence.
Pages with the highest bounce rates, slowest load times, and JS errors. Find and fix what’s broken before your users complain.
Weekly declared-customer cohorts distinguish observable, partial and future periods. Anonymous network groups are excluded from customer retention.
Build up to 10-step funnels from recorded pages and events. Identify observed steps with the largest drop-off in the configured flow.
Statistical alerts when any metric deviates from its baseline. Z-score analysis catches traffic drops, error spikes, and revenue anomalies automatically.
First-touch, last-touch, or linear - choose how to credit your marketing channels. See which campaign actually drives revenue, not just clicks.
Compare recorded campaign performance. Identify where observed journeys drop off in your funnel.
Select two or more campaigns and compare them side by side - sessions, conversions, revenue, bounce rate. Instantly see which campaign is outperforming and which is burning budget.
Then go deeper with Funnel Analysis. For any campaign, see the step-by-step flow:
Use the largest observed drop-off to choose what to investigate next. Check the recorded steps and test a focused change, then compare the next complete reporting period.
Set up smart alerts. Know when a threshold needs attention.
Define rules like “alert me when sessions drop > 30% vs yesterday” or “notify me when revenue exceeds ₹50,000 in a day.” Eligible alerts include AI explanations of possible contributors to help you investigate. Rule allowances and available channels follow your plan; delivery state remains visible in the dashboard.
Discuss your performance with NeuIntel in plain English.
Type questions like “Which campaign had the best ROAS last month?” or “Why did my bounce rate spike on Tuesday?” NeuIntel uses available website metrics to explain observed changes and suggest checks. Follow-up questions stay grounded in your reporting context, with evidence gaps called out where they affect the answer.
Illustrative conversation using sample data:
You:
“Which paid campaign recorded the most net revenue this week?”
NeuIntel:
“Google CPC has ₹1,23,400 in net revenue from 34 recorded purchases. With ₹30,000 in mapped spend, its ROAS is 4.11x. This comparison uses INR only. Two other purchases have no campaign match and remain unattributed.”
Import ad spend. See real ROAS per campaign.
Use an eligible Google Ads or Meta Ads connection to synchronize spend. Manual entries and CSV import support other sources. NeuTarget compares mapped spend with currency-specific net revenue for ROAS. Cost per conversion uses the recorded conversion count; customer acquisition cost requires eligible customer identity. Unmapped spend stays visible.
Your analytics summary, in your inbox before your first coffee.
Enable a daily briefing for a concise performance review in your inbox. Scheduling follows your workspace timezone, and the message links back to the dashboard when something needs attention.
- Sessions, pageviews, and average load time
- Revenue generated (if applicable)
- Your top referrer and top-performing campaign
- Top 3 pages by traffic
- A 7-day traffic sparkline showing the visual trend
- Green/red percentage deltas vs. last week
Team briefing access
Admins choose eligible briefing recipients. Each recipient receives only the website data permitted by their membership and role. Team access and briefing availability follow the workspace plan.
One glance. You know if something needs attention or if things are on track.
Invite your team, control access and manage privacy requests.
Invite colleagues to the same reporting workflow and assign the website access they need. Roles control what members can read or change, while audit history records supported workspace actions.
Manage invitations and authorized website membership from Settings. Plan allowances determine team capacity and available governance controls.
Request a JSON export of supported account records through the privacy controls. Review its documented scope before responding to a data-access request.
Use the authenticated erasure workflow to remove eligible account and website data. Required billing records and documented recovery safeguards follow their retention obligations.
Start with a measured workflow. Upgrade when coverage and value are clear.
Use the trial to verify collection and your first outcome. Bootstrapper supports a recurring measurement workflow with manual spend reporting. Growth adds connected paid acquisition and higher collaboration allowances. NeuSignal is a separately purchased add-on with its own access requirements.
The pricing page shows current limits and supported-market prices alongside the feature comparison.
Compare plans and accessCheckout shows the payment methods available in your supported market. Subscription receipts and available invoices can be reviewed in Billing. Shopify app purchases use Shopify billing.
Manage renewal from Billing. Collection and access follow the current subscription period and documented lifecycle policy.
Turn a performance change into a focused investigation.
NeuIntel explains available workspace evidence and proposes useful next steps. Intelligence Review brings calculated findings into a review workflow, where your team can record an action and check its result after a complete observation period. AI capabilities and usage allowances follow the current plan.
Illustrative insight using sample data:
“Google CPC sessions are 12% above the previous complete week. Recorded net revenue is ₹44,500, with 3.2x ROAS on compatible mapped spend. The largest observed funnel drop-off is at checkout, at 74%. Review the checkout steps and errors before choosing a change, then compare the next complete week.”
WhatsApp Daily Briefing
Eligible workspaces can opt in to a daily briefing on WhatsApp. Notification preferences and provider delivery state remain available in the dashboard. This is separate from alert delivery.
Begin with one script. Complete the outcome integrations your workflow requires.
Data you can actually act on.
Review the collection, retention and integration details before installing your tag. No credit card is required for the trial.
