topic Re: Best Practice? Workaround for Buyer Intent Reporting in Reporting & Analytics

Best Practice? Workaround for Buyer Intent Reporting

LFrankl — Tue, 09 Dec 2025 09:07:51 GMT

Hi all 🙂

Since we cant use buyer intent data easily for reportings yet, I wanted to ask if some of you have some smart workarounds on how to use buyer intent data to share it easily with your sales/ cs teams (best case in a dashboard or reporting)?

Hidden in the marketing hub it makes no sense to me tbh

Re: Best Practice? Workaround for Buyer Intent Reporting

BérangèreL — Tue, 09 Dec 2025 09:46:34 GMT

Hey @LFrankl 👋 and welcome, it's a pleasure to have you here!

Great question, thanks for asking the HubSpot Community!

- What specific buyer intent data fields or signals are you trying to surface in reports or dashboards?

For new feature suggestions, I'd recommend first to search and check if this idea is already present on our Ideas Forum here. If you find a similar idea, give it an upvote and share your unique use case in the comments.

If the idea doesn't exist already, please consider posting and creating a new Idea on our Ideas Forum here.

Now, let's consult our Top Experts: Hi @karstenkoehler, @Josh and @Gaurav_Aggarwal can you think of a workaround to help @LFrankl, please?

Thanks so much and have a wonderful day!
Bérangère

Re: Best Practice? Workaround for Buyer Intent Reporting

LFrankl — Tue, 09 Dec 2025 09:53:52 GMT

HI:)

I want to see ,how many visits my TAM had on specific pages (showing intent), and how many visits my website had from a specific segment list: In the buyer intent feature we use views based on the defined TAM and some other views based on a segment (our key account list).

For a start, this would already help me 🙂

Re: Best Practice? Workaround for Buyer Intent Reporting

BérangèreL — Thu, 11 Dec 2025 16:34:22 GMT

Hi @LFrankl and thanks for getting back to us!

I'd love to put you in touch with our Top Experts: Hi @Levi, @TomM2 and @PremKannan do you have best practices or workarounds to share with @LFrankl, please?

Thanks so much in advance for your valuable contributions! 🧡
Bérangère

Re: Best Practice? Workaround for Buyer Intent Reporting

RubenBurdin — Tue, 16 Dec 2025 23:12:00 GMT

Hi @LFrankl , you’re feeling a very real gap, and you’re not missing a hidden report. Buyer intent today is powerful, but awkwardly siloed.

Right now, HubSpot treats buyer intent as an insight layer, not a first-class reporting dataset. That’s why you can see TAM or target account activity in the Buyer Intent UI, but you can’t easily drop it into dashboards or combine it with standard web analytics.

The most common workaround I see working well is to materialize intent into properties. For example, create company-level properties like “Buyer intent – pricing page viewed (last 30 days)” or “Buyer intent score.” Then use workflows to update those properties when intent thresholds are met. Once intent lives on the company record, it becomes reportable, filterable, and shareable with Sales and CS like any other firmographic signal (https://knowledge.hubspot.com/workflows/create-workflows).

For your specific use case, TAM and key account traffic, another pattern is list-first reporting. Build company lists that mirror your Buyer Intent segments (TAM, key accounts), then use page view–based workflows or list membership as a proxy. You still won’t get raw anonymous visit counts per company, but you can answer questions like “Which TAM accounts showed intent on page X this week?” in dashboards.

If you want pure visit counts by segment, HubSpot just doesn’t expose that yet. Buyer intent aggregates activity at a signal level, not as explorable event data. Most teams accept this limitation and focus on directional intent indicators for Sales rather than precise traffic metrics.

You’re right to push on this. Until HubSpot promotes buyer intent into the reporting layer, the property + workflow approach is the most practical way to make it visible and actionable outside Marketing.

Re: Best Practice? Workaround for Buyer Intent Reporting

AnnaStanuch — Fri, 02 Jan 2026 11:22:40 GMT

Hi, I have a very similar challenge. I need to create a report for website visits from key accounts. As per the above advice:

1. I made a new number property on the Company object

2. Started a new workflow with the trigger 'Buyer Intent Saved View Event has been completed any number of times anytime'

3. Set the WF action to 'Increase the property value by 1'.

Is it what you had in mind @RubenBurdin ?

Re: Best Practice? Workaround for Buyer Intent Reporting

AnnaStanuch — Fri, 02 Jan 2026 11:27:56 GMT

Btw, I have 13 saved views in Buyer Intent. Will the property be updated each time ANY view gets a new Company or anytime any Company falls into any view filters? What about the segment filter on views? Will the workflow respect that and only edit the property for Companies that are in the segment?

Re: Best Practice? Workaround for Buyer Intent Reporting

LFrankl — Fri, 02 Jan 2026 12:34:04 GMT

Hi Ruben!

Thank you for your detailed response and input.

Based on your suggestions, I've created an static segment of all the visitors to the demo page in the last 30 days (only target accounts). They get added automatically.

Once a company is added to this static segment, a workflow updates a custom field ('demo page visit in last 30 days' = yes), which allows us to generate reports.

What I was wondering is whether, after those 30 days, the companies will remain in the segment since it is static. Would you add another workflow saying 'after 30 days, remove company from segment'?

I hope this makes sense!

Best wishes and a happy New Year!
Laura

Re: Best Practice? Workaround for Buyer Intent Reporting

LFrankl — Fri, 02 Jan 2026 12:39:27 GMT

Ive tried something similiar, Ive added in the workflow Buyer Intent Saved View Event has been completed any number of times anytime' another filter with "name of view", because I had the exact same thought as you.

Unfortunately, the saved view I am intersted in, shows 10 companies, but the workflows doesnt recognize any of them..

But maybe it works with your setup?

Re: Best Practice? Workaround for Buyer Intent Reporting

AnnaStanuch — Fri, 02 Jan 2026 13:46:56 GMT

Ha, I didn't notice the 'view name' filter, thank you!

I think the WF doesn't work retroactively and will only get triggered by new events (even though the trigger says 'anytime'). So we have to wait to see, unfortunately.

Re: Best Practice? Workaround for Buyer Intent Reporting

LFrankl — Fri, 02 Jan 2026 14:54:05 GMT

Please inform me, once it worked for you !:) Fingers crossed for both of us!

Re: Best Practice? Workaround for Buyer Intent Reporting

AnnaStanuch — Fri, 02 Jan 2026 16:49:13 GMT

Will do and please do the same 🙏 Yes, fingers crossed 🤞

Re: Best Practice? Workaround for Buyer Intent Reporting

Victor_Becerra — Mon, 05 Jan 2026 18:39:41 GMT

Hi @LFrankl and @AnnaStanuch

Buyer intent saved view–based workflow triggers are not retroactive. Even though the trigger says “anytime,” the workflow will only fire when a new buyer intent event occurs after the workflow is turned on and matches the saved view (including the view name and segment filters). Existing companies already visible in the saved view won’t trigger the workflow

That’s why you’re not seeing the 10 existing companies picked up right away, and why you’ll need to wait for new intent activity to confirm the setup is working.

Your approach is still valid going forward — just keep in mind that buyer intent works as a signal layer, not historical event data. Most teams pair this with property-based workflows (for forward-looking tracking) rather than expecting a backfill.

Thanks both for testing and sharing learnings here !

Best,

Victor

Re: Best Practice? Workaround for Buyer Intent Reporting

AnnaStanuch — Mon, 05 Jan 2026 19:31:41 GMT

Thank you, Victor! Just one question, if the WF trigger is 'Buyer Intent Saved View Event has been completed any number of times anytime', will the WF run for each page view or each website visit?

Re: Best Practice? Workaround for Buyer Intent Reporting

Victor_Becerra — Tue, 06 Jan 2026 22:17:36 GMT

Hi @AnnaStanuch , great question!

The workflow trigger does not run for each individual page view or website visit. It runs each time a buyer intent event is generated for a company that matches the saved view criteria.

In practice, that means:

Buyer intent aggregates underlying activity (page views, sessions, signals) into an intent event.
Your workflow will fire once per intent event, not once per raw visit or per page load.
Because of that, increasing a numeric property by 1 reflects intent occurrences, not exact visit counts.
If your goal is precise visit-level reporting, that data isn’t currently exposed via buyer intent. Most teams use this setup for directional signals (e.g. “account showed intent again”) rather than exact traffic metrics.

Hope this helps clarify how the trigger behaves —Let me know how it goes!

Best,
Victor

Re: Best Practice? Workaround for Buyer Intent Reporting

AnnaStanuch — Wed, 07 Jan 2026 11:47:18 GMT

Thank you, Victor. It's very interesting, but I have just checked the Buyer Intent view, and it shows a company with Visitor Intent and 6 visited pages (after the WF was activated for sure). Yet, it didn't trigger the WF.

@LFrankl did you get any triggers?

Re: Best Practice? Workaround for Buyer Intent Reporting

AnnaStanuch — Wed, 07 Jan 2026 12:49:44 GMT

@Victor_Becerra I have just noticed now that there is an option to add an automation to a BI view. Does the WF need to be added here for the trigger to work?

Re: Best Practice? Workaround for Buyer Intent Reporting

Victor_Becerra — Wed, 07 Jan 2026 22:17:05 GMT

Hi @AnnaStanuch

Great catch — that detail is actually the missing piece here, so you’re right to question it.

Yes: for Buyer Intent saved view–based workflows to fire, the automation must be added directly from the Buyer Intent saved view itself (using the Add automation option you spotted). Creating a workflow separately with the “Buyer Intent Saved View Event” trigger is not sufficient on its own unless it’s explicitly linked to that saved view.

A few key clarifications to tie it all together:

Buyer Intent workflows are view-scoped, not just condition-scoped

The saved view is effectively the “event source”

If the workflow isn’t attached to the view via Add automation, intent events from that view won’t trigger it

This is why you can see companies accumulating visited pages in the view, but the workflow never fires

Once you attach the workflow directly from the Buyer Intent view:

New intent events that occur after that point should trigger correctly

Existing intent already aggregated in the view still won’t backfill (as discussed earlier)

You’re absolutely on the right track — this is one of those UX details that’s easy to miss and not very well documented yet.

Let us know what you see after attaching the automation 👍
Best,
Victor

Re: Best Practice? Workaround for Buyer Intent Reporting

AnnaStanuch — Thu, 08 Jan 2026 10:06:12 GMT

Thank you, Victor.

Two companies have gone through the WF since I added the automation in BI, yay. When I check the enrollment history, it says that 'Saved View Action is any of enter'. Does 'enter' mean 'entered the view'? Indeed, those two companies and nothing else have entered the view.

If so, the trigger wouldn't be some mysterious 'aggregated underlying activity' but simply a visit to the website because that's how my view is set up.

Re: Best Practice? Workaround for Buyer Intent Reporting

LFrankl — Thu, 08 Jan 2026 13:45:02 GMT

Hi Anna 🙂 yes, two companies entered the workflow, which is the same number as in the saved view.

Right now, I am now thinking about how to work with this information in the future. I want to hand over to sales, which companies from our target account list have been on our demo landingpage in the last 30 days.

When you think like that, normally after 30 days the information should be deleted again.. Maybe a workflow can do this here for me as well (?)

How do you work with it?