ActivityLog lines up website traffic, the content changes behind it and the leads it produced, through to the deals they became.
Publish a page and watch the visits, the campaign that drove them and the leads that followed.
Laura Callahan's case study in the list of content published from the CMS on Monday, with the site's sessions before and after it, and the sessions chart with the publish marked. Visits come from Google Analytics and are anonymous, so this is the whole site's traffic, not one author's; it does not split out campaigns or form submits for a single page.
Sessions by campaign and landing page, conversions, and the path from an anonymous visit to a named lead and a deal.
Sessions and leads per day for the whole site, with website publishes marked on the timeline, and the campaigns table with the sessions each campaign brought. Monday's case-study publish lines up with the spike; the table shows which campaigns drove the traffic.
The pages visitors arrived on, with sessions and form submits for each. A page with many sessions and no submits is getting attention but not leads.
The path from a campaign to sessions, to a form submit that created a HubSpot contact, to a deal. Here a Wednesday form submit became a named lead and a deal opened on Friday. Everything before the form submit is anonymous.
Website numbers come from Google Analytics, page changes from your website's CMS, and leads and deals from HubSpot. Lined up in time, they show which content and campaign led to which lead.
Sessions, page views, scrolls and form submits, with campaign, source, medium, landing page, device type and country.
Through Google Analytics' BigQuery export, which gives each visit as it happened rather than a daily summary.
Pages published and updated, with who published them and when.
The ActivityLog package for Umbraco reports publishes as they happen. Other CMSs can send publishes to the ActivityLog ingest API.
Contacts created from form submissions, with the form and page, and the deals they turn into.
The same HubSpot connection used for sales: record changes sent to a web address you create in ActivityLog.
Google Analytics reports visits, your CMS reports publishes, and HubSpot reports new contacts and deals.
A visit stays anonymous until the visitor submits a form. At that point the form's email links the visit to the new HubSpot contact. Publishes are tied to the staff member who published.
Sessions by campaign and landing page, publishes marked on the timeline, form submits, and the path from campaign to lead to deal.
Writers see what their content did. Marketing puts budget behind the campaigns and pages that produce leads, not just visits.
No. Visitors stay anonymous unless they submit a form and give their email. We do not buy data or match IP addresses to companies.
No. Keep using Google Analytics for detailed web analysis. This page joins its numbers to publishes, leads and deals, which Google Analytics cannot see.
Turn on the BigQuery export in Google Analytics, connect HubSpot and connect your CMS. With the free daily export, today's traffic shows up tomorrow.
ActivityLog is in beta. Connect the tools you already use and get this report for your organisation.
See pricing →Questions first? Talk to us → · All use cases
