Platform

Updates / Bug Fixes

• Infrastructure improvements. 

Petitions

Updates / Bug Fixes

• We've updated the logic we use to send pieces of content through our spam filter. Previously, all petitions, messages to decision makers, etc. were sent through the filter. However, this was causing identical templated campaigns (in the Efforts feature) and messages (in the Decision Makers feature) to be erroneously marked as spam. With the new logic, we first check to see how close the new campaign or message is to the admin-entered template. If the new content is less than 10% different than the template, we skip the spam filter. This should prevent false positives in Efforts and Decision Maker messages.
  
  
• In the blast email moderation queue, we previously allowed admins to update an email's 'from name' and 'from address'. However, to remain complaint with SPF/DKIM and to ensure deliverability, we've removed the ability to override the from address. Instead, admins can specify an alternate reply-to address that will be used if a recipient responds to the email. 
• For organizations using Segment, we've added a few new tracked events, including tracking for the Facebook, Twitter, and Email share buttons being clicked. If your organization is using Google Analytics with Segment, these events will be visible in Behavior > Events > All. 
  
  
• Previously, if a successful petition's settings were updated, we'd display a second (or third, or fourth...) success story in the petition's timeline section. We've updated the code so that petitions should not have duplicate success messages going forward. (Petitions that already have multiple messages will not be updated.)

Events

Updates / Bug Fixes

• On some calendars, logged out users could see a "More Events" link even if there weren't any more visible events. This has been fixed.
   
• We've moved the override emails settings out of the event Manage page and into the event Admin page. These overrides were only available to admins, so we moved them to keep everything consistent.
  
  
• The hide event functionality didn't behave in an expected way. Instead of making an event temporarily invisible, it was a soft delete of the event that could not be undone. That didn't make sense, so we've updated the code. Now, hiding an event just hides the even (and can be undone).
  
  
• We've added a new line to the stats block on calendar pages. In addition to the total number of events in a calendar, we now also include an Upcoming Events line that only counts upcoming, publicly visible events.  
  
  
• Org admins can now update a user's event RSVP status. More information: https://controlshiftlabs.zendesk.com/hc/en-us/articles/204369128#updatersvp.
  
  
• For organizations using Segment, we've added a few new tracked events, including tracking for the Facebook, Twitter, and Email share buttons being clicked. If your organization is using Google Analytics with Segment, these events will be visible in Behavior > Events > All. 
  
  

VisitThem

New

• We've released an API of our data, which is available to organization administrators. The API includes the ability to look up legislators by location and external ID. Legislator information will include district office locations and any associated events. More information about the API is available: http://developers.visitthem.org/.

Updates / Bug Fixes

• In their data tab, admins can now filter events by type (town halls, office hours, etc.) and perform an export of event data. 
  
  
• Also in their data tab, admins can add new events to the existing official event list. 

 Nothing new in groups or TakeCharge.