What Vendably Pulse is
Vendably Pulse is web analytics for your storefront that lives inside your Vendably account. You install it with a single script tag on your store, or connect it via Google Tag Manager if you use that already. No separate analytics platform, no third-party data processor, no account signup elsewhere: the analytics data belongs to you and stays in your Vendably workspace.
Pulse runs on first-party infrastructure. Your store's domain owns the analytics data from the moment a visitor arrives. This architecture removes the need to send shopper behaviour to external services.
Privacy architecture and consent
Pulse's privacy design is its defining feature. It honours Google Consent Mode, the vocabulary most compliance teams already use.
When a visitor arrives, they carry no analytics identifier until they grant consent. If your store shows a consent banner, Pulse listens for consent signals. Once consent is given, Pulse sets a first-party cookie that persists across every page, including checkout. The cookie is scoped to your domain and your domain only.
If a visitor denies consent, Pulse still counts them in aggregate traffic totals. They appear in visitor counts and session numbers. But they carry no persistent identifier and no event-level record. Denied visitors are statistics, not profiles.
Analytics events themselves are scrubbed at the point of capture. Pulse will never record names, email addresses, postal addresses, phone numbers, or any personal data. Commerce events are filtered to a fixed vocabulary of commerce fields: product SKU, product ID, category, price, quantity, transaction ID, and revenue. No customer PII enters the system.
Geography is deliberately coarse. Pulse records city and a centroid rounded to roughly one kilometre. You see that a visitor came from London or Manchester. You do not see a precise street address or latitude/longitude.
What Pulse measures
Pulse captures traffic and conversion metrics from your storefront.
Traffic and engagement includes visitors (unique first-party identifiers), sessions (visits grouped by inactivity), and pageviews. Pulse shows trends over time so you can spot patterns in traffic volume.
Revenue and transactions are deduplicated by transaction ID to prevent double-counting. Pulse records the total revenue per period, the number of transactions, and the average order value. These metrics update as orders are captured.
Marketing attribution works server-side from URL parameters and HTTP referrer headers. Pulse recognises utm_source, utm_medium, utm_campaign, and utm_content parameters. It also infers channel from referrer domain (organic search, social, email, direct). You see which channels drive traffic and which drive revenue.
Product performance is tracked via per-product funnels. Pulse counts product list impressions, product views, additions to basket, and purchases. You can drill into any product to see its full funnel and spot where shoppers drop off.
Site search captures the terms shoppers search for on your store. You see which products or categories shoppers are looking for and whether they convert after searching.
Goals and custom events let you track actions beyond purchases. You can register named goals in Pulse setup, then fire them from your site. Examples include newsletter signups, demo requests, or wishlist additions. Pulse counts them and shows them in trends.
Dashboard and reporting surfaces
Pulse surfaces analytics in several views.
The main dashboard shows a dual-axis chart: traffic (visitors and sessions) on one axis and revenue on the other. You see at a glance whether traffic and revenue are moving together or diverging. The dashboard includes summary cards for key metrics: total visitors, sessions, transactions, revenue, and average order value.
The Live view shows the last 30 minutes of activity. You see visitors arriving now, which pages they are on, and which products are being viewed. Live view is useful during campaigns or product launches to spot real-time response.
The Products page lists every product tracked by Pulse, ranked by revenue or views. Click any product to drill into its funnel: list impressions, product page views, basket additions, checkout starts, and purchases. You spot which products convert well and which leak shoppers at each step.
The Transactions list shows every transaction Pulse recorded, with order value, channel, and timestamp. You can filter by date, channel, or product to investigate specific orders.
Channel drill-down pages break down traffic and revenue by marketing channel. You see organic search, paid search, social, email, direct, and referral traffic separately. Each channel shows visitor count, revenue, conversion rate, and average order value.
Setup includes a consent-health statistic. This shows what share of recent analytics events carried valid consent. If consent rates are low, you know your banner is not converting visitors, or your consent logic needs adjustment.
Direct dataLayer capture
If your store is already instrumented for GA4 ecommerce tracking, Pulse can observe your existing dataLayer without re-tagging.
GA4 ecommerce events (view_item_list, view_item, add_to_cart, purchase, and others) are pushed to the dataLayer as JavaScript objects. Pulse can listen for these events, extract the commerce fields, and ignore everything else on the page.
To enable this, toggle 'Observe dataLayer' in Pulse Setup. Pulse will then monitor your site's dataLayer and pick out standard ecommerce events automatically. You do not need to modify your GA4 implementation or rebuild your tag manager container.
This approach saves time if you have already invested in GA4 instrumentation. Pulse reads the same data without duplication or re-tagging.
Who Pulse is for
Vendably Pulse is built for merchants who want commerce-grade analytics without outsourcing shopper behaviour data.
If you run a direct-to-consumer store and want to keep analytics in-house, Pulse avoids the overhead of a separate analytics account and third-party data processor. Your analytics lives alongside your inventory, orders, and customer data in one workspace.
If you have already tagged your store for GA4 but want a privacy-first alternative, Pulse can read your existing dataLayer. You do not need a tag-manager rebuild or a parallel analytics setup.
If your business or market has strict data residency rules (GDPR, UK GDPR, or similar), Pulse's first-party architecture and consent model help you comply. Data never leaves your account. Consent is respected and recorded.
If you want to understand product performance, marketing channel effectiveness, and visitor behaviour without a complex analytics platform, Pulse provides the metrics that matter to commerce in a single dashboard.
Pulse is not a replacement for advanced behavioural segmentation, machine learning attribution, or audience building. It is a focused analytics tool for merchants who need to know what is working on their storefront and why.