I'm looking for ideas on how to block bad actors or spam chatters in web messenger. Previously in web chat, I've set a cookie with a UUID and then retrieved that UUID for use in a block list.
I'm curious if there's an easier or baked-in way to achieve blocking with web messenger as we get ready to move to it.
Within your Inbound Message Flow you could achieve something similar by using Architect built-in variableMessage.JourneyContext.customer.id which contains the user identifier (aka cookie-id, same is stored in External Contact record): if you can store these variables in your own database, you could use it for lookup of blacklisted cookie-IDs. You could consider using our native Data Tables as well, but keep in mind these have Limits to be aware of, and you would actually be storing PII, which implies some level of manual purging for compliance and privacy regulations.
In future we would evaluate how to productize this, and move the function at Contact level, so that it may apply across all user's identifiers.