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!
-
Add the event's timestamp in addition to the webhook timestamp
The time of the event is important to us and if the event time is only available from the Event API, then we will have to make additional calls to the Event API for EVERY single notification(delivered, failed, open, click etc), which may add significant load to our (and probably yours) server and network.
2 votes -
Add segmenting options to the list sending API to make it easier to send to a portion of the list
Add some options to segment list sending, or create temporary lists based on number of list members.
4 votes -
Add a throttling to allow for list sending to be sent over longer time period
When sending out to a large list, a user may sometimes wish to throttle the sends over a time period to avoid having too many responses or heavy web traffic all hitting at once.
4 votes -
Do not send duplicate email to same recipient in different list
Recipient in different list would receive only one copy of message, this is a basic ESP feature that everyone supports. But currently if a address is on more than one list than recipient will receive messages that are sent to each list, the only way to avoid this is to remove the email from other list.
Please add a workaround for this basic ESP feature.
5 votes -
HTML mailing list variables
Have the ability to put HTML into the mailing list template variables.
e.g.
{
html : "<strong>bold text</strong>"
}<html>
<body>
%recipient.html%
</body>
</html>Gets transformed into:
<html>
<body>
<strong>bold text</strong>
</body>
</html>2 votes -
Add "block" as a third option in spam_action with the Domains API.
Add "block" as a third option in spam_action with the Domains API.
3 votes -
Messages can be scheduled for a maximum of 7 days in the future.
Messages can be scheduled for a maximum of 7 days in the future instead of 3.
If it's due to spam perhaps you can get people to verify their bank account etc.
The reason why this would be good is because i plan my release of products every weekend. The items will be released daily and so can my email be sent daily automatically. Well i mean it's easier for me.
Thanks :)
7 votes -
Add total hourly, daily tracking for email sends
Add the ability to track email sends (hourly) in the dashboard so they can be compared directly against opens. This would greatly improve the ability to assess best send times that garner the highest open/click rates for recipients by drilling down into open rate by the hour the email was sent.
3 votes -
Add a feature of Disable / Enable link tracking by parameter
my idea is the you shoukd add a support for Disabling /Enabling link tracking by adding a parameter infront fo the link.
the reason is thet somtimes like in "Please Remove Me..." the email address in the links is differenf for eache mail and therefor this is a uniq link. this info is not very useful when tracking a campagin.2 votes -
Specify Outbound IP on Submit
Would be great to define the outbound IP address (of those in my pool), for which emails will deliver, upon submitting to the API.
5 votes -
Mailing list join date
Show the date an email address has been added to a mailing list.
2 votes -
Provide a "Spam Probability" API
There should be an endpoint where you can submit the MIME of a message and get a spam probability score to determine deliverability.
4 votes -
Add a customizable footer to mails that are sent to mailing lists
I'd like some basic footer information included on every email that gets sent to a mailing list. Eg something like:
Thanks for using somethingsomething, visit us here <link>
Or call us anytime on <number>It would be great to just use the current Templating functionality to attach a Footer Template.
1 vote -
mailing list template variables; custom message data
Make the mailing list recipient variables available within the sendMessage call so that when sending to a list, dynamic recipient data can be set within the message v:my-custom-data.
So when you create a user within a mailing list you can set custom recipient variables via 'vars' on the create and update mailing list recipient call.
But when you then send a message to the pseudo email address, you cannot tag that message with the dynamic recipient variables within the v:my-custom-data string on the sendMessage call.
If you could access the recipient.vars within the sendMessage call, then you could tag individual…
0 votes
- Don't see your idea?