leadmaps release notes since v4.0

See the leadmaps product before signing up

The leadmaps homepage now presents the current product experience through a focused story and an authenticated dashboard preview built with clearly labelled representative data.

• The hero reflects the current Summary shell, navigation, metrics, traffic, sources, and bot context from the authenticated application.
• Four visual chapters explain overview, live activity, funnels, and acquisition without turning the homepage into product documentation.
• English and Dutch routes share the same responsive presentation, including a compact mobile header and a signup action inside the mobile menu.
• Entrance and data transitions respect reduced-motion preferences, while keyboard navigation and responsive layouts remain available without animation.
• Representative metrics stay labelled as illustrative product data and do not claim to be a live customer workspace.

Read product activity from one exact data contract

Summary, Pages, Sources, Campaigns, Events, Funnels, and Attribution now reconcile through strict production data contracts. Totals, filters, completeness, and live updates describe the same measured population across the dashboard.

• Summary, Pages, Sources, and Campaigns use exact server totals. Partial coverage is labelled instead of looking complete.
• Events combines exact range totals, a 60-minute activity view, recent history, and a resumable live stream that reconciles after reconnects.
• Funnels supports 2 to 12 ordered steps, saved revisions, breakdowns, time between steps, and aggregate transition analysis from one query.
• Attribution keeps conversion selection, model calculation, spend ranges, and separate currency totals aligned workspace-wide.
• Shared date, site, source, device, browser, operating system, and location filters are applied before totals and rows are calculated.

Read the analytics dashboard guide.

Connect lead activity to the tools your team uses

The Integration Hub is live as a private preview for selected workspaces, with a 16-entry catalog and no-code connection and automation editors. A provider stays unavailable until its production application and canary have passed.

• Slack alerts, HubSpot contact access, Pipedrive people and deal workflows, and secure webhooks passed production canaries in the leadmaps dogfood workspace.
• HubSpot field choices use current readable labels, and a contacts-only connection cannot create or update deals without a separately granted capability.
• Slack passed connection, delivery, pause, resume, reconnect, duplicate suppression, and disconnect checks in the production dogfood workspace.
• Pipedrive passed readable field and stage discovery, explicit deal-write approval, one person and one deal delivery, replay-safe duplicate prevention, delivery history, and provider credential revocation.
• Secure webhooks passed direct delivery, retry, duplicate suppression, delivery history, and disconnect cleanup checks.
• Connections can be paused, resumed, reconnected, or disconnected, with encrypted credentials, permission checks, plan limits, and non-sensitive delivery history.
• Zapier, Make, and n8n can receive leadmaps activity through the same secure webhook bridge.

Read the Integration Hub guide.

Install leadmaps under its own package name

The public browser SDK, Node SDK, shared contracts, and MCP server now use the @leadmaps npm scope. Existing @syntarie installs keep working through September 29, 2026, so teams can migrate during a normal release.

• @leadmaps/tracking 0.14.3 includes the lazy, customizable consent banner entry. It does not contact leadmaps before consent.
• The Cookie banner studio lets non-developers edit copy, colors, placement, spacing, and responsive presentation while required consent text and Accept and Decline controls stay protected.
• The canonical browser SDK, Node SDK, shared-contract, and MCP packages passed strict consumer checks on Node 20 and Node 22.
• Final compatibility releases under @syntarie remain supported until September 29, 2026. Published versions stay installable after the window.
• Public packages omit source maps, raw source, private repository metadata, and server-side analytics recipes.

Read the package migration guide.

See what blocks people, then connect it to outcomes

Experience Intelligence connects consented interaction evidence to recordings, journeys, returning behavior, campaigns, leads, conversions, and revenue. Capture is rolling out gradually to new consent-mode sites, while existing sites remain opt-in.

• The Experience workspace brings issues, richer heatmaps, recordings, journeys, and Returning visitors into one investigation flow.
• When a qualifying recording exists, an issue can open at the relevant replay moment. leadmaps says clearly when no recording is available.
• Unique visitor identity now remains stable across repeat openings, while live visitor counts release closed pages and expire abandoned presence safely.
• @syntarie/tracking 0.14.1 adds the lazy Experience module. It loads only after consent, and anonymous mode remains excluded.
• Outcome comparisons describe observed associations, not proven causation. Known bots and synthetic traffic stay out of Experience aggregates.
• Privacy-safe summaries can explain why an issue matters without sending replay frames, page text, selectors, personal identifiers, or exact revenue to the AI provider.

Read the Experience guide.

Turn campaign interest into owned follow-up

The new Leads workspace turns campaign and form interest into owned follow-up. It is live with a production-proven path from tagged visit to one deduplicated lead, sales work, Won value, and outbound delivery.

• Normal campaign tags work across social networks, newsletters, partners, and ad platforms, so acquisition context follows the lead.
• Create leads through identification, hosted or embedded forms, and previewed CSV imports without duplicating an active opportunity.
• Board and table views share owners, stages, companies, values, private notes, tasks, history, and campaign context.
• Pro includes one working pipeline. Business adds multiple pipelines, behavior-based prioritisation, and workflow automation.
• Contact details and private text stay in the private record vault. Reveals are audited, and Article 17 erasure removes the private content while retaining a redacted workflow trail.

Read the Leads guide.

Four new ways to read your product

The headline visualisation upgrade. Journeys, geo, cohorts, annotations — each shipped with a real route in the dashboard, server-side aggregation, and a Pro+ pricing gate.

• Sankey user journeys — every page-to-page transition with drop-off bands and click-through drill into the events behind them.
• Geo world map — per-country session bubbles on a d3-geo backed map, scaled by traffic and tinted by engagement.
• Cohort retention grid v2 — the classic SaaS triangle with week/month grain toggle and one-click CSV export.
• Deploy and marketing annotations — drop named markers on the timeline, picked up by every time-series chart workspace-wide.

Pick the region your data lives in

Event data is EU-resident (Amsterdam) by default today. US and Asia regions are planned as part of region-routed ingest.

• EU collector live in Amsterdam, with additional Fly regions provisioned for rollout.
• Workspace residency setting (EU is the live default; region-routed ingest is in progress).
• Cross-region Postgres replica dormant by default — flipped on per-workspace for DR.
• EU is the live residency on every plan today; US and Asia region choice ships with region-routed ingest.

Audit-ready, without the audit theatre

CI gates that fail the build on test-coverage regressions, SDK bundle growth, and collector p99 drift. Plus the policy docs auditors expect to see on day one.

• Test-coverage CI gate, SDK perf-budget CI gate, and a 10-percent p99 regression bench on the collector hot path.
• Sentry coverage audit so any unhandled error route has a paging alert.
• SOC 2 evidence pack with security policy, vendor reviews, incident-response template, and a public /trust portal.
• DPA template generator so customers can fingerprint a signed agreement in a click.

The composable insights layer

Fixed dashboards are good, composability is better. v3.4 adds the JSON DSL that powers a drag-and-drop insights builder under the hood, with cohorts and group analytics on top.

• Insights JSON DSL with a typed compiler that emits safe parameterised SQL.
• Cohorts builder that filters every insight on a saved population.
• Group analytics for B2B accounts so you can pivot from user-level to account-level views.
• SQL escape hatch for power users who already know exactly what they want.

Flags + experiments, evaluated where the data lives

Customers using flags from another vendor were the hardest to migrate. So we shipped them — eval in the Rust collector, exposed by the SDK, surfaced by the dashboard, and tied to a stats cron for A/B significance.

• Feature flag schema and Rust evaluation engine on the collector hot path.
• SDK feature-flags subpath with bearer auth and cached evaluations.
• Dashboard /flags and /experiments pages with rule builder and traffic-split UI.
• A/B experiment stats cron with p-value, lift, and decision recommendation.

SAML SSO + onboarding for buyers who need a procurement checkbox

Enterprises do not adopt magic-link-only auth. v3.2 wires SAML 2.0 with JIT provisioning, an onboarding checklist for new workspaces, billing forecasts so finance teams stop guessing, and SIEM-friendly audit-log streaming.

• SAML 2.0 SSO with JIT user provisioning and per-workspace identity-provider config.
• Onboarding checklist that walks new admins from install to first dashboard.
• Billing usage forecast surfaced on the workspace home so quota surprises stop.
• Audit-log streaming to Datadog, Splunk, and generic webhook destinations.