Feature · Website Dashboard

A website dashboard that connects clicks to closed revenue.

Most website dashboards show sessions and bounce. The Strkr website dashboard reads sessions, forms, identity resolution to the CRM contact, campaign attribution, pipeline sourced, and closed-won revenue on the same tile grid. The marketing team and the sales leader see the same number for the same question, which is the whole point.

Start free trial See pricing
The attribution gap most websites ship with

Sessions on one tool, revenue on another, no join.

The usual stack has Google Analytics (or Plausible, or Fathom) rendering web sessions on one dashboard and the CRM rendering closed-won revenue on another. Nothing joins the two. The marketing lead opens the analytics tab, the sales lead opens the CRM tab, and the quarterly review becomes an argument about which campaign actually sourced the deal. The Strkr website dashboard solves the join at the data layer, so sessions, form submissions, pipeline, and closed revenue render on the same tile grid under the same date filter. The eight tile shapes below are the ones most teams pin on day one.

Sessions by source

Organic, paid, direct, referral, social.

The sessions tile breaks total weekly sessions by source and renders a stacked-bar time series. The default filter is trailing eight weeks. The refresh is hourly. The data flows from the Strkr tracking snippet (one script tag, no cookie-consent complexity beyond the standard CMP) or from a connected Google Analytics 4 property. The marketing lead sees the full source mix without logging into a second tool.

Form submissions

Every form, every submission, dedup by email.

The form submissions tile counts form posts across every tracked form on the site, dedups by email within a 24-hour window, and renders the volume by form by day. The default filter is trailing 30 days. The refresh is live. Each submission creates or updates the matching Strkr contact and attaches the form payload as a timestamped activity.

Known-visitor count

The visitors Strkr already recognizes.

The known-visitor tile counts the visitors whose session Strkr resolved to an existing contact (through a form fill, an email-link click, or a logged-in product session). The tile breaks the number by segment and renders a trend line. The default filter is current month. The refresh is hourly. The pattern turns anonymous traffic into named activity the sales team can act on.

Pipeline sourced

Pipeline that started with a website event.

The pipeline-sourced tile sums the open-pipeline value of deals whose first-touch attribution is a website event (form fill, product sign-up, pricing page view resolved to a known contact). The default filter is current quarter. The refresh is daily. The tile is the one marketing shows the CFO to justify the website investment.

Closed-won by source

Revenue attributed to each source.

The closed-won-by-source tile renders the trailing-quarter closed-won revenue broken by first-touch source (organic, paid, direct, referral, social, campaign). The filter is current quarter. The refresh is daily. The tile is the one that typically settles the “which campaign actually worked” argument because the number is reconciled from the pipeline, not reconstructed from a pixel.

Top landing pages

Which pages drive the most conversions?

The top landing pages tile ranks pages by the count of conversions (form fills, product sign-ups, pricing-page qualifying events) over the trailing 30 days. The ranking is by conversion, not by traffic, which inverts the usual GA default. Marketing uses the ranking to decide which pages deserve a refresh and which pages deserve a retire.

Campaign attribution

UTM params and campaign hierarchy.

The campaign attribution tile reads UTM parameters from every session, maps them to the campaign hierarchy in Strkr Marketing, and renders pipeline and closed-won by campaign. The default filter is current quarter. The refresh is daily. The campaign hierarchy is editable so a marketer can group ad-set-level campaigns under a parent initiative without rebuilding the dashboard.

Content-to-close path

The content that touches a closed deal.

The content-to-close path tile lists the content assets (blog posts, case studies, white papers) that received at least one view from the contacts on a closed-won deal in the 90 days before close. The pattern surfaces the mid-funnel content that most attribution models drop because they only track first-touch and last-touch. The content team sees which assets earn their place.

Session-to-contact ratio

How much traffic becomes a known visitor?

The session-to-contact tile renders the ratio of total sessions to known-visitor sessions, trended over the trailing 90 days. The ratio is the single clearest health metric for the identity-resolution pipeline. A ratio moving in the wrong direction is a sign that forms are capturing fewer identities, cookies are expiring faster, or a privacy update broke something.

Identity resolution, in depth

Turning an anonymous session into a named contact.

The whole value proposition of a website dashboard inside the CRM is the identity resolution. Without it, the dashboard is just a GA mirror with a different brand on the chrome. The resolution pattern Strkr uses is explicit, consent-aware, and auditable. The design points below are the ones security review and marketing operations both ask about on day one.

First-touch cookie

A session identifier, with consent.

The Strkr tracking snippet writes a first-touch cookie on consent (the standard CMP flow). The cookie is a random session identifier, never a personal attribute. On a form submission or an email-link click, Strkr links the session identifier to the resolved contact, which turns the anonymous session into a named one going forward. Consent is a hard gate; no consent, no cookie, no resolution.

Email-link resolution

The highest-fidelity signal.

Every email Strkr sends includes a tagged link. A click on the link lands on the website with the contact already resolved. The pattern is the highest-fidelity resolution signal because it is explicit and consent-aware (the recipient opted into the email). Email-driven resolution is the primary way most B2B teams turn traffic into named visits.

Product-sign-in

A logged-in user is a resolved user.

For teams running a product tour or a logged-in app, the Strkr tracking snippet picks up the signed-in user identity and ties the website session to the matching Strkr contact automatically. The pattern works for marketing sites that live under the same root domain as the product app.

Form-fill lift

A single form fill resolves the whole history.

When a visitor fills a form, Strkr retroactively associates every page view, blog read, and session in the trailing 30-day window to the resolved contact. The pattern is important because most contacts fill a form after weeks of anonymous research. The retroactive lift turns the full research journey into attributable content.

IP enrichment

Firmographic signal, no PII leap.

For anonymous sessions, Strkr performs IP-to-company enrichment against a reputable reverse-DNS and firmographic provider. The enrichment yields company name, industry, size, and country, which lets marketing see “which companies are visiting” without claiming personal identity. The pattern is honest about the limits: company-level, not person-level, until a form fill or email-link click occurs.

Consent record

Every consent event logged.

Every consent grant and revocation is logged against the resolved contact (where known) or the session identifier (where anonymous). The log is the artifact the GDPR audit asks for on day one, and it is exportable in a format the Data Protection Officer expects. The pattern is designed for regulated-industry tenants from the start.

Opt-out path

A single click to forget.

A visitor who revokes consent on the CMP banner causes Strkr to delete the session identifier, drop any tied enrichment, and remove the resolution against the Strkr contact. The revocation event is logged with the time and the method. The pattern honors the right-to-be-forgotten contract in regulated regions and the general privacy contract everywhere else.

Data residency

EU sessions, EU storage.

For EU tenants, Strkr routes the tracking snippet to the EU-hosted collector and stores the session identifier and enriched data in the EU-hosted database. The regional data path is important for GDPR and for the sector-specific regulators who ask about residency on every HIPAA review. Strkr is HIPAA compliant and offers a BAA on request.

Audit continuity

Every resolution step logged.

Every time the identity-resolution pipeline links a session to a contact, the event lands in the audit log with the method (form fill, email click, product sign-in), the source signal, and the resulting Strkr contact. Security teams reviewing “what did Strkr know about this employee” get a one-query answer. The audit log retention matches the regulated-tenant requirements and is configurable per tenant.

Three website dashboards in production

What the pattern looks like on three real sales floors.

The templates below are the three website dashboards most Strkr tenants clone first. Each has a audience, a tile mix, and a refresh cadence. The design is intentionally focused rather than kitchen-sink.

Marketing attribution

For the demand gen lead.

The marketing attribution dashboard pins seven tiles: sessions by source, campaign pipeline, campaign closed-won, top landing pages, content-to-close paths, session-to-contact ratio, and MQL volume. The audience is the demand gen lead. The default filter is trailing 90 days. The refresh is daily. The dashboard replaces the manual GA plus pivot-table report that marketing usually assembles for the monthly ops review.

Sales awareness

For the SDR team lead.

The sales awareness dashboard surfaces the companies browsing the website in the last seven days ranked by firmographic ICP fit, with the account owner (where assigned) and the most-visited pages. The audience is the SDR team lead. The default filter is current week. The refresh is live. The dashboard turns anonymous traffic into a targeted outbound queue.

Executive summary

For the CMO board update.

The executive summary pins four tiles: sessions by source trend, pipeline sourced quarter-over-quarter, closed-won by source, and content-to-close path for the top ten deals. The audience is the CMO. The default filter is current fiscal quarter. The refresh is daily. The dashboard is the one the CMO exports as a PDF for the board update, which replaces the usual slide reconstructed by hand.

Content performance

For the editorial team.

The content performance dashboard renders page views, average dwell time, scroll depth, and content-to-conversion attribution per asset. The audience is the editorial lead. The default filter is trailing 90 days. The refresh is daily. The dashboard tells the editorial team which posts deserve a refresh and which posts deserve a retire.

Form conversion

For the website operations lead.

The form conversion dashboard counts submissions per form, submission rate per form, and the drop-off per field (where field-level analytics is enabled). The audience is the website operations lead. The default filter is trailing 30 days. The refresh is hourly. The dashboard is the one that spots a broken field that drops the conversion rate overnight.

Campaign ROI

For the paid search manager.

The campaign ROI dashboard reads campaign spend from the connected ad platforms (Google Ads, LinkedIn Ads), pipeline sourced by UTM, and closed-won by UTM. The audience is the paid search manager. The default filter is current quarter. The refresh is daily. The dashboard is the one that typically retires half the ad groups by month two because the attributed revenue finally has a reconciled number.

How Strkr compares to standalone web analytics

What a website dashboard inside the CRM replaces.

Marketing teams usually run Google Analytics (or Plausible, or Fathom) alongside the CRM. The comparison below is honest about where each pattern breaks and where the Strkr website dashboard adds value.

Google Analytics

Deep on sessions, blind on revenue.

Google Analytics 4 is strong on session, event, and funnel analysis. It is blind on revenue because it does not join to the CRM pipeline without a custom BigQuery integration most teams never ship. Strkr's website dashboard reads either the Strkr tracking snippet directly or a connected GA4 property, and renders the revenue join automatically. The pattern complements GA rather than replacing it.

Plausible, Fathom

Privacy-first analytics, revenue not joined.

Plausible and Fathom are credible privacy-first web analytics tools. They are deliberately scoped to session-level metrics and do not join to revenue. For teams running a privacy-first stack, Strkr's website dashboard adds the revenue join without changing the client-side analytics choice. The two tools complement each other.

HubSpot analytics

Marketing-aligned, limited CRM-wide view.

HubSpot Marketing Hub ships a credible website analytics module tied to the HubSpot contact record. The gap shows up when the sales motion lives outside HubSpot (common at mid-market and above). Strkr's website dashboard reads the full CRM pipeline regardless of where the deals originated, which keeps the attribution picture whole.

Standalone attribution tools

Rockerbox, Bizible, dedicated vendors.

Attribution-only tools like Rockerbox or Bizible solve the multi-touch model deeply. They are also a six-figure annual commitment and a six-month implementation. For teams under 500 reps, the Strkr pattern consolidates attribution and reporting into the CRM at the seat price, which is the right trade for most companies. Teams above 500 reps with complex multi-channel programs may still earn their keep with a specialist.

Spreadsheet reconstruction

The manual join finance has been running.

Finance and marketing teams often reconcile sessions to revenue by downloading CSVs and pivoting the join in Excel. The ritual takes a day a month and the output is a quarter stale. Strkr's website dashboard eliminates the ritual.

In-house warehouse

Snowflake plus a BI tool, built in-house.

Larger companies sometimes land sessions and CRM data in Snowflake and model the attribution in dbt. The pattern is powerful and expensive, and typically takes a year to ship end-to-end. Strkr's website dashboard gives a cloneable version of the pattern on day one. Teams that eventually invest in a warehouse keep the Strkr dashboard as a working reference while the warehouse team builds the parallel.

Compliance posture for website data

The GDPR and privacy answers, upfront.

Website data is where privacy regulators focus the hardest. The Strkr posture is explicit and documented.

GDPR

EU residency, SCCs, consent-first.

Strkr is GDPR compliant with Standard Contractual Clauses in the standard contract and an EU-hosted path for EU tenants. The website tracking is consent-first: no cookie, no fingerprint, no resolution without an explicit consent event logged against the session.

CCPA

California opt-out honored.

Strkr honors CCPA opt-out of sale and the full suite of consumer rights. A California visitor who opts out causes the resolution pipeline to drop their session identifier and remove the tie to any Strkr contact. The opt-out event is logged for audit.

HIPAA

Compliant, BAA available.

Strkr is HIPAA compliant and executes a Business Associate Agreement on request. The website tracking is in scope for the BAA when the tenant enables it on a protected site, and the resolution pipeline respects the field-level masks that apply to the matched contact.

SOC 2 Type II

In progress through 2026-Q4.

Strkr is actively pursuing SOC 2 Type II with report completion targeted through 2026-Q4. The website tracking collector, identity-resolution pipeline, and dashboard rendering are all in scope. Interim controls artifacts are available under NDA.

Open API

Every website metric via API.

The website dashboard tiles are rendered from documented public API endpoints. A customer who wants to pipe sessions, resolutions, or attribution into a parallel BI tool or data warehouse can do so with a documented call. There is no privileged dashboard-only data path, which matters to compliance teams that audit API access rather than UI access.

DPA on request

Data processing agreement, standard terms.

Strkr ships a standard Data Processing Agreement on request. The DPA covers the website tracking, identity resolution, enrichment, and audit retention. The agreement is in the format most Data Protection Officers expect, which keeps the privacy review from being a six-week back-and-forth.

Add one snippet and the website dashboard starts rendering within the hour.

Install the Strkr tracking snippet (one script tag, consent-aware, GDPR-ready), connect your CRM pipeline (one toggle on an existing Strkr tenant), and the dashboard pins start rendering with real data by lunch. No GA migration, no attribution project, no warehouse build. Start a trial and see the join of clicks to closed revenue by end of day.

Start free trial See pricing
Common questions

What buyers ask about this feature.

Does Strkr replace Google Analytics?

No, it complements it. Google Analytics 4 is strong on session, event, and funnel analysis. It is blind on revenue because it does not join to the CRM pipeline without a custom BigQuery integration most teams never ship. Strkr's website dashboard reads either the Strkr tracking snippet directly or a connected GA4 property, and renders the revenue join automatically. Many teams keep GA4 for deep session analysis and use Strkr for the attribution and revenue join.

How does identity resolution work without violating privacy?

The Strkr tracking snippet writes a first-touch cookie only after consent through the standard CMP flow. The cookie is a random session identifier, never a personal attribute. Resolution happens on an explicit event (form fill, email-link click, product sign-in), at which point the session identifier is linked to the matching Strkr contact. For anonymous sessions, IP-to-company enrichment yields firmographic context (company name, industry, size) without claiming personal identity. All consent events are logged for GDPR audit, and the resolution pipeline respects the per-tenant data residency contract.

Can anonymous visitors become part of my CRM?

Only on an explicit event. An anonymous session enriches at the company level (through IP-to-company lookup) but does not create a person record. The session becomes attributable to a Strkr contact only when the visitor fills a form, clicks an email link, or signs into a connected product app. On that event, the trailing 30-day session history retroactively associates to the resolved contact, which gives marketing the full research-journey view without claiming identity before consent.

Is Strkr HIPAA, SOC 2, GDPR, and CCPA compliant?

Strkr is HIPAA compliant with a BAA available, GDPR compliant with Standard Contractual Clauses on file and an EU-hosted path for EU tenants, CCPA compliant with opt-out honored, and actively pursuing SOC 2 Type II with report completion targeted through 2026-Q4. The website tracking and identity-resolution pipeline are in scope for all four. A standard Data Processing Agreement is available on request.

Can I pipe the website dashboard data into my warehouse?

Yes. Every tile rendered in the website dashboard is backed by a documented public API endpoint, and the raw session and resolution events are available via a bulk export. A customer who wants to land the data in Snowflake, BigQuery, or Redshift can do so with a documented call. The pattern is important for teams that run a central BI warehouse alongside Strkr. There is no privileged dashboard-only data path that is unreachable from the open API.

What happens when a visitor revokes consent?

The revocation event flows into Strkr and triggers deletion of the session identifier, removal of the tie to any Strkr contact (while keeping the contact record itself, which may exist for other legitimate reasons), and drop of the enrichment. The revocation event is logged with the time and the method for audit. For regulated-industry tenants, the audit retention matches the regulatory window and is configurable per tenant.

Related features

Pair this with...

Dashboard reporting examples Dashboard program Microsoft dashboard

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing