...
| Info |
|---|
This release deployed on August 9, 2024 at 3pm ET |
Notable Updates
Have you heard about Segments? There is some exciting news coming - look out! 👀https://www.youtube.com/watch?v=f8pofEQpmeY
Notable Updates
Get excited - Segments is arriving in your Engaging Networks account at the end of the month! Want to learn more? We have a brand new course in the Academy for you to take that will give you an overview of the functionality and how to use your segments with the Marketing Tools. We also have documentation in the Supportal to help familiarize you with how Segments works. We hope you are looking forward to checking it out in a few weeks!
Improvements
Gateways
WorldPay: We have migrated from “Pay as Order” to a tokenization solution due to the decommissioning of “Pay as Order” coming in October 2024. Only WorldPay (not Vantiv) clients who are processing recurring payments and/or using the “one click” functionality must contact WorldPay to enable tokenization in their accounts. Once this happens, they must inform Engaging Networks to turn on this new solution, as otherwise, transactions will start failing in October 2024.
Deleting a gateway: clients can now delete a gateway even if there are live pages, recurring schedules, or events dependent on it. Those pages and recurring gifts will not be affected.
Moneris: we are now passing these additional fields when processing a transaction: cardholder email and browser IP.
...
When inserting page links, additional options will be available to add the NSG value into the link text if the selected page has NSG configured.
To learn more, check out a brand new course in our Academy on Next Suggested Gift.Please note: you
| Info |
|---|
You are only able to insert a NSG value once in a single email broadcast (including either the value on its own or within the link). Any additional inserted values will not work properly. |
Bug Fixes
Data Import
Importing supporter data without Send Offset was clearing out any values stored for that supporter in the Send Offset fields. This has been fixed.
...