Introducing Logspot v2

Analytics tells you what happened and then stops there.

The dashboard updates, the alert fires, and the real work starts somewhere else. Someone reads the number, decides it matters, works out which account it was, looks up who works there, and writes the follow-up by hand. The interesting part of analytics has always happened outside the analytics tool.

Logspot v2 changes what the tool is for. It closes that loop, from the event through to the action. It is live now, and it is the largest release in the product's history.

We rebuilt Logspot from the foundation up because we wanted analytics to do more than report on the past. We wanted it to drive what you do next. Our team has run analytics at real scale before, through Webtrends (acquired by Oracle) and across billions of events, and privacy, trust and compliance is our main business at Concord. What we built is a modern go-to-market analytics platform, focused on turning your own data into action rather than only reporting on it.

Where the work gets lost

Every team we have worked with collected more data than it used, and the reason is usually the handoffs. Measurement lives in one tool, identity in another, enrichment in a third, and the action in someone's browser tabs. Each handoff loses something, and the last one, between noticing and doing, often doesn't happen at all.

Logspot owns the event layer, so everything above it comes from behavior on your own site and in your own product.

What shipped

Measure

We rebuilt the foundation, moving to ClickHouse so the system grows with traffic rather than straining against it.

Showing every event as it happens only works if the system keeps up under load, across customers a thousand times different in size, without dropping data or falling behind. We built it to.

The two that matter most here are a revenue dashboard and a company-level view. The revenue dashboard shows recent payments and which channels actually brought paying customers, first touch and last touch, so you can see which marketing turns into money rather than just traffic. And you can look at all of your analytics by company, not only by user, which for a B2B product is the view that tells you whether an account is expanding or going quiet. Channel tracking works out where visitors came from and applies to traffic you already collected, not only new visits, and shareable URLs carry state so a link shows your teammate exactly what you see.

Dashboards are configurable and flexible, and you can embed them in your own product, so plenty of teams run Logspot as a privacy-ready analytics tool in its own right, before they ever touch the rest of the loop.

If you are already a customer, you will notice this as faster queries and dashboards that hold up as your volume grows.

Identify

Anonymous visits and signed-in users are now joined into one person across devices, so what someone did before signing up stays attached to them.

When two identities conflict, Logspot doesn't guess. It records the conflict and waits for a person to resolve it. Silent auto-merging is how identity data quietly goes wrong, and being confidently wrong about who someone is causes more damage than admitting you don't know.

This is first-party. The people we resolve are people who interacted with you.

Enrich

Company details fill in automatically through a built-in enrichment waterfall: industry, size and location, drawn from several sources in order, so you get an answer without wiring up a separate enrichment vendor. Looking up the same company twice doesn't cost twice. Company profiles and personas build a picture of who you sell to.

Signal

Instead of remembering to check, you get told. An account you care about visited. Someone landed on pricing. Someone came back within a week. Usage jumped above normal. A company that looks like your customers turned up.

Alerts go to Slack, Telegram, or anywhere else you want them. Once a week you get a summary of what moved, with a suggested next step for each account.

Act

The Actions engine is a catalog of things Logspot can do for you: notifications, scheduled reports, and agents that research companies, prospect, qualify leads and draft outreach.

You can also connect Logspot to an AI assistant like Claude and ask it questions directly. It can look up profiles, companies and revenue from wherever you already work.

Privacy, built for compliance rather than around it

We are the founding team of Concord, a privacy, trust and compliance platform, so the privacy work here is built by people who do it for a living.

We take real inspiration from the privacy-first, cookieless analytics movement, which did important work in getting the category to take privacy seriously. Where we differ is the approach. Many privacy-preserving analytics tools rely on IP-based fingerprinting to stitch a visitor's activity together within a single day, and a lot of people question whether that is a compliant tactic under current processing rules like the ePrivacy Directive. It also gives up most cross-session analysis, since nothing follows a visitor from one day to the next.

Rather than build on a tactic with those questions hanging over it, we built our own consent layer directly into the analytics pipeline: adaptable to your compliance setup, integrated rather than bolted on beside it, and something we have not seen another analytics platform do. Consent is not a niche concern: more than 150 countries now have a data protection or privacy law, and building on consent from the start is what keeps Logspot aligned with them rather than betting on one contested reading of the rules.

In practice, that means consent is recorded on every event and travels with the data. It picks up consent automatically from the consent management platforms teams already run, Concord and OneTrust among them, and it honors native browser signals like Global Privacy Control out of the box. Requests to delete or export data run start to finish, and a deletion erases the data rather than hiding it.

Because consent is captured end to end, more becomes possible over time, not less. A properly consented dataset supports much deeper analysis, and it can be routed and activated into the downstream systems and campaigns where the work happens, your outbound included, in ways a minimized dataset never can.

Also new

Underneath the loop, v2 lands the foundations that make it a real platform: organizations and roles, so accounts are no longer single-user and you can bring in a teammate or a client at the right level of access, and a public API that now ships with full documentation.

New pricing

The old model tied advanced features to volume tiers, which punished a common case: a small team that wanted a more capable feature long before they had the volume that justified a bigger plan.

The new model separates the two. Price scales with events, and feature access is set by tier. The entry point is lower, pricing stays published, and there is no "Contact Sales" gate on standard tiers.

The full structure is at logspot.io/pricing.

If you are already on Logspot

Log in. Your data, dashboards and tracking are all in place, and the migration ran automatically.

Three things worth doing first: create an organization and invite a teammate, look at your analytics by company rather than only by user, and check the revenue dashboard against what you thought your channels were doing.

If you would like fifteen minutes with the team to walk through it, reply to your customer email or message us in the product.

If you are considering Logspot

If you want your analytics to help you win customers, not just report on what already happened, this is the release that makes that possible. One snippet, minutes to your first event, real-time by default, a documented developer-first API, and a loop that runs from the event through to the action. A modern go-to-market analytics platform that runs on your own data and is built to drive the next action, not only to report on the last one.

Start free at logspot.io. If you would rather see it first, the team is happy to walk you through it.