Platform

New

• We've released a new API endpoint and member setting that allows organizations to anonymize members without decreasing a petition's signature count or leaving blank rows in a petition's delivery documents. (Please note: this is a different feature than the 'anonymize petition' feature. The anonymize petition feature is a more thorough member deletion feature vs. this feature, which is a softer member anonymization.) When a member is anonymized (either from their member page > Settings tab or from the API endpoint: https://developers.controlshiftlabs.com/#members), the majority of their member data is deleted, but their name (or initials) will remain in the system and will still be used in delivery documents. This feature may be useful for organizations considering how to handle older petitions in a GDPR-compliant way.*
  
  Organizations can choose how to display the name/initials of anonymized members from the organization's Settings > Privacy tab. †

Updates / Bug Fixes

• For organizations syncing to ActionKit, we're now appropriately stripping emojis from petition titles when syncing to AK. ActionKit doesn't support emojis in that field, so this was causing a sync error. 
  
  
• For organizations syncing to ActionKit, we're now including a controlshift_api_unsub source code when we sync unsubscribes from ControlShift to ActionKit.  
  
  
• On member pages, our help text explaining labels was sometimes covered by the label field or in RTL languages had other display issues. We've removed the help text from that page.
   
• We've updated the images and text we use on 404 and 500 error pages. Hopefully you won't see those pages, but if you do, the images are new. †

Petitions

Updates / Bug Fixes

• We're now including utm_source and utm_medium parameters on promoted petitions. The utm_medium can be set from your organization's Social Media settings page. The utm_source will be after-signing-promote-modal.
  
  
• In the thank you for creating/signing a petition emails, we're now allowing organizations to override the default source and utm_source for the facebook share buttons. To override the default source, you can update the variable in the emails to {% facebook_share_url source: foo %} where foo is your chosen source code. Here's an example of code you could use, if you wanted to use fb.thanks as the source code.
  
  <div style="text-align:center;padding-bottom:10px"> <a style="text-decoration:none;color:#ffffff;background-color:#3b5998;border:solid #3b5998;border-width:10px 20px;line-height:2;font-weight:bold;text-align:center;cursor:pointer;display:inline-block;border-radius:5px" href="{% facebook_share_url source: fb.thanks %}"> SHARE ON FACEBOOK </a> </div>
  
  
• We've updated the 'other ways to share' URL in the just launched banner to include share click tracking and a default  source and utm_source of rawlink.
  
  
• We received reports that Facebook messenger was not working correctly on mobile phones. We've rolled out an update and sharing should be fixed now.
  
  
• We've removed the sharing toolbar from the petition's review page. The buttons on this page were meant to show the petition creator what the petition page would look like, but they weren't clickable since the petition hadn't been launched yet. This was causing confusion for some petition creators, so we've removed the buttons. 

Events

Updates / Bug Fixes

• For groups that have disabled the events tools, we were previously still showing the events tools to partner admins. This has been updated so that disabling the events tools will also disable them for partners.
  
  
• We've updated the 'other ways to share' URL in the just launched banner to include share click tracking and a default  source and utm_source of rawlink.
  
  
• In the thank you for hosting/RSVPing to an event emails, we're now allowing organizations to override the default source and utm_source for the facebook share buttons. To override the default source, you can update the variable in the emails to {% facebook_share_url source: foo %} where foo is your chosen source code. Here's an example of code you could use, if you wanted to use fb.thanks as the source code.
  
  <div style="text-align:center;padding-bottom:10px"> <a style="text-decoration:none;color:#ffffff;background-color:#3b5998;border:solid #3b5998;border-width:10px 20px;line-height:2;font-weight:bold;text-align:center;cursor:pointer;display:inline-block;border-radius:5px" href="{% facebook_share_url source: fb.thanks %}"> SHARE ON FACEBOOK </a> </div>
  

Nothing new in groups or VisitThem.

* We're not lawyers, and you shouldn't interpret this feature or this description of the feature to be a legal recommendation about how to maintain GDPR compliance. As with all things GDPR, we strongly encourage organizations to seek independent legal review of their processes and systems. 

† 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.