109 results found
-
"Before" or "After" operator with a relative date (today)
I want to create a segment with the "Before" or "After" operator, but with a relative date instead of a fixed date as available currently. The other option "Is in the past" or "Is in the next" doesn't work for me as the date can be before or after 365 days which is the current limit.
1 vote -
Contacts Rating
Providing a rating for contacts based on their activity, i.e. Opening and Clicking of emails.
2 votes -
Facebook Page Integration
It would be great to have a Facebook integration so that we can add a signup form directly into our Facebook page.
1 vote -
GDPR module directly available on the UI
To have a tab/module directly available on the ui in order to make easier for a client to respect the right of oblivion of recipients (GDPR right) by deleting information regarding a contacts without having to do it subaccounts per subbacounts by deleting the contacts or doing it through API or through a request via LVL2.
The idea is to create special right for a shared access who will be able to manage it easily.
1 vote -
Add Last activity when exporting contacts from All contacts
When exporting contacts from All contacts should be good to include Last activity of each user instead of need to download each contact list to extract this data.
1 vote -
Let recipients edit their contact properties
Allow recipients to edit the contact properties stored in Mailjet.
2 votes -
Search a user in the Shared Access Section by email address
Ability to search for a shared access user by email address
2 votes -
segment creation - UI improvement
improve UI flow for naming a segment
current behavior
-user clicks "Create segment" at bottom right without titling segment
-application prompts user to give the segment a title
-user enters a title but does not click "Save"
-user clicks "Create segment"
-nothing happensInstead of nothing happening, segment should be created with the name that has been input (just without clicking Save)
0 votes -
Filtres "N'est pas" et "Ne contient pas"
Les recherches de type "n'est pas" ou "ne contient pas" devraient systématiquement remonter les contacts pour lesquels la propriété est vide ou n'existe pas.
Pour ces contacts-là :
- la valeur ne sera jamais la valeur renseignée avec le filtre "n'est pas"
- la valeur ne contiendra jamais la valeur renseignée avec le filtre "ne contient pas"Is not" and "Does not contain" filters
Searches of the "is not" or "does not contain" type should systematically return contacts for which the property is empty or does not exist.For these contacts :
the value will never be the value entered…
0 votes
- Don't see your idea?