You’re probably already being asked to prove it. Not in a hostile way, necessarily, but the question is there. In budget reviews, in planning meetings, in that moment where someone asks why content investment hasn’t shown up in pipeline yet.
And the honest answer is: it’s not that content isn’t working. It’s that you can’t clearly show how it’s working. Last-touch says the demo came from direct. GA4 tells you a blog post got 400 sessions. Both are true. But the link between them, how someone actually moved from reading that post to becoming a qualified opportunity, is missing. So you end up with activity on one side, revenue on the other, and no clean way to connect the two.
This post is about fixing that. Specifically, how to connect GA4 and HubSpot through AttributeIQ so you can take any demo and see exactly which blog posts played a role in getting it there.
Three Things to Have Ready Before Your First Blog Attribution Report
This isn’t a lengthy technical setup. But there are three things that need to be in place before AttributeIQ can connect your blog content to real pipeline, and it’s worth knowing what they are and why each one matters before you start the clock on your trial.
Setting Up AttributeIQ to Track Blog-to-Demo Attribution End to End
This setup takes under fifteen minutes and lets you trace demo requests back to the blog posts that influenced them.
Step 1: Connect Your GA4 Property to AttributeIQ
Once you’ve created your AttributeIQ account, the first thing you’ll do is connect GA4. This takes about three minutes and requires no engineering involvement.
AttributeIQ will ask you to select which GA4 property to connect. If you have multiple properties, pick the one where your blog and demo form live, if they’re on different properties, start with the one where the demo form fires.
Select Your GA4 Property
What AttributeIQ does with this connection:
AttributeIQ doesn’t read from the GA4 interface, it reads from your raw BigQuery event export. This matters because the GA4 interface shows you sampled, aggregated data. BigQuery has every individual event, every session, every page view, unsampled and in full. That’s what makes individual journey reconstruction possible. When you see a journey in AttributeIQ, it’s not a model or an estimate, it’s a real sequence of real page views from a real browser session.
Step 2: Connect HubSpot to Match Journeys to Real Deals
GA4 alone can tell you which pages were visited by users who converted. What it can’t tell you is who those users were, what company they’re from, or what deal value is attached to their journey. That’s what HubSpot unlocks.
Go to Settings → Integrations → HubSpot inside AttributeIQ and click Connect HubSpot. You’ll be taken through a standard OAuth flow, authorise access, get redirected back, and you’ll see your portal ID confirmed and the status showing “Connected.”
The matching logic:
When a buyer submits your demo form, two things happen simultaneously. GA4 records a demo_request event tied to a GA4 client ID. HubSpot receives the form submission and creates or updates a contact. AttributeIQ captures both events, reads the ga4_client_id from the form submission, writes it to the HubSpot contact property, and from that point forward every GA4 session associated with that client ID is connected to that named contact and their deal.
One thing worth flagging: This matching is forward-looking. Contacts who converted before you installed AttributeIQ won’t have a ga4_client_id attached, so their historical journeys won’t be visible.
Step 3: Find Your Demo Conversions in the Multi-Touch Tab
Now the interesting part. Go to Multi-Touch Attribution in the left nav. This shows you every page that appeared across every converting journey, filtered by the role they played in driving the demo.
Property
Attribution
Account
jent@nexa.com
AttributeIQMulti-Touch Attribution
See every page influencing conversions, with journey position breakdown.
Total Conversions
46
Avg Journey Length
1.1
Most Influential
/blog/ai-seo-...
Top Mid-Journey
/blog/measuring-...
Page Coverage
Reach by page (% of converting journeys). Colour = journey role
Here’s what each part of the dashboard is telling you:
See which content pieces
actually influenced your deals.
AttributeIQ shows page-level pipeline attribution natively over your existing GA4 and HubSpot stack, live within 24 hours.
Try 14 days for free →Step 4: Click Into Any Page and See Every Journey That Ran Through It
Click the chevron next to any page in the table and AttributeIQ expands every converting journey that included it, in full, in order, with dates and days-to-convert.
You can see exactly what a buyer read before they requested a demo, what they came back to, and where your blog post sat in the sequence relative to everything else.
JOURNEYS THAT INCLUDED /BLOG/SALES-PIPELINE-STAGES: 22 JOURNEYS
If you’re on Pro, the expanded journeys don’t just show anonymous page sequences. They show the contact name from HubSpot and the deal value. Buyer #1 becomes Marcus Webb, £8,000.
JOURNEYS THAT INCLUDED /BLOG/SALES-PIPELINE-STAGES: 22 JOURNEYS
And because AttributeIQ has the full HubSpot deal record, you can also see what happened after the demo, the post-conversion milestones through to closed revenue.
BUYER #2 · ELENA VASQUEZ
scheduled7 Jun
Step 5: Set Up Slack Alerts for High-Intent Blog Behaviour
A lot of buying activity happens between meetings. Prospects disappear for a few weeks, go quiet in email, then start revisiting content as they build an internal case, compare vendors, or prepare for the next conversation. If you’re only looking at CRM updates, you’ll miss most of it.
The screenshot above shows an example of what a few Alert Rules might look like in practice, one scoped to /blog/ visits from qualified contacts, another watching /pricing, a third flagging deals that have gone inactive for two weeks. The exact rules depend on your sales motion, but the pattern is the same: pick a URL, scope it to the right contact stage, and route it to Slack immediately.
Turning Blog Attribution Data Into Measurable Pipeline Impact
Running attribution without changing anything downstream is just expensive reporting. Once you can see which posts appear in demo journeys and which don’t, there are three decisions that should follow immediately, before you commission another brief, before you push another post into distribution, before you tell your team that content is working.
The three decisions above are only possible because the data finally exists to make them. For most content teams, that’s the missing piece, not the strategy, not the briefs, but the evidence that tells you which of those things is actually working. That’s what AttributeIQ shows, natively, over the GA4 and HubSpot stack you’re already running. Free trial is fourteen days, no card required. Sign up here.
