Feature Requests
If you’ve got a feature request, you’ve come to the right place! Please relay your request request here, along with any additional details you think might be helpful.
This is not the spot for feedback on current features, only new plausible ideas will be considered. Please be courteous of others and upvote if you believe strongly enough in an idea!
232 results found
-
Option to Duplicate Template in MG Drag and Drop Template Builder
Currently our DnD template builder has a duplicate option, but this only applies to the template version. Some users would prefer the option to make a duplicate which is a completely new template, and not just a new version within the same template
26 votes -
5 votes
-
Have the ability to turn off SMTP sending for the domain if only API is being used.
If we are not utilizing SMTP but only API we want the ability to turn off SMTP so that the server settings can't be used.
3 votes -
Webhook security
Webhook security
I am concerned about the security risks involved in using your service. I would appreciate it if you could consider implementing some of the following suggestions:
- Use a more specific user agent than "go-http-client" to identify your requests.
- Provide a list of verified IP addresses that you use to send webhooks, so that I can restrict access to my server with a firewall.
- Use a dedicated IP address or a domain name to send webhooks, instead of a shared one.
- Then you might even verify yourself to cloudflare (to be recognized as known bot)
These measures would greatly…
2 votes -
2 votes
-
Comments to SMTP credentials
It would be nice that we could add some comments to accounts at SMTP credentials. Now we have a list of accounts that was created years ago and I'm not sure where they are used. In this case if there are would any comment section I could enter that this account is used in CRM and this in website as example.
3 votes -
More than 3 URLs per Webhook event
Customer would like the ability to have more than 3 URLs per event type for webhooks
2 votes -
Please bring back short usernames -- why minimum character requirement?
In the past we could have short usernames, but could not manually set passwords (causing issues with printers etc). Now we can manually set passwords (huzzah!), but now usernames are required to be 5 characters long. Why is this?
I use initialisms or initials, so I have a bunch of old legacy two-letter usernames, but can not create new accounts with two letters. This inconsistency is causing issues with code that relies on standard naming conventions, and I am having to hard code around the issue, which is a terrible thing to do.
2 votes -
2 votes
-
Email Admins when new SMTP or API credentials are created
This is a fraud prevention action. We had multiple SMTP credentials created then fraudulently used. If we got emails whenever they are created we would know they weren't done by us true admins.
2 votes -
Provide admins to view all subaccounts
Currently there is no option for admins to view subaccount information
3 votes -
update template portion in documentation
It needs to use 't:version': to reference the version. I found this on another website but it would be helpful to have this added to the main docs page
2 votes -
HTML an Visual builder switch
As a developer. I want to convert between Visual builder and HTML builder when create an email template.
5 votes -
1 vote
-
Confusion Around Error "Destination must be publicly accessible" When Adding Route
When adding a URL for a route, if the URL is not publicly accessible we will return an error of "Failed to create route". When looking in the dev console, only then do we see that the error is related to the URL not being publicly accessible. This can be confusing to users as they are not given the error directly
1 vote -
1 vote
-
Log Retention Period Longer Than 30 Days
Currently our log retention period has a maximum of 30 days. Having a longer message retention is something that many customers would benefit from
2 votes -
Some feedback after almost a year of use
Changing the date in the analytics view doesn't update the metric numbers in the tag breakdown.
In the analytics view, three metrics are highlighted at the top: delivered, open, clicks. These should be unique opens and unique clicks. The total number of opens is essentially always irrelevant.
In the engagement view for a specific tag, you can't see the number of delivered emails. The absence of this metric makes the tool difficult to use.
In the reporting section, the line chart displays the open rate but not the unique open rate. This is ineffective because some people open the same…
1 vote -
Add support for UTF-8 characters in domain names
Allow domains with non-ASCII characters, as many mailbox providers are nowadays supporting them. Alternatively, add full support for IDNs, which is currently partially functional (for example, domain validation works, SMTP credentials creation doesn't work).
1 vote -
Ideas for improving Api / Quicklook / overall experience
Hi, I have a few ideas for improvement. For batch sending emails via API, please add a safe mode, where the request is rejected, if not every recipient address has a matching entry in recipient-variables. I just happened to send out a bunch of emails that would only show the %recipient.name% placeholder, because of an unintended whitespace in the "name " field of the recipient-variables. This is a very sad experience and could easily be prevent with better tooling.
But even better: Just take the recipient name from the recipient email address: -F to='Recipient Name recipient@email.com' Why do I…
1 vote
- Don't see your idea?