topic Re: Cant do Facebook ad reports with Heyflow and Hubspot in Marketing Integrations

Cant do Facebook ad reports with Heyflow and Hubspot

Privatesickpay — Wed, 24 Apr 2024 11:04:18 GMT

Hi everyone,

We are trying to track the leads our Facebook ads generate accurately in Hubspot marketing.

We are using Heyflow forms after someone clicks the Facebook ad to capture leads.

Our facebook account is integrated with hubspot. It is tracking the inpressions and clicks per ad but not our leads generated.

So we don't have cost per lead in hubspot for reporting.

The contacts are arriving in our Hubspot, and Heyflow is (supposedly) integrated properly ( we are getting no errors). But the contacts are not being attributed to the Facebook ads they are coming from in Hubspot.

We are getting leads and tracking them through emails we receive from Heyflow. and there is information in the email showing the utm parameters which ad the lead came from. In the image attached it shows utm_campaigm 'PSP51' - which is the name of our campaign.

When we go into the contact activity in hubspot - it just says the contact was created by paid social. There is no other ad activity in there.

Thank you for taking the time to read this.

Re: Cant do Facebook ad reports with Heyflow and Hubspot

PamCotton — Wed, 24 Apr 2024 19:51:53 GMT

Hey @Privatesickpay, thank you for posting in our Community!

Since you're seeing UTM parameters in the emails received from Heyflow, ensure that these parameters are being correctly passed to HubSpot. This includes verifying that the UTM parameters are captured and associated with the respective contacts in HubSpot upon form submission. Also, review your attribution settings in HubSpot to ensure that leads are appropriately attributed to the correct campaigns or sources, especially those coming from Facebook ads. Adjustments may be needed to ensure accurate reporting.

To our top experts, @Jnix284, @JWingate2, and @RSchweighart do you have any recommendations for @Privatesickpay matter?

Thank you,

Pam

Re: Cant do Facebook ad reports with Heyflow and Hubspot

Privatesickpay — Thu, 25 Apr 2024 17:15:33 GMT

Hi Pam,

First of all thank you for commenting on my post so quickly.

What would be some actionable steps we could take to follow your advice when you say "verifying that the UTM parameters are associated with the respective contacts in HubSpot upon form submission."

As far as we can see the utm parameters are not being passed on to hubspot and we don't know exactly why or where the point of failure is for this.

Which settings should we check in Hubspot to check "our attribution settings in HubSpot to ensure that leads are appropriately attributed to the correct campaigns or sources".

If there's any more useful info I can provide please let me know.

Thanks so much for your time and effort.

Best regards,

Re: Cant do Facebook ad reports with Heyflow and Hubspot

RSchweighart — Thu, 25 Apr 2024 18:10:41 GMT

Hi @Privatesickpay,

These are some good questions, Daniel.

The Source property is set by HubSpot (see details here).

Have you ensured the HubSpot tracking code has been added to your website?

https://knowledge.hubspot.com/reports/install-the-hubspot-tracking-code

Check out this article if you are on Marketing or Content Hub Pro or above: https://knowledge.hubspot.com/settings/how-do-i-create-a-tracking-url

If the code or tracking help articles don't get you what you need, you may simply add contact properties in HubSpot corresponding to the parameters you want to track in HubSpot. Then, you could map the utm parameters from Heyflow to the new utm contact properties in HubSpot in the integration page you screenshot.

Here's an article on how to create properties if you're unfamiliar with the process: https://knowledge.hubspot.com/properties/create-and-edit-properties

Please let me/us know if this misses the mark on what you're trying to accomplish.

Best,

Ryan Schweighart

Whole Hart Impact, LLC

whimpact.co

I help businesses with HubSpot and Zapier.

Re: Cant do Facebook ad reports with Heyflow and Hubspot

Privatesickpay — Mon, 29 Apr 2024 16:54:14 GMT

Dear Ryan Schweighart,

Thanks for providing so much suggestions.

We have installed our tracking code and checked it is firing properly.

I dont fully understand how creating custom contact parameters in Hubspot would help with attribution to facebook ads in hubspot marketing.

Our leads coming into hey flow even have the "hubspot hsa parameters". I have attached a screenshot coming from the emails Heyflow sends for every lead we get.

Thanks so much for your help so far. If anyone knows any useful and relevant info relating to this problem please let us know.

Best regards,

Dan

Please see screenshot attached.

Re: Cant do Facebook ad reports with Heyflow and Hubspot

LeonWi — Tue, 25 Mar 2025 19:29:27 GMT

Hi Dan,

I have been struggling with the exact same issue as you are describing. Did you find any solution to your problem or identify any workaround that can be integrated?

Thank you very much,
Leon

Re: Cant do Facebook ad reports with Heyflow and Hubspot

Sweely — Mon, 06 Oct 2025 17:01:07 GMT

The short answer is:

Your problem is that the UTM parameters are being received by Heyflow, but they are not being passed from Heyflow to HubSpot in a way that HubSpot's native attribution logic recognizes, so HubSpot defaults to a vague "Paid Social" source.

The key is that the native Facebook-HubSpot integration tracks clicks and impressions but relies on the HubSpot tracking code being present on the final form page and capturing the full visitor journey.

Since Heyflow is an embedded or external form, it's breaking this chain.

The solution Ryan suggested is the immediate fix: Create custom contact properties in HubSpot (e.g., `Original UTM Campaign`, `Original UTM Source`), and then map the UTM parameters from the Heyflow submission directly into those custom fields.

This will ensure the data is saved with the contact even if the official attribution is broken.

However, a better, long-term solution involves an advanced server-side setup using the HubSpot API and the Facebook Conversions API to fix the attribution and the reporting accuracy at the source ✅

The long answer is:

The reason your contacts are being vaguely attributed to "Paid Social" is twofold.

First, HubSpot's native Facebook Ads integration primarily handles the upper-funnel data - the impressions and clicks - directly through the ad account connection.

For contact attribution, HubSpot relies on its own tracking cookie and its JavaScript tracking code to link the contact record to the original ad click via the hsa parameters (which you correctly identified as being present in your Heyflow email).

When the lead is captured on a page where the HubSpot tracking code is not fully functional or the form data is passed through a third-party intermediary like Heyflow that doesn't explicitly pass the hidden `hutk` (HubSpot tracking cookie) or the `hsa` data with the submission, HubSpot's native attribution logic fails.

It then defaults to the next best known source, which in your case is the general Paid Social category, because it knows the visit came from a Facebook ad click but can't resolve the specific campaign.

Ryan's advice to create custom contact properties and map the UTMs from Heyflow is the necessary first step to ensure you at least save the `utm_campaign` data, allowing you to manually report on it in HubSpot using custom reports.

To fully restore the official attribution and unlock the cost per lead reporting in the HubSpot Ads tool, an excellent solution is to implement a server-side pipeline using the HubSpot API, Heyflow Webhook or Events API, and the Facebook Conversions API, managed through Google Tag Manager and a service like Stape or Google Cloud Platform.

When a lead completes the Heyflow form, instead of relying solely on the native Heyflow-HubSpot integration, Heyflow can send a webhook containing the lead data, including the UTMs and hsa parameters, to your server environment.

This server can then use the HubSpot API to explicitly create or update the contact record, passing the hsa parameters and the UTMs directly, which often fixes the attribution.

Crucially, the server can also use the Facebook Conversions API to send a `Lead` Standard Event back to Facebook, including the `fbc` and `fbp` browser IDs (which are present in the hsa parameters).

This ensures that Facebook is correctly logging the conversion event, and that this high-quality, server-side data is used to improve Facebook's own optimization and reporting, which in turn feeds better data back to the HubSpot Ad Integration via the Facebook connection.

This comprehensive API-to-API approach ensures both Facebook and HubSpot receive the precise attribution data they need to report cost per lead accurately.

This comment was generated with the assistance of an AI tool, incorporating my expertise in conversion tracking 🙂