The Green Party uses several systems centrally and information is shared between these systems through various means, and not all information is shared across all systems. In this guide we'll go through the fields that are currently synced to Action Network, and how you can update these fields on behalf of Members and Supporters.
You should avoid editing the values of any of the custom fields listed in this guide. Any changes you make will not be passed through to our membership billing system, and will be rewritten when the record is synced with Chargebee, our membership biliing platform.
Which Custom Fields Are Synced To Action Network From GPEW Centrally?
- First Name
- Last Name
- Email
- Mobile Phone
- Home_Phone
- Address
- City
- Zip/Postal Code
- Country
- Do_Not_Phone: This field will have a value of True if the member has asked not to be contacted by phone.
- Birthdate: In the format YYYY/MM/DD
- GPEW_Age: This field is calculated by from the value in the birthdate field.
Geographically Determined Fields
These fields are updated based on the postcode provided when a members join, or update their details via the Membership Portal. They are currently only updated for Members. If you require an update of this information for Supporters please
raise a support ticket.
- Regional_Party
- Local_Party
- Ward
- Parliamentary_Constituency
- Local_Authority
- GPEW_County_Division
- GPEW_County_Council
- GPEW_Parish
- GPEW_Devolved_Constituency
- GPEW_Devolved_Region
- GPEW_Combined_Authority
- GPEW_Police_Force_Area
- GPEW_Westminster_Future (the Parliamentary Constituency value after the next election)
- Member: This will have a value of Yes for Members with an active subscription, No for cancelled Members, and will be blank for Supporters.
- Membership_Status: Current/Pending/Grace/Cancelled/Expired/Suspended/Expelled.
- Membership_Type: This will show the membership type and frequency, eg. Standard Monthly Membership.
- Membership_Join_Date: This field will show the earliest join date for the member in the format YYYY/MM/DD.
- Membership_End_Date: This field will show the date the Activists membership will end, or did end for cancelled memberships, in the format YYYY/MM/DD.
- Membership_Period_Start: This will show the start of their current or last membership period, the date when their payment was due in the format YYYY/MM/DD.
- Chargebee_ID: This field should be present for anyone who has had an active membership from 2020 onwards.
- Salesforce_Contact_ID: This field should be present for almost all activists.
- Civi_ID: This field should be present for anyone who existed in our previous membership system. Newer members will not have a value in this field.
All three of these fields help support the communication between our various systems and to help Digital Support staff with data quality diagnostics. They will likely have little importance to the majority of Action Network administrators.
How Do I Update These Fields?
For Members
As the information synced to Action Network for members comes from the membership billing system it's important that this is where their details are updated. Members can update their own details, and manage their membership via the
Member's Site or by contacting the Membership Team. We know that not all members will remember, want, or have the ability to update their details themselves. Any officer of the party can contact the membership team at
members@greenparty.org.uk to provide updated details for members.
For Supporters
As Supporter information isn't linked to a billing record their basic contact details can be edited directly in Action Network. However, you will require the "Overwrite Network Custom Field Data" permission enabled. You should avoid editing any of the geographically determined field values, and it's a good idea to notify the Membership Team of any change to the Do_Not_Phone field.
Just as with members you can contact the Membership Team to update any supporter details if you're unsure.
Why Are There Duplicate Fields For Some Activists And Are They Kept Up To Date?
During the initial transfer of member and supporter data to Action Network some fields were used which were later replaced. For example, Local Party became Local_Party; Parliamentary Constituency became Parliamentary_Constituency...etc. These old Custom Fields were removed from Action Network Groups, but you may find that a fellow administrator has added them back in error. These fields aren't updated centrally and may contradict the values held in the fields listed in this article.
There are also plenty of examples of Action Network administrators creating new Custom Fields which duplicate existing data. For example, GP Member, Local Party (London), or Local Party For Events. These fields may have served a purpose at some point, but they are likely to cause confusion to other administrators so it's a good idea to check with your fellow admins and remove these fields and their data.
What About Other Custom Fields?
Any other Custom Fields will have been created within your Action Network Group, or within any child Groups that may exist. Some may have also been sent from a parent Group. Most of the data in these fields flows up the network, and so regional parties will see most of the Custom Fields created by their local parties. It's a good idea to plan out how you'll use Custom Fields, whether they'll duplicate existing data, or if they will serve a purpose beyond their initial use.