Updates / Bug Fixes
- We're now showing a banner warning on the admin homepage if your organization's deliverability settings are not configured correctly. The steps in our deliverability wizard will walk you through confirming that we're allowed to send platform emails on behalf of your organization.†
These settings are an important part of ensuring that your organization's emails are delivered to your supporters, and we strongly recommend completing the deliverability wizard as soon as possible. More information about these deliverability settings is available in our new deliverability guide.
- We've released a dashboard where your team can monitor bounces and overall platform deliverability. To access the dashboard, go to Settings > Deliverability. If you've already completed the Deliverability wizard, you'll see a Bounces link at the top of that tab. All emails that bounce, are blocked, or are dropped will show in this tab, along with additional details about what happened. (Please note: these records will be automatically destroyed after three months.) †
If you haven't yet completed the Deliverability wizard, you will not see bounce information on the Deliverability tab and you'll need to go through the process of completing your organization's email deliverability authentication. (If you're currently seeing a red banner at the top of your org admin homepage, that also means you need to complete the deliverability authentication.) This is an important setting that, in addition to enabling the deliverability monitoring tools and other upcoming features, will also improve the deliverability of your emails by having fewer of these emails sent to spam. If you have questions about deliverability, you can send us an email or check out our new deliverability guide.
- We've updated our name validation rules. We were previously not accepting names that looked like URLs. That meant that we were generally rejecting names that had single strings with periods unless they were clearly initials. (So "P.T. Barnum" and "Jane D." were accepted, but a first/last name of "notarealurl.fake" and "nota.realurl.fake" would have been rejected). This was causing an issue especially for partner organizations who wanted to use acronyms in their partner admin account first and/or last names. We've now changed the name validation rules to only reject strings that use a top level domain string (e.g. .com, .uk, .org., etc.) or an IPv4 IP address.
- For organizations using NGPVAN/EveryAction, some supporter data was failing to sync if the user's phone number didn't pass NGPVAN/EveryAction's phone number validation. If the phone number is rejected, we'll now reattempt the supporter sync without including the phone number.
- We're now including delimiters for large numbers in the petition > Admin > Signatures > Stats section and the Blast Emails page (org admin homepage > Blast Emails). For example, "30000" will now be "30,000" or "30.000" depending on your locale. This change should improve the readability for these large numbers.
- On the Blast Emails page we've also moved the unsubscribe count below the recipient count.
- In the unsubscribes CSV export (available from the org admin homepage > Members), we're now including two additional columns: source (the reason the user was unsubscribed) and external_ID.
Updates / Bug Fixes
- When a user clicks a social share and lands on the petition signature page, we'll now show the sharer's name at the top of the petition page (based on what they entered when they signed the petition, and according the privacy rules configured for your organization). The message will ask the new user to 'Join [the original signer] in signing this petition'. We've made this change following an a/b test that showed this message increased conversion rates. †
- We've made improvements to decrease load times for admin petition comments pages.
- For organizations using our Authenticated REST API for petitions data (https://developers.controlshiftlabs.com/#authenticated-rest-api) we're now including a launched boolean. The API includes all launched (visible in the platform) and unlaunched (not yet included in moderation/admin views) petitions, so the new boolean will differentiate between those two states.
Updates / Bug Fixes
- We've rolled out support for adding a web conference URL to virtual events. Now, when a user is creating a virtual event, they'll see a box to add the web conference URL on the event creation form. If entered, we'll include a 'Join Web Conference' button on the event page. Web conference URL information will also be included in the emails sent to hosts and attendees. Admins will also be able to see that information in the moderation queue. †
Nothing new in groups or VisitThem.
† This feature required new text strings. If you're using the platform in a language other than English, you may need to provide updated translations.