I have an internal site that is only accessible via SSO.
The site visitors are salespersons who refer contacts and deals to my team.
My team of 10 are the only users of HUBSPOT... while the 2,000 salespeople are visitors of our site and contacts inside of our CRM. (Contact Type = Salesperson)
Our sales people need the ability to submit their referrals and have contact records created in our account (Contact Type=Client). I have a workflow that automates the association between the Reffering Sales Person and the Referred Client.
My issue is that i have them use a form that creates new contacts for every email that is submitted..... that's great except for that everything they do on our site, is then recorded on the New contact.
My question(s) - Is there a way to have the referring salespersons create new contacts without transfering the tracking mechanisms to the newly created contacts?
I thought that with the Microsoft SSO login, their identity would remain locked/associated via their work email address no matter what activity was created.
In essence, isn't SSO protected/private contact the same as having a login & Password?
It's hard to comment on the exact expected behavior here without have more details about how this page is set up and without more information about your SSO and overall environment.
If you have the tracking code installed AND if you're using a HubSpot form AND if you don't want submissions on that form to be tracked, then you would have to block the execution of the HubSpot tracking code on that particular page. That seems like the easiest and most straightforward solution here.
Best regards!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
It's hard to comment on the exact expected behavior here without have more details about how this page is set up and without more information about your SSO and overall environment.
If you have the tracking code installed AND if you're using a HubSpot form AND if you don't want submissions on that form to be tracked, then you would have to block the execution of the HubSpot tracking code on that particular page. That seems like the easiest and most straightforward solution here.
Best regards!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer