Proprietary form adds contacts as Offline Sources instead of the proper traffic source attribution
SOLVE
Hi,
I run a tech company and we have built our own form process for the creation of accounts on our application. We integrated the hubspot API to add any contacts that sign up through this form to hubspot. The issue is that when we upload the contact, instead of connecting the user who submitted information through our proprietarily built form to the hubspot pixel (which would provide correct traffic source attribution), it adds the contact as "Offline Integrations".
What are we doing wrong? How do we fix it so that our form is able to add a contact into hubspot and connect it to the proper hubspot pixel for traffic source attribution?
The best approach I have scene for the scenario you describe is to use HubSpot's Forms API.
By passing the HubSpot user token along with the API call, you will ensure that a contacts original source is captured and passed into HubSpot. This does require the HubSpot tracking code to be installed and working on your account creation / sign up page.
Hope that helps.
Frank
Found my comment helpful? Great! Please mark it as a solution to help other community users.
The best approach I have scene for the scenario you describe is to use HubSpot's Forms API.
By passing the HubSpot user token along with the API call, you will ensure that a contacts original source is captured and passed into HubSpot. This does require the HubSpot tracking code to be installed and working on your account creation / sign up page.
Hope that helps.
Frank
Found my comment helpful? Great! Please mark it as a solution to help other community users.
Aug 30, 20237:10 PM - edited Aug 31, 20239:01 AM
Contributor | Elite Partner
Proprietary form adds contacts as Offline Sources instead of the proper traffic source attribution
SOLVE
Unfortunately for HubSpot's Original Source and Latest Source, the values will be set to "Offline Sources" since the contact is coming through an API. There are a couple ways to work around this:
Use the Original Source Drill-down 1, Original Source Drill-down 2, Latest Source Drill-down 1, Latest Source Drill-down 2 to see attribution.
Set up a custom property that refines the attribution sources. This would let you assign the value directly via the API on form submit, and create a set of workflows to funnel other sources into the correct buckets using the Original and Latest Source properties.
This is the relevant documentation on the Original and Latest Source