Philip
My feedback
2 results found
-
17 votesPhilip
supported this idea
·
An error occurred while saving the comment -
320 votesPhilip
supported this idea
·
Yeah +1 on this. Similar to:
https://autopilothq.uservoice.com/forums/284270-autopilot-feedback-forum/suggestions/17458465-allow-using-event-variables-in-transactional-email
https://autopilothq.uservoice.com/forums/284270-autopilot-feedback-forum/suggestions/10126569-allow-dynamic-content-be-inserted-for-each-user-fr
https://autopilothq.uservoice.com/forums/284270-autopilot-feedback-forum/suggestions/17458465-allow-using-event-variables-in-transactional-email
At minimum, we should be able to dynamically generate and send the raw HTML to an API endpoint that takes the contact id, journey id, and Autopilot wrap / track the links like traditional transactional email services like Mandrill, Sendgrid, etc.
Today, there is no way to send any meaningful dynamic emails which is honestly something I just assumed that was offered as that's kind of table stakes.
- Newsletters
- Daily/Weekly Digests
- Receipts
- Cart abandonments
- List goes on
Iterable offers a feature where you surface an api endpoint on your server that spits out json which they use to parse and populate the emails which is really nice as it's up to date whenever the person opens it, but I'd settle for being able to send json / html / handlebar variables with the payload.
Will likely have to switch providers soon due to this fact, which makes me sad because I really like other aspects of the product ; (