Luminate Advocacy Custom Targets Required Fields

Ryan O'Keefe

With the release of 17.1 we updated required fields on action alerts across the board. This was done to improve deliverability to some targets we've had issues with reaching in the past and get to 100% deliverability. Because of the dynamic nature in which we target elected officials through email/webform/fax we had to require those fields be added to ensure that all targets would be covered in case of changes to deliverability were to occur.


The changes we made adding required fields (title, first name, last name, street address 1, city, state, zipcode, and phone number) were made with the express intent of improving deliverability and not to cause additional issues with custom targets. Custom targets were affected by this change and it was noted that this was prohibiting orgs from quickly updating API forms and managing online petitions and other actions through custom target alerts because they were requiring additional fields.


We understand the impact to most of your custom target alerts and are moving to make a change on January 31. We are going to roll out a release to update custom targets and allow them to go back to being modified like they were previously. This would mean on Wednesday, February 1, organizations that have custom target only alerts would be allowed to update their forms. This is only for custom target only alerts. Any alert that has a standard elected officials and custom targets would have the newly required fields overriding the custom target fields. This is to ensure deliverability to those standard targets.


There will be some additional changes for advocacy coming in 17.3, but those changes will be around social tags. For now, we are focusing on deliverability and making sure we can reach those hard to reach targets.