Closed ber8749 closed 1 year ago
Hi, we don't include the user info details in the webhook payload - as the user_info is generated and owned by your systems we only provide the user_id. With this you can then conduct any lookups or enrichment of the event with the info you hold about the user. This also keeps the payload size to a minimum. At this time we don't have any plans to add user_info to the presence event webhooks.
The documentation for presence channels shows that
user_info
can be passed into thePusher#authentication
function. I would expect that the correspondingmember_added
ormember_removed
webhook event would contain that sameuser_info
, but in my testing so far that has not been the case. Instead, the presence events look something like this:Am I missing something, or has this information been stripped from the event for some reason?