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!
105 results found
-
Sending DNS record instructions via email with one click.
I should be able to send someone the DNS records via email so they can connec it to their hosting.
5 votes -
Upload Images for Use in MG Drag and Drop Template Builder
Currently the Mailgun drag and drop template builder only allows for images to be provided via URL. It would be helpful to also have the option to upload an actual image file to Mailgun.
21 votes -
API access audit logs
API Access Audit Logs
Please provide audit logging for any and all API calls. Results should include
- Date/time
- Source IP
- API called
- Account used
- Query header
- Authentication Success/Failure12 votes -
Allow setting the open, click, and unsubscribe settings when creating a domain
Currently when creating a new domain via the API, we have to set the open, click, and unsubscribe tracking settings via individual PUTs. Instead, we should be able to create and configure a domain in a single call - that way we don't have to worry about a domain being partially setup.
2 votes -
Sort order SMTP login
Hello,
It would be great if SMTP Credentials could be sorted on Login (ascending or descending).
Best regards,
Simon1 vote -
Support UTM Parameters and Google Analytics Integration
Support UTM Parameters and Google Analytics Integration.
Other competitors offer this or integration with solutions.
3 votes -
Allow specifying the DKIM selector during domain creation via the API.
Currently when creating a new domain via your API, you have to post a second request to set the DKIM selector. I think it would make more sense to allow us to specify the DKIM selector (along with anything else) in a single request - that way we don't have to worry about the possibility of a domain being partially setup (e.g. the create domain being successful but setting the DKIM name as unsuccessful).
1 vote -
Allow Route Filter on Email Body
Currently our routes only support filtering for the message header, and not the body. Being able to filter by specific body content would be helpful.
4 votes -
Request for method to programatically pull security event logs
Requesting to have an api endpoint or programmatic way of pulling security event logs (e.g. a org user logs in, if there was a failed login, activity of users etc) so they can be ported over into a SIEM.
2 votes -
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.74 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.
62 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.
117 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.
- Don't see your idea?