# Issues with lead attribution using 3rd party form

**URL:** <https://community.hubspot.com/t/issues-with-lead-attribution-using-3rd-party-form/146477>\
**Category:** Lead Capture Tools\
**Tags:** professional\
**Created:** [February 20, 2026, 9:06am UTC](https://community.hubspot.com/t/issues-with-lead-attribution-using-3rd-party-form/146477 "2026-02-20T09:06:40Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![AbhiGetastra](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/abhigetastra/32/213676_2.png) [@AbhiGetastra](https://community.hubspot.com/u/AbhiGetastra)\
**Post date:** [February 20, 2026, 9:06am UTC](https://community.hubspot.com/t/issues-with-lead-attribution-using-3rd-party-form/146477/1 "2026-02-20T09:06:40Z")

</div>

Requesting your support with an issue we’re facing with HubSpot tracking for a third-party form. As per the instructions shared in HS documentation to track leads, we’ve added the tracking code in the \<head\> tag and also tested placing it just before the closing \<body\> tag. The tag is visible in the page source on [getastra.com](http://getastra.com) and appears to be installed correctly. However, form submissions are not being captured automatically in the HubSpot source field. Could you please help us understand what might be going wrong and what changes are needed to ensure the data flows correctly into HubSpot?

---

<div class="post-metadata">

**Author:** ![Berangere](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/berangere/32/220784_2.png) [@Berangere](https://community.hubspot.com/u/Berangere)\
**Post date:** [February 20, 2026, 12:42pm UTC](https://community.hubspot.com/t/issues-with-lead-attribution-using-3rd-party-form/146477/2 "2026-02-20T12:42:54Z")

</div>

Hi @AbhiGetastra and welcome, it’s a pleasure to have you here! 🧡  
Thanks for asking the HubSpot Community!  
HubSpot can track many 3rd‑party forms automatically, but only if the Non‑HubSpot forms feature is enabled and the form meets a few technical requirements.  
Sometimes, simply adding the tracking code isn’t quite enough, but we’re here to help you get everything set up smoothly!  
Here are some resources that I’d recommend you to check:  
- [Use non-HubSpot forms](https://knowledge.hubspot.com/forms/use-non-hubspot-forms)  
- [Non-HubSpot forms | Frequently Asked Questions](https://knowledge.hubspot.com/forms/non-hubspot-forms-faq)  
I’d love to put you in touch with our Top Experts: Hi [@Jake\_Lett](https://community.hubspot.com/t5/user/viewprofilepage/user-id/72866), @FrancoisSmit777 and @TomM2 do you have suggestions to help @AbhiGetastra, please?  
Thanks so much and have a brilliant day!  
Bérangère

---

<div class="post-metadata">

**Author:** ![AGhost5](https://avatars.discourse-cdn.com/v4/letter/a/eb8c5e/32.png) [@AGhost5](https://community.hubspot.com/u/AGhost5)\
**Post date:** [February 20, 2026, 1:50pm UTC](https://community.hubspot.com/t/issues-with-lead-attribution-using-3rd-party-form/146477/3 "2026-02-20T13:50:36Z")

</div>

The form is a static HTML form.  
The form is wrapped in HTML \<form\> tags.  
The form has an email input field.  
The form is using a standard input type=“submit” button for its form submissions.  
The form is not in an \<iframe\>.  
The form is not have JavaScript bound to the form submit event or submit button click event. We are just scheduling the meeting with the help of revenue hero.  
The form is not introduced after the page completed loading.  
The form does not contain a sensitive field, such as a credit card number or any hidden fields.  
We have the **Collect data from website forms** turned **ON.**

 ![image.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/9/7/9703f6c7efc50003180eebd59bb2f571c1f97fca.png)

---

<div class="post-metadata">

**Author:** ![nssekar](https://avatars.discourse-cdn.com/v4/letter/n/7bcc69/32.png) [@nssekar](https://community.hubspot.com/u/nssekar)\
**Post date:** [February 23, 2026, 12:56pm UTC](https://community.hubspot.com/t/issues-with-lead-attribution-using-3rd-party-form/146477/4 "2026-02-23T12:56:25Z")

</div>

![hubspot-tracking-failed.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/0/4/044b84423b89c3ca5c3b24e3100cb27d226fe5bb.png)

 ![organic attribution - not tracked properly.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/0/3/03cb328831d6ddb40543bf81444534d05382c62f.png)

Hi Hubspot Team,

My colleagues have been following up on the above thread regarding the attribution issue for the past two weeks; however, it is still not resolved.

Please refer to the attached screenshots:

1. The HubSpot tracking code validation has failed for the entire website.

2. I also tested the form via organic traffic in incognito mode, and the original source attribution is showing as an offline source.

Kindly treat this as a high priority and resolve the tracking issue at the earliest.

---

<div class="post-metadata">

**Author:** ![Berangere](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/berangere/32/220784_2.png) [@Berangere](https://community.hubspot.com/u/Berangere)\
**Post date:** [February 25, 2026, 5:19pm UTC](https://community.hubspot.com/t/issues-with-lead-attribution-using-3rd-party-form/146477/5 "2026-02-25T17:19:17Z")

</div>

Hi @nssekar and thanks for sharing these details and the screenshots.  
For urgent issues like tracking code validation and lead attribution, the best next step is to [contact our Support Team](https://help.hubspot.com/) directly, they have access to your account specifics and can provide a faster resolution.

Thank you for your patience and for flagging this with us.  
Bérangère

---

<div class="post-metadata">

**Author:** ![DLwarance](https://avatars.discourse-cdn.com/v4/letter/d/3be4f8/32.png) [@DLwarance](https://community.hubspot.com/u/DLwarance)\
**Post date:** [February 20, 2026, 9:17pm UTC](https://community.hubspot.com/t/issues-with-lead-attribution-using-3rd-party-form/146477/6 "2026-02-20T21:17:30Z")

</div>

Check if the form is in an iFrame. My company had this issue last month and the tracking script can’t “see” inside most iFrames. You might need to use a tracking URL or a different integration method.