I hope you are doing well. We need assistance with an issue that has come up after we transitioned from using Hapikey (v2 version) to a Private App (v3 version) for our API calls. Since this change, we’ve had trouble tracking Google and Facebook leads in our HubSpot contacts list.
Previously, using [specific code], tracking for Google contacts worked correctly with the v2 version. However, after switching to the v3 version, the tracking no longer differentiates properly between Google and Facebook leads. Instead, [specific code] seems to aggregate contacts from both sources under a single filter in the HubSpot contacts list, specifically under the “Original source drill-down 2” filter option.
Could you help us resolve this issue so that we can correctly track and differentiate leads coming from Google and Facebook separately, as we did before?
Your prompt attention to this matter would be greatly appreciated.
Hi @SKundu6,
It sounds like the issue you’re facing with tracking Google and Facebook leads in HubSpot occurred after transitioning from Hapikey (v2) to a Private App (v3).
1. Check the parameters being sent with the v3 API calls, especially for identifying Google vs. Facebook leads.
2. Ensure the correct properties (utm_source, utm_medium, source, etc.) are included and properly formatted in the data payload.
3. Ensure your API calls to the v3 version are correctly mapping to HubSpot’s contact properties.
4. Include explicit parameters to differentiate leads (like hs_analytics_source or custom properties if needed).
5. Review and update any workflows, filters, or settings in HubSpot that use these lead sources.
6. Make sure your “Original source drill-down 2” field in HubSpot is configured correctly to differentiate Google and Facebook leads.
7. When transitioning to v3, you may need to remap fields that are used for tracking in HubSpot. Double-check the mapping in your API integration settings.
8. Conduct tests by manually creating or importing leads with specific source parameters to confirm that they are being tracked and categorized correctly.
9. Review the HubSpot API documentation for any notices about deprecated fields or functions between v2 and v3.
10. If the problem persists, contact HubSpot support with specific details of your API calls, payloads, and any error messages you’re receiving. They can provide specific guidance or updates on any known issues.
We have implemented a “Javascript Cookie” concept on our website pages to track the “utm_source” of visitors coming from Facebook or Google ads. This “utm_source” is then sent to the Deal creation API call and stored in a custom property called “contact_source.” While this logic works for some contacts, it does not consistently capture the source for all contacts coming from Facebook or Google ads.
We are using Private App concept in version 3, we are using PHP CURL call concept. Following are the sample:
Apart from above logic, we have used the JavaScript tracking script throughout the pages of the website:
<!-- Start of HubSpot Embed Code -->
<!-- <script type=“text/javascript” id=“hs-script-loader” async defer src=“//js.hs-scripts.com/HUBID.js”></script> -->
<!-- End of HubSpot Embed Code -->
This script serves to display the HubSpot chat option on the website and also facilitates the storage of contact source indicators (e.g., Paid social, Paid search) in the ‘Original source drill-down 2’ filter option in V2.
Should you require further details, please don’t hesitate to ask, and we’ll gladly provide additional information.
Here are few points that may cause the error -
1. API token not used properly.
2. UTM Sources are not correctly used.
3.Mismatching of data under API.
4. HubSpot property is not correctly updated.
I hope this will help you out. Please mark it as Solution Accepted and upvote to help another Community member.
Thanks!
Hi @GRajput ,
Thank you for your response.
We have double checked following things:
1. API Token Usage: The API token has been correctly configured, but the integration isn’t functioning as expected.
2. UTM Sources: All UTM sources are set up properly, yet they don’t seem to be tracking or reporting correctly.
3. Data Mismatch: There appears to be a discrepancy in the data being passed through the API, even though the configurations match.
4. HubSpot Property Updates: The HubSpot properties are supposed to update automatically via the API, but this isn’t happening consistently.
I’ve double-checked all settings and configurations, but the issues persist. Could you provide guidance on what might be causing these issues?