In order to back-populate origin source data for existing records in both of our data centres, there will be a brief outage of a few minutes between 9pm and 10pm EDT, Friday 22nd June (6pm and 7pm PT, Friday 22nd June, 2am and 3am BST, Saturday 23rd June).
We do not expect this update to take more than five minutes. There will be no impact to any scheduled jobs during this downtime but pages and email links will be inaccessible during this five minute outage.
If you have questions about any of the upcoming functionality, contact client support.
The ability to create or duplicate legacy pages has been removed from the software. All pages should be created in the page-builder tools from now on.
You can continue to edit legacy pages in the software until 31st December 2018. However, if you want legacy page URLs to redirect to a new page after 31st December 2018, you will need to put a redirect in place. This can be done easily by changing the status of a legacy page to ‘closed’ and entering a redirect URL to a new page created in page-builder. If you do not have a redirect in place for a legacy page by 31st December, the page will fail, starting on 1st January 2019.
A supporter’s Origin Source (how they came to be in your database) can now be set in Engaging Networks.
Origin Sources help identify how different channels compare on performance. With this release, origin sources can be specified via import, set on a page's 'admin settings' layer and/or passed through the URL parameter ‘en_og_source’. This field is located on the Supporter Record and is an uneditable field.
As a supporter's 'origin source' can only be set once, these values would only be written if no origin source is set currently on their record.
To aid in managing Origin Source we have added the following to the software:
An ‘Origin Source’ category in the Activity Summary gadget, found under ‘Lookup Supporters
‘Origin Source’ on the Components menu, to help manage Origin Sources
Two new fields which are available when importing: ‘Origin Source’ and ‘Origin Source Category’
Super Administrators (SA) may now enable ‘2FA’ on all account users or on a per individual account user basis. This tool leverages the Google Authenticator app, which can be downloaded from the Google Play or Apple App store. Upon enabling and on the account user’s first login to the Google Authenticator app, the user will be required to scan a barcode, which will link the Google Authenticator app to their user account. Thereafter, if a new device is seen logging in with the user credentials - the account user will be required to enter the 6 digit code which the Google Authenticator app generates.
Note: We recommend testing this thoroughly before enabling to ensure you are happy with the experience.
This new gateway supports both single and recurring donations processing, through credit cards. It is fully integrated meaning you can manage refunds and update credit card information from the Lookup Supporters module or using the HUB.
Once householding is enabled (under account preferences), account users will be able to create relationships between supporters as well as set a supporter as a primary contact for a household. Setting relationships can either be done via import (when importing there is a certain file format, reach out to support for help on this) or in the Lookup Supporters module.
There are two new gadgets in the Lookup Supporters module, which will help define and oversee relationships between supporters.
There is now a Manage Duplicates gadget under Data & Reports that allows you to set up this tool. This tool will allow organizations to set up ‘Matching rules’ that will check your data set for duplicates and then give you the ability to confirm and merge those contacts. This is a licensed feature - please contact your account representative to learn more about the pricing.
Opt-in and Questions have been added to the Page Components menu.
Finance Reports now include an option to export event transactions, which is an ‘ECS’ transaction type
An Email Engagement Score of 0 has been added to the Email Engagement Filter - a score of 0 is given to any supporter who is opted-in to any opt-in question but has not done anything (ex: donation, action, email activity, petition) within the last 12 months and creation date is less than 12 months. Note: If you are using a profile with Email Engagement Scores, you’ll want to check those profiles to ensure they are still working how you want them to work.
The ‘Campaign Insert’ layer has now been upgraded to allow for 'custom' URL parameters - this functionality allows a client to create and manage custom URL parameters that can be added to email links
The option to include or not include peer-to-peer donations has been added to the Fundraising Total Donations filter
Implemented a Fundraising Summary By Page data service ('Pledge Drive')
Roll call now lists supporters by most recent donation
A service that exposes events and their details has been created
A new transaction type, HSU (Hub Supporter Update) has now been added for supporters updating their details in the HUB
When creating emails in the EMA tool, you can now add campaign reference fields to each email in an EMA workflow. Campaign references are accessible in the UI when editing emails and data is exposed as part of the MBC transaction type in an export. Note: this feature must be enabled under the email settings initially.
Integration with Google Analytics has now been implemented with Marketing Automation emails
The ‘Supporter create date’ filters in the query builder have been updated to match the options that are available in profiles (for the Supporter create date filter)
PayPal Payflow Pro Gateway - We have added the ability to include PayPal as a secondary gateway on the same donation page.
Added a “copy URL” button to the UI layer
For non-image files, a UI layer similar to that for image files has been added
Social share tools have been updated to take into account Twitter's increase to 280 characters
You now have the option to set an Appeal Code to One-Click page types
Notification emails now include a receipt where the PDF file name contains the donor’s first name and last name
Other1, Other2, Other3, Other4, and Appeal Code tagged fields have now been exposed in the Transaction History gadget under Lookup Supporters
Registration Detail Report: addition of discount code used during registration
Twitter limit updated to 280 characters
Certain details of a split test page were not viewable when searched, this issue has now been resolved
An issue with editing the Tweet to Target block occurred on some page-builder two column layouts when used with an ‘unclosed div tag’, this issue has now been resolved
If a page-builder donation page had no receipt, it was still issuing a receipt number - this issue has now been resolved
The transaction date was not displaying in the Single Donations Gadget of Lookup Supporters - this issue has now been fixed
For consistency, the QCB (Question Checkbox) output is now the same for both export API and the User Query tool, if a MSU (Manage Supporter Update) transaction is generated
When creating a Marketing Automation email, the 'Reply to' was not updating when it was different from the ‘sender’, this has now been fixed
An issue was reported that there was a discrepancy between the (query builder) Marketing Automation export and Export API - this has now been fixed
There was a visual issue where the same icon was being used for all filters - the correct icons are now shown
In page-builder, a receipt number was still generated if a receipt was not set on a thank-you email - this bug has been addressed and a receipt number will no longer be generated
The custom notification emails did not show the blue insert buttons on first load - this has now been fixed.
When clicking through to a page from an email there was a conditional account setting regarding opt-ins that was being ignored - this has been fixed.
The overwrite page name feature did not work for Event pages - this bug has now been fixed
There was an issue with the code being truncated on the Site Design Custom CSS box - this issue has been resolved
© Engaging Networks | Company registered in England and Wales | Company number: 03848111