Platform

New

• We've released an ActionNetwork integration! The new integration allows ControlShift organizations to have their petition signer and creator information automatically synced to ActionNetwork.
  
  As supporters take action on your ControlShift site, we'll automatically send their contact details to ActionNetwork, and the petition(s) your supporters took action on will be included in their ActionNetwork Action History. Signers and creators will be tagged with controlshift-petition-creator or controlshift-petition-signer depending on their role, and they'll also be tagged with the categories that correspond to the petition on ControlShift. Finally, opt-ins and unsubscribes will sync back to ActionNetwork. †
  
  This is the first version of the ActionNetwork integration, and support for syncing event attendees and group members will be included in subsequent iterations.  
  
  If you'd like to get started using the new integration, send us a support email.

Updates / Bug Fixes

• Our new SMS opt-in feature now includes support for a pre-checked checkbox that only becomes visible after the user begins entering their phone number. You can see an example of this behavior here: https://demo.controlshiftlabs.com/petitions/save-the-library.
  
  As part of our support of this new behavior, we've rearranged the phone number field on petition signature and event RSVP forms so that it's immediately above the corresponding disclaimer/opt-in. Org admins can configure the SMS opt-in by going to Settings > SMS Opt-In Types. †
  
  
• On the Deliverability page (Settings > Deliverability), we're now including timestamps for bounces, blocks, and drop events. †
  
  
• Our friends at Greenpeace have been building an open source tool to sync ControlShift database tables to Google Big Query on top of our Bulk Data API. You can find more information here: https://gitlab.greenpeace.org/global-data/csl-nightly-bq-load/.

Petitions

Updates / Bug Fixes

• We've added support for reCAPTCHA v3 protection of petition signature and creation forms. reCAPTCHA is a service provided by Google that detects whether site visitors are likely to be real users or bots. reCAPTCHA v3 is invisible to most users –  the verification process happens in the background, and only high risk users are shown the visible CAPTCHA. †
  
  reCAPTCHA is a third-party integration that org admins can enable from Settings > Integrations. For organizations who have completed our EU GDPR DPA, please note that Google is not considered an authorized subprocessor for reCAPTCHA, but is a third-party integration that can be enabled if the organization chooses to do so.
  
  We added reCAPTCHA support in response to a spate of spam signatures affecting a small number of our customers. If your organization was affected by the spam attack, we've already reached out to clarify next steps. We're also in the process of adding reCAPTCHA support for other forms, including user creation and RSVPs.
  
  
• When custom fields were added to petitions, we allowed admins to include numbers in the custom field's shortname. However, a number in the shortname would cause an error page when a user signed the petition and then reloaded the petition page. This is now fixed.
  
  
• We've updated the way we handle signature form errors when the one-click signature flow is shown. Now, if the one-click information retrieved from the CRM is all valid, but the user fails to choose an opt-in status (when the organization uses radio buttons), the user will stay on the one-click signature view and we'll show the error on the opt-in field only. Users whose one-click information is invalid or missing required pieces of data will be redirected to a blank signature form, but UTM and other URL parameters will be preserved.
  
  
• We fixed a Javascript error that occurred when a logged in user visited a petition they had not already signed. This error didn't change the user's experience, but it did lead to an error message in the user's browser console. 
  
   

Events

New

• We've changed the way virtual events are created on the platform. Now, when a user creates a virtual event, we'll ask them to choose whether the audience for their event is national or local.
  
  At the moment, this audience information is used when assigning events to particular regions. If the virtual event's audience location is part of an existing region, we'll assign that virtual event to the corresponding region. Admins will be able to see an event's audience information in the moderation queue. In the future, audience information will also be used for event search results.
  
  As part of this work, we've also changed the wording on the event creation form to make it more user friendly. We're now using "Make this an in-person event" instead of "Add a physical location". †

Updates / Bug Fixes

• Event invitation emails had broken images, but these are now fixed.

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.