Roadmap
Changelog

Have something to say?

Tell user.com how they could make the product more useful to you.

Product Segments - Add API for operations

Jest potrzeba żeby móc wykluczać lub dodawać produkty do segmentów w celu uwzględniania ich faktycznej dostępności. Obecnie przeliczenie segmentu powoduje to że produkt którego już nie ma w sklepie dalej może zostać rekomendowany.Mogłoby to działać podobnie jak działają moduły Add/Remove user from segment w automatyzacjach, tylko jako requesty API uwzgędniające ID produktu.Tą potrzebę zgłasza g.wagner@superauto.pl

Maciej Rządkowski 4 months ago

🧩 Feature Request

Emails are forceed to lower case, but search is case sensitive

All emails stored in user.com are forcibly converted to lower case (which I don't agree with, but fine). However, the API email search is case-sensitive, meaning you cannot use the email the customer entered, without first converting it to lower case.Suggested change:According to best practices you should store emails as customer entered it, but all searches should be case-INsensitive.If this is not possible: Make email search in the API case insensitive, possibly with a optional boolean flag if you feel this might break things.

Sire 5 months ago

⚙️ Logic Change

Possibility to reorganise (sort) attributes

Possibility to reorganize (manually sort) people, company, and deal attributes. Now, they are in the order you have created them, but in reality, it's random without logic. It is even better if you could organize all attributes (custom & default), but MVP-level is the possibility to organize custom attributes.

Paulus Perkkiö 5 months ago

🧩 Feature Request

Detecting existing emails when importing

Can you please create some kind of warning or notice that email addresses already exists within our database if the email imported already exist? Like an additional column - duplicate emails or something. This will significantly make importing easier, as it does not require deduplication automations etc etc. Just a plain warning that an email already exists and the choice if you want to continue importing the duplicate emails or import everything else just not the duplicate emails.

Tamara Jelic 6 months ago

🧩 Feature Request

error reporting email metrics within campaigns

Problem campaign metrics reported within campaigns, namely open and click rates can be inflated due to the well known issue of bots, apple privacy, email security software etcthe issueAs emails are often opened and clicked - not by the member but by applications and tools the metrics reported can be considerably higher than they should be.Possible solutionwe are aware of the difficulty and complexity of working with email sending but we have seen that other platforms have created features to try and distinguish clicks and open rates which are outside of a normal pattern for email delivery, example being - https://community.hubspot.com/t5/Email-Marketing-Tool/Are-Bots-Affecting-Your-Email/m-p/310626/page/3this thread details the issue we have and some steps that hubspot have made to help reduce these inflated numbers from being added to the final metricsthe solution mentions "The new tools take a behavioral-based approach. We look for patterns in the open or click events that indicate a likelihood of being generated from a bot.  " and this is something that could be put in place, probably at the SMTP level, rather than the user.com app level heres some info that another SMTP delivery platform is taking to address this https://www.mailgun.com/blog/product/bot-detection/,other exampleshttps://experienceleague.adobe.com/docs/marketo/using/product-docs/administration/email-setup/filtering-email-bot-activity.html?lang=enhttps://experienceleague.adobe.com/docs/marketo/using/product-docs/administration/email-setup/filtering-email-bot-activity.html?lang=enhttps://sponge.io/6-ways-sponge-recommends-handling-bot-clicks-marketo/#:~:text=Remove%20Bot%20Click%20Link%20Scoring,improve%20your%20email%20metric%20reporting.From researching their does seem to be a number of possible solutions to identify bot like activity with email campaigns sentthis could be a setting that can be turned on/off within the app - if turned on the campaign could show both values of clicks and opensOpened; 98 (with bot guard 56)We believe this could be a good feature request - many other providers have addressed this issue, looking at the forum on hubspot it was a big issue for clients, and these stats are such an important metric to determine the success of the campaign and the strategy of email marketing in general a user.com specific update to also help address this issue could be the placement of a hidden link contained within the DEMs sent from user.com, (not added in the template, but sent in the email) if this link is clicked it is likely a bot, so could also be used to help with analysis of possible bots

Nick Wale 7 months ago

🧩 Feature Request

Ability to change the name and category of an email campaign

Our company urgently requires this feature as we have numerous email campaigns that need to be renamed and re-categorized. Presently, we are unable to modify either the name or the category. Due to this limitation, our email campaigns section appears disorganized, making it extremely difficult to work with.

Vlad Turak 7 months ago

1

🧩 Feature Request

Color of pipeline steps

It would be nice to have the ability to add different colors to the pipeline stages. For my main pipeline, my first stage would be grey, the second would be yellow, third red, fourth to seventh blue, and eight would be green. If a deal is in a stage or has already passed it, the color is full; otherwise it's muted by 50%.

Vatroslav Mileusnić 9 months ago

🧩 Feature Request

Need to have "in x minutes/hours" filter for on date and time

Need to have "in x minutes/hours" filter for on date and time This is a lacking condition for your On date and time.This will ensure sending campaigns/emails when its X minutes before a Date/time Value.You only have X mins have passed and less than X mins.But no option for "In X mins" meaning it will trigger if date /time event is x minutes from now.

dinodinz 10 months ago

🧩 Feature Request

Completed

New operators for attributes in product snippet tag

Description Currently, in the attributes parameter in the product snippet tag, we can only use the = operator, which works asequal signORin (in case of checking whether a given value is in the data list as a product attribute of the multiple fixed choice type)There is a need to add further operators to the above parameter:><>=<=!= (analogously to =, the != operator would also check if the value is not in the list given as multi fixed choice or the value of one of the keys in the json type attribute)What's more, the = and != operators would work not only for fixed_choice type attributes, but also for json type (in the same way as for fixed_choice type).For example, for a json attribute named json_attr and the value {"list": ["A", "B", "C"]} checking if the value is in the list list:{% products count=5 attributes='json_attr.list=B' order_by='updated_at' order=-1 as product_list %}

Grzegorz Kacperski 10 months ago

🧩 Feature Request

Completed

Snippet tag for filtering by multiple segments in Product/Product Event Snippet Tag

Description Currently, it is not possible to add more than one snippet for the segment parameter in the Product/Product Event Snippet Tag.Customers ProblemProduct categories have multiple subcategories. A one-time creation of segments that meet the condition of belonging to a given subcategory, combined with the ability to filter products in the snippet by many segments, would allow returning the right products.To-doAdding a snippet that allows you to create a text string based on the given values (text strings or references to the user's attribute values or objects assigned to it)Example{% join_attrs 'attr1' receiver.company.country 'attr3' as multiple_attrs %}will return e.g. attr1_value|USA|attr2_valuein turn, the same attributes in the same snippet, but with the sep parameter equal to e.g. ";" :{% join_attrs 'attr1' receiver.company.country 'attr3' sep=';' as multiple_attrs %}will return attr1_value;Poland;attr2_valueAdd sep parameter, which is not required, thanks to which it would be possible to select a separator separating the above values(default value | )for the join_attrs tag snippet abovefor a product snippet tagfor product event snippet tagExtending the segment parameter with the possibility of accepting many values given as a text string separated by a default separator.Multiple values for the segment parameter would be possible only when the sep parameter was specified in the snippet (otherwise the parameter value would be assumed as the name of one segment).The change would apply:product snippet tagproduct event snippet tag

Grzegorz Kacperski 10 months ago

🧩 Feature Request