Hi, @SonjaPetrik. Are you saying you added HubSpot tracking code onto a Salesforce web-to-lead form? I'm not sure that would work - those forms are designed to always send the record to your Salesforce org first.
In general, using web-to-lead versus HubSpot forms is a tradeoff. Organizations using web-to-lead usually have a specific need for duplicate records on email to exist in their Salesforce org, something that HubSpot won't allow you to do. But without HubSpot understanding the browsing behavior of a record until it converts on a HubSpot form, you lose HubSpot analytics on these web-to-lead submissions.
If you're not doing this on a Salesforce web-to-lead form, but on a native HubSpot form, reach out to HubSpot Support with examples, and they can better diagnose what's happening.
Brad Mampe, Salesforce Analyst, Fidelity I'm probably wrong. I may not be right about that.
Hi, @SonjaPetrik. Are you saying you added HubSpot tracking code onto a Salesforce web-to-lead form? I'm not sure that would work - those forms are designed to always send the record to your Salesforce org first.
In general, using web-to-lead versus HubSpot forms is a tradeoff. Organizations using web-to-lead usually have a specific need for duplicate records on email to exist in their Salesforce org, something that HubSpot won't allow you to do. But without HubSpot understanding the browsing behavior of a record until it converts on a HubSpot form, you lose HubSpot analytics on these web-to-lead submissions.
If you're not doing this on a Salesforce web-to-lead form, but on a native HubSpot form, reach out to HubSpot Support with examples, and they can better diagnose what's happening.
Brad Mampe, Salesforce Analyst, Fidelity I'm probably wrong. I may not be right about that.