Hey guys, how are you doing?
I’m kinda new to hubspot and wasn’t abble to find what I’m looking for on the documentation.
I want to use hubspot to track my backend funnels. The idea is that the contact will enter my hubspot database once they buy my front end product, and then my comercial team will try to schedule a meeting with them to offer the backend product.
However, I couldn’t find a way to track what front end product the contact brought in order to enter my database. Is there a way to add something like a “source” field or something like that?
Hi @PASSIS0, I hope that you are well!
Great question, thank you for asking the Community!
I’d like to ask some clarifying questions please.
1. How do they buy the front end product? By submitting a form? Via an online shop?
2. If you are using a form, is this a HubSpot form? Or an external form?
3. The website you are using is a HubSpot page or an external website?
4. Did you create a custom property for the products? Or are you using the line items in deals/quote?
The more info, screenshots (without sensitive/confidential information), and details you can provide, the better the Community can assist.
First, I’d like to share these articles that explain and give information about the sources properties in HubSpot:
- Understand HubSpot’s traffic sources in the traffic analytics tool
- Understand Original and Latest source properties
I also found similar posts that might help you:
- The solution from @Aakar on this post “Tracking the source of Form Submissions”
- The solution from @karstenkoehler on this post “Form submission Source tracking”
- The solution from @trevordjones on this post “Track Hubspot forms submission in Google Analytics”
I also wanted to invite a couple of subject matter experts to this conversation: Hi @danmoyle, @deepikaverma and @Ian_Matt do you have suggestions to help @PASSIS0, please?
If anybody else has anything to add and/or share, please feel free to join in the conversation 
Thank you so much and have a fantastic day!
Best,
Bérangère
Hi @PASSIS0 and thanks for the tag @BérangèreL !
What I would do is create a Deal Property Called “Front End Deal” on the deal record.
If you’re not already, I would automatically create deals in your back-end pipeline when the front end deal is closed using pipeline automation or just a workflow.
Trigger: Deal in Pipeline “Front end Products” reaches closed won.
Action: Create Record (Deal) in Pipeline “Back End Products.”
Set the values you need to from the standard stuff, but also click “Add More Properties.”
Click the radio button to “Copy a property to a deal property.”
Copy the Record ID of the Existing Deal to the Property “Front End Deal.”
Now deals are automatically created in the back end pipeline with a property to identify the front end deal they were connected to.
You may need to play around with this to see what works best. Record ID’s have numeric values so they can be clumsy for reporting, and they are also unique for every deal. You might do better, for example, to copy the owner of the Front End Pipeline Deal to the Back End Deal, since this is a shorter list of individuals, or perhaps you have a deal type or some other field you are using the segment your front end deals,
Hey @PASSIS0 and welcome to HubSpot and the Community!
Your frontend product - is this something you can add to HubSpot? They have a Product object, used for selling products & services. The bonus here is that you can even take payment.
Another option is that yes, you could create a custom property that you mark off as a source by product. HubSpot automatically measures sources, but a custom property in the Deal object could help you with it as well. It would be a manual process, but you’d be able to segment your Deals by that.
Property types could be a dropdown menu where only one choice is possible, or multiple checkboxes, where you could choose more than one frontend product if you have multiple options.
I also like the approach from @trevordjones.
Hi @danmoyle ,
Great thoughts on the product object! I think the main reason I don’t use it more in situtions like this is that our ability to manipulate deal line items with automation (and without code) is so limited, whereas custom properties and new deal records can be created within workflows.