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!
96 results found
-
Add Pretext in Visual Builder
Add a option to add pretext in the visual builder
1 vote -
"Remove All" Option for Complaints and Unsubscribes
Currently our UI gives a "Remove All" option for Bounces only, and is not present for Complaints and Unsubscribes. Some customers would like to have this option for Complaints and Unsubscribes
1 vote -
Suppressions search
We often need to search for a suppressed email in all sub-domains. As far as I understand, currently the search works only for a specific sub-domain. We have to check that for each sub-domain separately. Can you make an option which checks all domains by default in "Suppressions".
1 vote -
Allow link tracking on URLs longer than 1000 characters
Please add support for click tracking on URLs longer than 1000 characters. As far as I can see this limitation on link-rewriting is not documented. Our SSO solution generates links in the 1000 - 1300 char range that contain a base64 encoded JWT. All browsers support at least 2048 characters so it would be obvious to allow as least as many characters for the rewrites.
/David
3 votes -
Share templates between domains
I would like to ask, whether it is possible (or at least you plan it in the future) to share mailgun templates between domains?
We would love to have 2 separate domains for production and testing purposes, but share templates, se we do not have to duplicate them and keep different ids depending on environment from which we are sending.72 votes -
Search in Templates Listing
There should be at least search for templates.
21 votes -
Search suppressions list by email domain
PLEASE allow us to search the suppressions list by email domain, not just specific email. Our use of the product means that we often have multiple users from a single domain that we send email to. If something goes wrong with their email server, and they end up suppressed, removing them is a real pain. The customer has to provide us with every possible email that was suppressed, and we have to search them all one by one. I REALLY wish I could just search by domain instead.
18 votes -
Add support for macros in DNS SPF records
Currently, DNS SPF records using macros will not be automatically approved by mailgun. Some mail services (like valimail.com) use macros to avoid the SPF character limit.
Example:
v=spf1 include:mydomain.com.nspf.vali.email include:%{i}.ip.%{h}.ehlo.%{d}.spf.vali.email ~all9 votes -
Per-link analytics for click tracking
Being able to track opens and clicks and consume that data via the Analytics dashboard is awesome. However, most emails that we send out contain multiple links - e.g. for account activation, homepage, featured blog post, social links, etc.
I would like to be able to have analytics on a per-link basis. Mailchimp allows this, see https://i.imgur.com/2iIocrv.png.
61 votes -
Manage multiple accounts with the same email
There is a way to create multiple logins for the same Mailgun account but we can't reuse an existing account. The error message is:
Error: Unable to invite user. User already exists
We need a way to manage multiple accounts under the same email, not having this is a total nightmare :\ We have this in Stripe, Twilio, SendGrid, Mailchimp, etc ...
There is no way I will ask my clients to forward me the "passcode" everytime I need to login on my client's account.
116 votes -
Analytics by SMTP user
It would be great to filter analytics by SMTP user!
16 votesThis ask might be better satisfied through use of our tagging feature so you can arbitrarily mark-up your message with a value specific to that SMTP user. You could then easily filter data in our new reporting specific to that tag.
-
Invite new users/roles to specific domain(s)
Recently you introduced invitation of new users and assigning them roles.
In addition to "roles" i would like to see that these invitations/roles can also be limited to specific domains.135 votes -
Support Non-credit card payment types
Allow customers to pay via alternative payment types other than credit card.
100 votes -
Add support for idempotent requests to the API
Add Idempotency-Key to request ala Stripe's API. https://stripe.com/docs/api?lang=curl#idempotent_requests
41 votes -
Alert and Notify based on Sending Metrics and Usage
There are some delivery issues which usually warrant manual inspection and care by the administrative users. I feel that continuing to send emails to addresses that have ended up in the Bounces list would at least be one of them.
It would be convenient if the user could select certain common delivery issues like this and get a notification about them emailed to a specified email address. This email address could then be a mailing list for administrative personel who could look in to the error and see it they should act upon it.
It is possible to implement this…
35 votesHello,
As we work through ideation on an alerts feature for Mailgun, I wanted to gauge opinion on the configuration of notification channels. If out of the box, Mailgun allows for configuration of notification channels to include emails addresses, webhooks, and Slack integration where in the flow does it make most sense where the channels are defined.
Our position is that the pattern for notification channels is created on the account level. Such that any all alerts created would use the notification channels previously defined. This would be foundational to a future state is which users could have greater control on how Mailgun communicates emergent issues (e.g. some users would like to receive domain disablement or similar notification posted to webhook rather than email).
So, for "alert and notify based on sending metrics and usage" is there any reason Mailgun needs to have notification channels defined on a per alert…
-
Shorten Tracking URLs
The current URLs used for tracking link clicks are quite long. Offering a way to shorten them via Bit.ly or perhaps an custom shortened URL would be helpful.
14 votes
- Don't see your idea?