The Visitor Identification API is now in public beta! You can read more about it and get started here. This is open to all Pro+ portals as of now, no need to be ungated.
The newVisitor Identification APIenables you to provide details about visitors' identities to the chat widget after they've been authenticated by an external login system. So, if a visitor logs in (by providing their email address), the Visitor Identification API can send their identity to HubSpot's chat widget.
This API also works automatically with HubSpot's private content membership for CMS Hub or Knowledge Base, no additional setup required!
Please let me know if you have any questions or feedback. This API is still in beta, by using this API you agree to our developer beta terms.
Why is this limited to Pro+ only subscriptions? This seems more like a bug fix than a feature to me as a consumer of the product. I have embedded live chat on my site but cannot track who that person is when they reach out even if I know who they are.
@prafful54 sorry that is your portal number. You can find that in the URL. If you can't find it you can leave it blank and we can find it on our end. I will update the form to be a bit more clear.
Hey all, we recently came out with a Conversations JavaScript API, where you wouldn't have to refresh the page. This is great for SPAs because now you can just refresh the widget and not the page itself. After some quick testing on a page of my own, I was able to identify the contact, refresh the widget programmatically, then have the ability to see the contact's email address within the Conversations tool.
We still can't use personalization tokens inside the chat unless you're using bots, but now the contacts you identify won't show up as "Anonymous Visitor". Here's the code I used:
function onConversationsAPIReady() {
var _hsq = window._hsq = window._hsq || [];
console.log("ready")
_hsq.push(["identify",{
email: "test@testing.com" }]);
_hsq.push(['trackPageView']);
setTimeout( () => {
console.log("refresh")
window.HubSpotConversations.widget.refresh();
}, 1000)
}
function sendIdentify(){
if (window.HubSpotConversations) {
onConversationsAPIReady();
} else {
window.hsConversationsOnReady = [onConversationsAPIReady];
}
feel free to keep testing, but just wanted to make sure you were aware of this new JS API we have.
Theidentify method critical to the approach HubSpot Developer Support has heretofore positioned on the Community only directly updates the hubspotutk cookie with the visitor's identity.
The conversations (live chat) tool uses a different cookie — messagesUtk— to populate visitor names. If this cookie is not associated with any identity information, a chat will come in under an "Unknown Visitor."
HubSpot currently has a back end process which associates the hubspotutk identity information with themessagesUtk cookie, but calling theidentifymethod does not always trigger this process.
As such,there is currently no way to guarantee that a chat won't come in under an "Unknown Visitor,"even with the method outlined above, which works much of the time.
Our team is working on a dedicated solution for this use case but we currently can't offer a concrete timeframe. Please subscribe to the API Changelog to be notified of the update when it is released.
Apologies for the confusion and thank you in advance for your understanding.
Hi Isac, im currently evaluating hubSpot and reading the current thread, but I'm not 100% sure I'm getting the issue, in my case I need to identify 100% a user chatting, my site is built with angular and people logs in using Facebook and some simple data, but I need to guarantee that every time a logged user types in a chat, the operator knows exactly who the person is, and on which part of the web site the person is located
We hear you and recognize how critical it is to reliably identify visitors in chats.
@cdewey22 and her team still view this feature as a priority and are aiming to release some functionality in beta in the next handful of weeks. Please stay tuned to this thread and the platform changelog for updates.
In the meantime, the admittedly imperfect workaround I've outlined above is the next best approach.
I don't recommend you use hubspot then. We have been waiting for this to be fixed for months now. With no real update. If you use case is as you describe you can't use Hubspot as it does not work.
Hey Jonathan, thanks a lot for your message, any ideas on how to move forward? I'm currently trying tawk.to and have managed to get some stuff working but it just chat, what about using the js api for HubSpot to handle page events and sales process and a third party chat? or would be better to look for something like FreshSales