Submit your Product Ideas to the Click Product Management Team below.
These will be reviewed for consideration in a future product release. It is not intended to provide Product Support. If you are having a product issue, please follow regular support procedures.
Thank you for taking the time to submit your thoughts!
Ensuring that our products address the needs of our customers is important to Click. By providing your input, you're helping us ensure that our products are built by Marketers, for Marketers.
Information about the Product Ideas portal can be found in this support article.
To submit ideas related to Click Intelligent Dashboards please go to this link.
We have come across scenarios where bots/hackers are submitting ClickD iFrame embedded forms on our website with injected HTML and/or SQL into our "Comments" (text-area) fields. These submissions eventually come into CRM and our database. Luckily, CRM's rendering of text fields like the posted fields with injected code is only presented as plain text in a web browser. However, having this injected code in our database is still a security concern. I would think the same is true for ClickDimension's Azure servers on their end as well.
I am aware of the "Filters" functionality and have set them up to block further submissions from these known IP Addresses as a reactionary measure. But I would like to invoke ClickDimensions on building out a more proactive process to prevent these security threats at the source of the form itself.
These added security measures could be an enhancement on the existing "Filter" entity, instead of only allow users to block an IP Address or a Domain. Expand the functionality set up "filters" on blocking any injected code and/or spam keywords defined by the user.