We just implemented live chat on our site and want to make sure we identify the people using the live chat. Please send me the beta
I tried the widget refresh code and it does not work.
Any updates on the beta? I signed up but havent heard anything back yet.
Hi @gugahoi! The beta is still very small and will be opening up over the coming weeks. We expect to reach out to those who submitted the form at some point in July, so look for an email from us then!
As a note: This API will be available to Pro+ subscriptions across all Hubs (Service, Marketing, Sales, CMS).
Please let me know if there are any other questions!
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.
I think so too, this is a bug fix, why do I need a Pro subscription
The API to identify a visitor already exists (Accounts Dashboard | HubSpot), but it dont work as expected with chat.
I’m not sure to understand why this bug will be fixed only for Pro+ subcriptions.
My company is testing out Hubspot. We want to use live chat in our company intranet. This would be a valuable feature for us!
I don’t think we have the Pro+ plan.
Is there any progress?
When will it be released?
@tilly July is almost over, do you have any updates here? We submitted the form long time ago but have not heard back from you yet. Thanks
@vruben -- Thank you for checking in! Hoping to have an update for you all very soon. Keep an eye out for a product notification, and I will make sure to post a note here as well.
If it’s possible to answer, are we talking days or weeks? We migrated to hubspot thinking the chat would be a great replacement of Intercom and are now regretting that. Chats are coming in from people without proper labeling, as you know. And every day we dont have this, it causes issues.
So if its days, I’ll gladly wait. If it’s weeks, then ill need to switch for the time being.
Thanks
Shouldn’t the “Identify” method just update both cookies and identify the user across all services? As a dev you would expect to call “Identify” and for hubspot to stitch all the data associated with that session to the user in question, rather than having to do one thing for analytics and one thing for the chat.
This request has been pending for 2 years and still no solution. This platform is almost useless to request anything.
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 new Visitor Identification API enables 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.
Good Morning,
just tried it without an app, but API/Token only. Got error complaining about missing scopes:
{"status":"error","message":"This app hasn't been granted all required scopes to make this call. Read more about required scopes here: https://developers.hubspot.com/scopes.","correlationId":".....","errors":[{"message":"All of the following scopes are required.","context":{"requiredScopes":["conversations.visitor_identification.tokens.create"]}}],"links":{"scopes":"https://developers.hubspot.com/scopes"},"category":"MISSING_SCOPES"}
linking to dead url:
Pls. advice
Hi, @patroqueeet.
I’ll look into this. Could you share your app ID and the scopes you are currently requiring?
I’ve learned that @tilly helped you uncover the issue directly.
Here are links to the most updated OAuth documentation (mentions scopes) and the older but still relevant scopes documentation.
For others reading this, make sure to add the conversations.visitor_identification.tokens.create scope in your app definition’s Auth tab, as shown below:
It seems the visitor identification API does only create a contact, when the customer sends a chat message. Is this the intended behaviour?
We’re sending email, firstName, lastName to get a token. Contacts should be created then if not stored at HS.
Hi @cl77 -- That is correct, the Visitor Identification API only creates a contact if and when they initiate a chat.
To make sure I understand your use case and needs, what is your expectation for this API? How are you currently using it? Thanks!
Hello Hubspot team,
The whole visitor identification doesn’t work whenever the chat is loaded on the knowledge base. Because the knowledge base is opened from our mobile app, even though we know the email the chat is not able to identify the visitor.
Please let us know the solution for this.
NOTE: This must be happening because on the knowledge base loaded by Hubspot instantly loads up the chat.