Thanks for the reply Sahil, yes I believe so. It's implemented as suggested by the chatbot:

private func generateHMAC(data: String, secret: String) -> String {
    let secretData = Data(secret.utf8)
    let dataToHash = Data(data.utf8)
    
    let signature = HMAC<SHA256>.authenticationCode(for: dataToHash, using: SymmetricKey(data: secretData))
    
    return Data(signature).map { String(format: "%02hhx", $0) }.joined()
}

Do you see any issues here?

It also doesn't work if I send only email, which is the only required parameter according to docs (email OR phone). Chat works, but email is not attached.

hello @Ivan This is the documentation for the identity verification process: https://docs.yourgpt.ai/chatbot/customization/sdk/identity-verification/

Have you tried using the $yourgptChatbot method? I’m checking your use case by passing it in the URL to see if verification can be done that way. I’ll update you meanwhile — if you can try using the YourGPT method and see if that works.

Thanks @Sahil !

In case it's not clear, I'm using the webview approach on iOS client, without SDK. Should it be possible to pass in this info through URL query on iOS?

Yes, through the URL — I’m checking if that’s supported from the widget. If not, I’ll update my team to see if we can add support for it via the URL as well.

Please let me know if you find out. WebView implementation is very fast and straightforward so it would be great if it works.

hello @Ivan We’ve added hash support in the URL. Please check now — if the hash validates as true and is generated according to the documentation we shared, it should correctly store the email as a contact in the system

Sample: https://widget.yourgpt.ai/<widget_uid>?CONTACT.email=<[email protected]>&CONTACT.ext_user_id=<user_id>&CONTACT.name=<user_name>&user_hash=<hmac_hash>

Hey Sahil,

unfortunately, it still doesn't work with me.

It would be enough for us if only email was logged.

But if hash is always required, how can I validate that it's correct?

You can debug by filtering the logs based on my test email: [email protected]

@Rohit Joshi - could you also check please.

hello @Ivan If you prefer to skip the verification step, you can simply use the following URL: https://widget.yourgpt.ai/<project_uid>?CONTACT.email=<email>

This will automatically log the email on the conversation page and add the user to your contacts list.

Unfortunately, it still doesn't work if I try with email only. So it's not the hash issue at all, but user data doesn't get logged.

Can I do something on my side to help with debugging? Should I see the email in the logs? Because it's not there right now.

Can you share your widget link? I’ll try it with an email attached and you can check if it appears in your dashboard.

I’m seeing some contacts being registered in Dashboard > Project > Contacts that include external_ids and session info. Can you confirm whether you’re able to verify those contacts? Also — if you’re testing with test emails, note that our system does not allow test emails to bypass the valid-email checks. Allowing test emails or duplicate addresses makes the leads data unreliable. Please test using real email addresses that do not already exist in the system.

emails that you see are coming through web client, not iOS. I just tried with a valid email, the issue persists and it's not logged.

Are you testing it using the widget URL in the browser?

I tried that too.

I tested your bot with one conversation. Could you check if this email was registered in your dashboard?

thanks for that, it works. I believe I know what the issue is. Your system doesn't allow so called plus addressing in emails. Is that intentional? I believe it shouldn't dismiss all emails with + suffix because users might actually use these emails to log in

Yes, we’re aware of this. Our verification provider currently doesn’t support “+” emails, but we’re working on enabling them soon.

alright, this was the issue from the very start. thanks for the help, should be ok now