Webchat: secure user identification (HMAC signature)
Recognize your signed-in customers: your server signs their ID and the widget links the conversation to their record.
Watch this step in the video · Secure user identification
In Embed Code → User identification is the channel's secret key (Show, Copy, Regenerate).
- On your server, compute
user_hash = HMAC-SHA256(user_id, secret_key)in hexadecimal. The tab includes the example in PHP, Node.js and Python. Never put the key in the browser. - On the page, call
Omnifox.identify({ user_id, user_hash, email, name, phone, attributes }). - The conversation is filed under that customer, linked to their record (by their
user_id), even if they write from another device.
If you call the API before the widget loads, use the command queue shown in the tab. When signing out of your site, call Omnifox.logout(). Regenerate key instantly invalidates all previous signatures.
Related articles
-
WhatsApp (Meta) error codes: what they mean and what to do
A table of the most common Meta error codes when sending on WhatsApp (131026, 131047, 131049, 130497, 141006, 131031, 131056, 132000, 190, 368…) and how to fix each one.
-
How to connect Telegram
Connect a Telegram bot to your Omnifox inbox in minutes using BotFather.
-
Instagram and Facebook comments: reply and moderate from Omnifox
See and answer comments on your Facebook and Instagram posts and ads, publicly or privately, and set up automatic replies.
-
Sending and receiving videos on each channel: formats and size limits
Which videos you can send and receive on WhatsApp, Instagram, Messenger, Telegram, web chat and email, the real size limits, and what to do with a large video.
-
Move from WhatsApp QR to Coexistence or Cloud API
Once you're done testing with the QR code, move your number to the official connection: no caps, with templates and broadcasts, and no volume-based ban risk.