Difference between revisions of "Integration"
(216 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
+ | <p style="font-size:30px">NEW!! Find all of your answers in the [https://helpdesk.growthzone.com/kb/article/1813-contents-integrations// GrowthZone Knowledge Base!]</p> | ||
+ | ==Connecting to Constant Contact== | ||
− | + | Through your GrowthZone software, you can sync contacts in your Lists/Committees to Constant Contact. Any additions, changes or deletions made to lists/committees that you have set to '''Synchronize Contacts with authorized third party newsletter solution''' will synchronize to Constant Contact near real-time. | |
− | + | {| class="wikitable" | |
+ | |- | ||
+ | | | ||
+ | [[File:Smallest.png|35px]] | ||
+ | | style="width: 100%"| '''NOTE:''' You may synchronize as many groups (lists/committees) as you wish with Constant Contact. See '''[[Communications_Basics#Working_with_Lists.2FCommittees|Setting Up Lists/Committees]]''' for information on configuring your lists/committees to synchronize to a third party newsletter. | ||
+ | |} | ||
#Click '''Setup''' in the left-hand navigation panel. | #Click '''Setup''' in the left-hand navigation panel. | ||
Line 34: | Line 41: | ||
---- | ---- | ||
− | Through your GrowthZone software, you can sync contacts in your Lists/Committees to Mail Chimp. Any additions, changes or deletions made to lists/committees that you have set to '''Synchronize Contacts with authorized third party newsletter solution''' will synchronize to Mail Chimp near real-time. See '''[[ | + | Through your GrowthZone software, you can sync contacts in your Lists/Committees to Mail Chimp. Any additions, changes or deletions made to lists/committees that you have set to '''Synchronize Contacts with authorized third party newsletter solution''' will synchronize to Mail Chimp near real-time. |
+ | |||
+ | {| class="wikitable" | ||
+ | |- | ||
+ | | | ||
+ | [[File:Smallest.png|35px]] | ||
+ | | style="width: 100%"| '''NOTE:''' You can synchronize as many groups (lists/committees) as needed to Mail Chimp. See '''[[Lists/Committees#Synchronize_a_List.2FCommittee_to_an_Authorized_Third_Party_Newsletter_Solution]]''' for information on configuring your lists/committees to synchronize to a third party newsletter. | ||
+ | |} | ||
==='''<span style="color:#800080">Connecting to Mail Chimp'''</span>=== | ==='''<span style="color:#800080">Connecting to Mail Chimp'''</span>=== | ||
Line 53: | Line 67: | ||
− | =='''<span style="color:#800080">Mail Chimp Synchronization'''</span>== | + | ==='''<span style="color:#800080">Mail Chimp Synchronization'''</span>=== |
---- | ---- | ||
Line 86: | Line 100: | ||
Once you have connected, you will be able to sync your events to GoToWebinar on the event's '''Overview''' tab, under '''General Information'''. Events synced, will automatically be created in GoToWebinar. When attendees register, they will receive confirmations from GoToWebinar with login instructions. | Once you have connected, you will be able to sync your events to GoToWebinar on the event's '''Overview''' tab, under '''General Information'''. Events synced, will automatically be created in GoToWebinar. When attendees register, they will receive confirmations from GoToWebinar with login instructions. | ||
+ | |||
+ | {| class="wikitable" | ||
+ | |- | ||
+ | | | ||
+ | [[File:One Row.png|25px]] | ||
+ | | style="width: 100%"| '''SYNCING PAID EVENTS''': If you wish to charge for a webinar and sync the event from GrowthZone, your event in GoToWebinar must be set up as a free event, as all payments will be processed through GrowthZone and not GoToWebinar. Setting the GoToWebinar event as a paid event will cause GoToWebinar to reject registrations coming from GrowthZone and will not sync registrants. | ||
+ | |} | ||
+ | |||
+ | ='''<span style="color:#800080">Zoom Integration'''</span>= | ||
+ | ---- | ||
+ | We now have the ability to integrate GrowthZone Events with Zoom Meetings. Once enabled, you'll be able to sync your event in GrowthZone to Zoom, and when synced, GrowthZone will automatically create the event in Zoom. Attendees will utilize the GrowthZone event registration form and be tracked in GrowthZone just like any other attendee. Once registered, they'll be captured in your Zoom event, and will automatically be sent the confirmation email from Zoom. | ||
+ | |||
+ | GrowthZone will automatically pass over the following information to Zoom if available: First Name, Last Name, Email Address, City, Country, Postal Code, State/Province, Phone, Organization and Job Title. | ||
+ | |||
+ | '''Best practice''': Do not select any Zoom registration Questions or Custom Questions in your Zoom registration setup. | ||
+ | |||
+ | '''More details''': It is not necessary to select any of these fields in your Zoom registration setup; it won't affect the registration if you do but it does not make any difference because the data noted above is automatically passed through. However, please note that marking any of the registration questions or custom questions as required in Zoom registration setup is not supported and will cause the registration to fail. | ||
+ | |||
+ | {| class="wikitable" | ||
+ | |- | ||
+ | | | ||
+ | [[File:One Row.png|25px]] | ||
+ | | style="width: 100%"| '''IMPORTANT''': You must have at minimum a Pro subscription to Zoom to use the Zoom Integration with GrowthZone. | ||
+ | |} | ||
+ | |||
+ | '''Please note:''' | ||
+ | * If a registrant comes to the event LIVE, they will not be marked as attended in GrowthZone. | ||
+ | * At this time we are not able to sync Webinar-type events in Zoom (i.e. Zoom + Webinar). | ||
+ | |||
+ | =='''<span style="color:#800080">Connecting to Zoom'''</span>== | ||
+ | ---- | ||
+ | With Zoom integration, you can create your events in GrowthZone and have the corresponding meeting created in Zoom. To enable Zoom integration: | ||
+ | #Click Setup in the left-hand navigation panel. | ||
+ | #Click Zoom in the Integrations section. | ||
+ | #Click Connect. | ||
+ | #:[[File:Zoom1a.jpg|800px|center|Zoom integration window]] | ||
+ | #Enter your Zoom credentials to login to Zoom and Authorize access to your Zoom account. | ||
+ | [[File:Zoom2.jpg|800px|center|Zoom credentials prompt window]] | ||
+ | |||
+ | Once you have connected, you will be able to sync your events to Zoom on the event's Overview tab, under General Information. Events synced, will automatically be created in Zoom. When attendees register, they will receive confirmations from Zoom with login instructions. | ||
+ | =='''<span style="color:#800080">Uninstalling the GrowthZone Zoom Add-On'''</span>== | ||
+ | ---- | ||
+ | To uninstall the GrowthZone Add-On from your Zoom account: | ||
+ | #Log in to your Zoom Account and navigate to the Zoom App Marketplace. | ||
+ | #Click '''Manage > Installed Apps''', or search for the '''GrowthZone''' App. | ||
+ | #Click the '''GrowthZone''' App. | ||
+ | =='''<span style="color:#800080">Disconnecting from Zoom'''</span>== | ||
+ | ---- | ||
+ | To disconnect from Zoom: | ||
+ | #Click Setup in the left-hand navigation panel. | ||
+ | #Click Zoom in the Integrations section. | ||
+ | #Click Disconnect. | ||
+ | =='''<span style="color:#800080">Syncing an Event with Zoom'''</span>== | ||
+ | ---- | ||
+ | An event can be synced to Zoom through two different screens. | ||
+ | #Events -> Add New Event (Button on top right) -> Enable the "Sync with Zoom" option toward the bottom of the screen. | ||
+ | #:[[File:ZoomAddNewEvent 06042020 new.png|800px|center]] | ||
+ | #If an event is already created, click on the event from the “Events” module. Then you should be able to click on the pencil within the “General Information” section, and enable the "Sync with Zoom" option. | ||
+ | #:[[File:ZoomExistingEvent 06042020.png|800px|center]] | ||
+ | |||
+ | '''NOTE:''' GrowthZone does not let you create a Zoom Meeting with a Start Date / Time prior to the current date time. | ||
+ | |||
+ | ==Joining the Zoom Meeting== | ||
+ | |||
+ | ==='''As an Organizer'''=== | ||
+ | #Log in to Zoom. | ||
+ | #Navigate to "Meetings" on the left navigation menu. | ||
+ | #Find your meeting and click "Start". | ||
+ | #:[[File:ZoomJoin 06162020.jpg|800px|center]] | ||
+ | |||
+ | ==='''As an Attendee'''=== | ||
+ | #Register for an event via the GrowthZone event registration page. | ||
+ | #You will receive an email from Zoom. | ||
+ | #Follow the link in the email to join the Zoom meeting. | ||
+ | |||
+ | ==Misc Zoom Info== | ||
+ | |||
+ | All Zoom Meetings are created with the following settings, all other settings are defaulted to Zoom’s defaults. | ||
+ | * Video Host: On | ||
+ | * Video Participant: Off | ||
+ | * Meeting Options: Enable Waiting Room | ||
+ | |||
+ | |||
+ | Below are the mappings of GrowthZone event fields to Zoom Meeting fields. | ||
+ | * Event Name -> Meeting Topic | ||
+ | * Event Start At -> Time | ||
+ | * Description -> Agenda | ||
='''<span style="color:#800080">Higher Logic'''</span>= | ='''<span style="color:#800080">Higher Logic'''</span>= | ||
Line 93: | Line 194: | ||
After the integration is in place, it is not necessary to complete any additional work to ensure that the data reflected on your community site remains synchronized with the GrowthZone AMS. GrowthZone uses Higher Logic's Push API Integration methodology. This type of integration allows GrowthZone to send updates directly to Higher Logic. | After the integration is in place, it is not necessary to complete any additional work to ensure that the data reflected on your community site remains synchronized with the GrowthZone AMS. GrowthZone uses Higher Logic's Push API Integration methodology. This type of integration allows GrowthZone to send updates directly to Higher Logic. | ||
+ | |||
+ | {| class="wikitable" | ||
+ | |- | ||
+ | | | ||
+ | [[File:One Row.png|25px]] | ||
+ | | style="width: 100%"| '''NOTE:''' The integration allows active individual members of lists/committees set to sync with a third party newsletter solution to use their InfoHub credentials to sign in to your Higher Logic communities. Data synced to Higher Logic is used for sharing the login information and cannot be edited in Higher Logic and synced back to GrowthZone. | ||
+ | |} | ||
===='''<span style="color:#800080">Higher Logic Authentication'''</span>==== | ===='''<span style="color:#800080">Higher Logic Authentication'''</span>==== | ||
Line 102: | Line 210: | ||
---- | ---- | ||
− | When synchronized to Higher Logic, GrowthZone will push (near real-time) changes to | + | When synchronized to Higher Logic, GrowthZone will push (near real-time) changes to the following records: |
*Contact Information | *Contact Information | ||
Line 109: | Line 217: | ||
*Lists/committees to which the contact is assigned | *Lists/committees to which the contact is assigned | ||
+ | We do '''NOT''' currently support the following types of updates via our Higher Logic integration: | ||
+ | *Security Groups | ||
+ | *Demographics | ||
+ | *Events | ||
+ | *Job History | ||
+ | *Education | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
| | | | ||
[[File:One Row.png|25px]] | [[File:One Row.png|25px]] | ||
− | | style="width: 100%"| '''NOTE:''' Individuals are pushed to Higher Logic, not organizations. When setting up lists/committees for synchronization to Higher Logic, ensure that individual contacts are added to the list/committee not a business/organization. | + | | style="width: 100%"| '''NOTE:''' Individuals are pushed to Higher Logic, not organizations. When setting up lists/committees for synchronization to Higher Logic, ensure that individual contacts are added to the list/committee not a business/organization. |
|} | |} | ||
Line 120: | Line 234: | ||
Higher Logic refers to lists/committees as '''Communities'''. If a new list/committee is pushed to Higher Logic, Higher Logic will automatically create the community, however it will be hidden. These communities will require further configuration in Higher Logic for the correct use, but they will not need to be created. A Higher Logic user with administrative rights would need to access the communities area, configure the community appropriately and un-hide it. '''[https://support.higherlogic.com/Content/IWantTo/ConfigAComm/CommunityTypes.htm Click Here]''' for Higher Logic documentation on managing communities. | Higher Logic refers to lists/committees as '''Communities'''. If a new list/committee is pushed to Higher Logic, Higher Logic will automatically create the community, however it will be hidden. These communities will require further configuration in Higher Logic for the correct use, but they will not need to be created. A Higher Logic user with administrative rights would need to access the communities area, configure the community appropriately and un-hide it. '''[https://support.higherlogic.com/Content/IWantTo/ConfigAComm/CommunityTypes.htm Click Here]''' for Higher Logic documentation on managing communities. | ||
− | |||
==='''<span style="color:#800080">Set Up Higher Logic Integration'''</span>=== | ==='''<span style="color:#800080">Set Up Higher Logic Integration'''</span>=== | ||
Line 158: | Line 271: | ||
#'''Link to HigherLogic Community Site''': This is automatically populated and should be the URL for your Higher Logic site. Best practice is to verify that this link is correct. | #'''Link to HigherLogic Community Site''': This is automatically populated and should be the URL for your Higher Logic site. Best practice is to verify that this link is correct. | ||
#'''Optional Custom Term for Community Link''': You can customize the Info Hub link, by default the link is named '''Community'''. | #'''Optional Custom Term for Community Link''': You can customize the Info Hub link, by default the link is named '''Community'''. | ||
− | #'''Optional Custom Icon for Community Link''': (Optional) You may enter a a Font Awesome icon to be displayed on the navigation panel for this item in the Info Hub. Visit the [https:// | + | #'''Optional Custom Icon for Community Link''': (Optional) You may enter a a Font Awesome icon to be displayed on the navigation panel for this item in the Info Hub. Visit the '''[https://fontawesome.com/icons?d=gallery&m=free Font Awesome]''' website. The icons you choose must be for supported '''FREE''' icons version 5. |
#Click '''Save'''. | #Click '''Save'''. | ||
Line 175: | Line 288: | ||
='''<span style="color:#800080">Voter Voice'''</span>= | ='''<span style="color:#800080">Voter Voice'''</span>= | ||
---- | ---- | ||
+ | |||
+ | =='''<span style="color:#800080">Overview</span>'''== | ||
Voter Voice is a third-party advocacy and lobbying platform. When enabled and linked, Growthzone provides a nightly sync of contact information to Voter Voice, updating records in Voter Voice to reflect changes made in Growthzone. The sync in GrowthZone will batch Active and Courtesy Member contact records and send them to the Voter Voice customer tenant nightly at 00:00 UTC; | Voter Voice is a third-party advocacy and lobbying platform. When enabled and linked, Growthzone provides a nightly sync of contact information to Voter Voice, updating records in Voter Voice to reflect changes made in Growthzone. The sync in GrowthZone will batch Active and Courtesy Member contact records and send them to the Voter Voice customer tenant nightly at 00:00 UTC; | ||
Line 190: | Line 305: | ||
#Click '''Save'''. | #Click '''Save'''. | ||
− | ='''<span style="color:#800080"> | + | =='''<span style="color:#800080">Data Sent</span>'''== |
− | =='' | + | When the integration between GrowthZone and Voter Voice is enabled, the following fields from GrowthZone are sent to Voter Voice: |
− | ---- | + | |
+ | <center> | ||
+ | <table border="1" cellpadding="0" cellspacing="0" style="border-collapse:collapse;border:none;mso-border-alt:solid windowtext .5pt; mso-yfti-tbllook:1184;mso-padding-alt:0in 5.4pt 0in 5.4pt;"> | ||
+ | |||
+ | <tr style="mso-yfti-irow:0;mso-yfti-firstrow:yes;"> | ||
+ | <td style="width:85.25pt;border:solid windowtext 1.0pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">Field Name</p> | ||
+ | </td> | ||
+ | <td style="width:382.25pt;border:solid windowtext 1.0pt; border-left:none;mso-border-left-alt:solid windowtext .5pt;mso-border-alt: solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">Description</p> | ||
+ | </td> | ||
+ | </tr> | ||
+ | <tr style="mso-yfti-irow:1;"> | ||
+ | <td style="width:85.25pt;border:solid windowtext 1.0pt; border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt; padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">ContactID</p> | ||
+ | </td> | ||
+ | <td style="width:382.25pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">The unique identifier of the contact's/member's GrowthZone record. | ||
+ | <br> | ||
+ | </p> | ||
+ | </td> | ||
+ | </tr> | ||
+ | <tr style="mso-yfti-irow:2;"> | ||
+ | <td style="width:85.25pt;border:solid windowtext 1.0pt; border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt; padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">FullName</p> | ||
+ | </td> | ||
+ | <td style="width:382.25pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">Member’s first and last name</p> | ||
+ | </td> | ||
+ | </tr> | ||
+ | <tr style="mso-yfti-irow:3;"> | ||
+ | <td style="width:85.25pt;border:solid windowtext 1.0pt; border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt; padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">Prefix</p> | ||
+ | </td> | ||
+ | <td style="width:382.25pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">Formal title which precedes member’s name Mr. Ms. Mrs. etc</p> | ||
+ | </td> | ||
+ | </tr> | ||
+ | <tr style="mso-yfti-irow:4;"> | ||
+ | <td style="width:85.25pt;border:solid windowtext 1.0pt; border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt; padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">FName</p> | ||
+ | </td> | ||
+ | <td style="width:382.25pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">Member’s first name</p> | ||
+ | </td> | ||
+ | </tr> | ||
+ | <tr style="mso-yfti-irow:5;"> | ||
+ | <td style="width:85.25pt;border:solid windowtext 1.0pt; border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt; padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">MName</p> | ||
+ | </td> | ||
+ | <td style="width:382.25pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">Member’s middle name</p> | ||
+ | </td> | ||
+ | </tr> | ||
+ | <tr style="mso-yfti-irow:6;"> | ||
+ | <td style="width:85.25pt;border:solid windowtext 1.0pt; border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt; padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">LName</p> | ||
+ | </td> | ||
+ | <td style="width:382.25pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">Member’s last name</p> | ||
+ | </td> | ||
+ | </tr> | ||
+ | <tr style="mso-yfti-irow:7;"> | ||
+ | <td style="width:85.25pt;border:solid windowtext 1.0pt; border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt; padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">Suffix</p> | ||
+ | </td> | ||
+ | <td style="width:382.25pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">Family generation and other suffixes - e.g. Jr., Sr., III, Esq. Note: do not enter designations here. There is a separate field for those.</p> | ||
+ | </td> | ||
+ | </tr> | ||
+ | <tr style="mso-yfti-irow:8;"> | ||
+ | <td style="width:85.25pt;border:solid windowtext 1.0pt; border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt; padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">Address</p> | ||
+ | </td> | ||
+ | <td style="width:382.25pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">Street name and address number of member’s address.</p> | ||
+ | </td> | ||
+ | </tr> | ||
+ | <tr style="mso-yfti-irow:9;"> | ||
+ | <td style="width:85.25pt;border:solid windowtext 1.0pt; border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt; padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">Address2</p> | ||
+ | </td> | ||
+ | <td style="width:382.25pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">This is a second line of address to be used for additional address information (building number, etc.).</p> | ||
+ | </td> | ||
+ | </tr> | ||
+ | <tr style="mso-yfti-irow:10;"> | ||
+ | <td style="width:85.25pt;border:solid windowtext 1.0pt; border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt; padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">Address3</p> | ||
+ | </td> | ||
+ | <td style="width:382.25pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">This is a third line of address to be used for additional address information (building number, etc.).</p> | ||
+ | </td> | ||
+ | </tr> | ||
+ | <tr style="mso-yfti-irow:11;"> | ||
+ | <td style="width:85.25pt;border:solid windowtext 1.0pt; border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt; padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">City</p> | ||
+ | </td> | ||
+ | <td style="width:382.25pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">Name of city for the address.</p> | ||
+ | </td> | ||
+ | </tr> | ||
+ | <tr style="mso-yfti-irow:12;"> | ||
+ | <td style="width:85.25pt;border:solid windowtext 1.0pt; border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt; padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">State</p> | ||
+ | </td> | ||
+ | <td style="width:382.25pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">State abbreviation.</p> | ||
+ | </td> | ||
+ | </tr> | ||
+ | <tr style="mso-yfti-irow:13;"> | ||
+ | <td style="width:85.25pt;border:solid windowtext 1.0pt; border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt; padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">Zip</p> | ||
+ | </td> | ||
+ | <td style="width:382.25pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">The 5-digit US Postal zip code.</p> | ||
+ | </td> | ||
+ | </tr> | ||
+ | <tr style="mso-yfti-irow:14;"> | ||
+ | <td style="width:85.25pt;border:solid windowtext 1.0pt; border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt; padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | ||
+ | |||
+ | <p style="margin-bottom:0in;line-height:normal;">B_Name</p> | ||
+ | </td> | ||
+ | <td style="width:382.25pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | ||
− | + | <p style="margin-bottom:0in;line-height:normal;">Name of the primary business associated to the member.</p> | |
+ | </td> | ||
+ | </tr> | ||
+ | <tr style="mso-yfti-irow:15;"> | ||
+ | <td style="width:85.25pt;border:solid windowtext 1.0pt; border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt; padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | ||
− | + | <p style="margin-bottom:0in;line-height:normal;">B_Title</p> | |
− | + | </td> | |
− | + | <td style="width:382.25pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | |
− | |||
− | |||
− | |||
− | + | <p style="margin-bottom:0in;line-height:normal;">Member’s business title.</p> | |
− | + | </td> | |
− | + | </tr> | |
− | + | <tr style="mso-yfti-irow:16;"> | |
− | + | <td style="width:85.25pt;border:solid windowtext 1.0pt; border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt; padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | |
− | |||
− | |||
− | |||
− | + | <p style="margin-bottom:0in;line-height:normal;">B_Phone</p> | |
+ | </td> | ||
+ | <td style="width:382.25pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | ||
− | + | <p style="margin-bottom:0in;line-height:normal;">Phone number of the primary business associated to the member.</p> | |
− | + | </td> | |
− | + | </tr> | |
− | + | <tr style="mso-yfti-irow:17;"> | |
− | + | <td style="width:85.25pt;border:solid windowtext 1.0pt; border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt; padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | |
− | |||
− | |||
− | === | + | <p style="margin-bottom:0in;line-height:normal;">B_Fax</p> |
+ | </td> | ||
+ | <td style="width:382.25pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | ||
− | + | <p style="margin-bottom:0in;line-height:normal;">Fax Number of the primary business associated to the member.</p> | |
− | + | </td> | |
− | + | </tr> | |
− | + | <tr style="mso-yfti-irow:18;"> | |
− | + | <td style="width:85.25pt;border:solid windowtext 1.0pt; border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt; padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | <p style="margin-bottom:0in;line-height:normal;">B_Address</p> | |
− | ---- | + | </td> |
− | + | <td style="width:382.25pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | |
− | + | <p style="margin-bottom:0in;line-height:normal;">Street name and address of the primary business associated to the member.</p> | |
− | + | </td> | |
+ | </tr> | ||
+ | <tr style="mso-yfti-irow:19;"> | ||
+ | <td style="width:85.25pt;border:solid windowtext 1.0pt; border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt; padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | ||
− | + | <p style="margin-bottom:0in;line-height:normal;">B_Address2</p> | |
+ | </td> | ||
+ | <td style="width:382.25pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | ||
− | + | <p style="margin-bottom:0in;line-height:normal;">This is a second line of address to be used for additional address information (building number, etc.) of the primary business associated to the member.</p> | |
− | + | </td> | |
− | + | </tr> | |
− | + | <tr style="mso-yfti-irow:20;"> | |
− | + | <td style="width:85.25pt;border:solid windowtext 1.0pt; border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt; padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | |
− | |||
− | |||
− | |||
− | |||
+ | <p style="margin-bottom:0in;line-height:normal;">B_City</p> | ||
+ | </td> | ||
+ | <td style="width:382.25pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | ||
− | + | <p style="margin-bottom:0in;line-height:normal;">City of the primary business associated to the member</p> | |
− | + | </td> | |
− | + | </tr> | |
− | + | <tr style="mso-yfti-irow:21;"> | |
+ | <td style="width:85.25pt;border:solid windowtext 1.0pt; border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt; padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | ||
+ | <p style="margin-bottom:0in;line-height:normal;">B_State</p> | ||
+ | </td> | ||
+ | <td style="width:382.25pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | ||
− | + | <p style="margin-bottom:0in;line-height:normal;">State of the primary business associated to the member</p> | |
− | + | </td> | |
− | + | </tr> | |
− | + | <tr style="mso-yfti-irow:22;mso-yfti-lastrow:yes;"> | |
− | + | <td style="width:85.25pt;border:solid windowtext 1.0pt; border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt; padding:0in 5.4pt 0in 5.4pt;" valign="top" width="114"> | |
+ | <p style="margin-bottom:0in;line-height:normal;">B_Zip</p> | ||
+ | </td> | ||
+ | <td style="width:382.25pt;border-top:none;border-left: none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt; mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt; mso-border-alt:solid windowtext .5pt;padding:0in 5.4pt 0in 5.4pt;" valign="top" width="510"> | ||
− | + | <p style="margin-bottom:0in;line-height:normal;">The 5-digit US Postal zip code of the primary business associated to the member.</p> | |
− | + | </td> | |
+ | </tr> | ||
+ | </table></center> | ||
− | ''' | + | ='''<span style="color:#800080">Builder Edition Integrations'''</span>= |
− | + | =='''<span style="color:#800080">WMS Export'''</span>== | |
− | + | ---- | |
− | + | <h3>See article in the [https://helpdesk.growthzone.com/kb/article/138-builder-edition-integrations/ GrowthZone Knowledge Base]</h3> | |
+ | ='''<span style="color:#800080">REALTOR Edition Integrations'''</span>= | ||
+ | ---- | ||
− | ''' | + | See '''[[Real_Estate_Integration|Real Estate Edition Integration]]'''. |
− | |||
− | |||
− | |||
− | |||
+ | ='''<span style="color:#800080">IIABA State Integration'''</span>= | ||
+ | ---- | ||
− | + | See '''[[IIABA_State_Integration|IIABA State Integration]]'''. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
='''<span style="color:#800080">GrowthZone APIs'''</span>= | ='''<span style="color:#800080">GrowthZone APIs'''</span>= |
Latest revision as of 17:15, 24 May 2021
NEW!! Find all of your answers in the GrowthZone Knowledge Base!
Contents
Connecting to Constant Contact
Through your GrowthZone software, you can sync contacts in your Lists/Committees to Constant Contact. Any additions, changes or deletions made to lists/committees that you have set to Synchronize Contacts with authorized third party newsletter solution will synchronize to Constant Contact near real-time.
NOTE: You may synchronize as many groups (lists/committees) as you wish with Constant Contact. See Setting Up Lists/Committees for information on configuring your lists/committees to synchronize to a third party newsletter. |
- Click Setup in the left-hand navigation panel.
- Click Constant Contact in the Integrations section.
- Click Connect.
- Enter your credentials for Constant Contact, and click Log-in.
- Click Allow on the Allow Access screen. This process authorizes the connection between GrowthZone and Constant Contact. Once completed, you will see the ConstantContact status updated to Connected.
After initial connection, click the Sync button. This will synchronize all of your existing lists/committees, that are set to you Synchronize Contacts with authorized third party newsletter solution, with Constant contact. NOTE: Only contacts with a default/primary email address and where Do Not Contact is not enabled, will be synchronized to Constant Contact.
Constant Contact Synchronization
Once your system is setup to synchronize to Constant Contact, the following additions, edits, and deletions performed in GrowthZone will be sent to Constant Contact in near real-time (usually within ten minutes):
- A new List/Committee is added to GrowthZone with “Synchronize contacts with authorized third party newsletter” set: The new list/committee is added to Constant Contact.
- A new contact (with valid default/primary email address) is added to the List/Committee in GrowthZone: The new contact is added within that group in Constant Contact
- A new contact (with valid default/primary email address) is added to the List/Committee in GrowthZone with Do Not Contact is set: The new contact is NOT synchronized to Constant Contact
- The “Do Not Contact” check-box is set for an existing contact in the List/Committee within GrowthZone: The existing contact is disabled in Constant Contact, and removed from the list/committee in Constant Contact.
- The "Do Not Contact" check-box is cleared for an existing contact in the List/Committee within GrowthZone: If the contact, that would previously have been disabled in Constant Contact, is re-enabled.
- An existing contact's name and/or default email address is changed (and the contact belongs to the List/Committee synched to Constant Contact): The updated contact information is sent to Constant Contact.
- An existing contact is removed from a List/Committee in GrowthZone: The contact is removed from the List/Committee in Constant Contact. If the contact is not a part of other lists, the contact is disabled.
- If a List/Committee is deleted from GrowthZone: The List/Committee is deleted from Constant Contact. If there are contacts in the Lists/Committees, and those contacts belong to no other Lists/Committees, they are disabled in Constant Contact.
- A contact who is in multiple Lists/Committees in GrowthZone is deleted from GrowthZone: The contact is deactivated in Constant Contact.
Mail Chimp Integration
Through your GrowthZone software, you can sync contacts in your Lists/Committees to Mail Chimp. Any additions, changes or deletions made to lists/committees that you have set to Synchronize Contacts with authorized third party newsletter solution will synchronize to Mail Chimp near real-time.
NOTE: You can synchronize as many groups (lists/committees) as needed to Mail Chimp. See Lists/Committees for information on configuring your lists/committees to synchronize to a third party newsletter. |
Connecting to Mail Chimp
- Click Setup in the left-hand navigation panel.
- Click Mail Chimp in the Integrations section.
- Click Connect.
- Enter your credentials for Mail Chimp, and click Log-in.
- Connection status will show Connected and your Organization Contact Information will be displayed.
- Select an Audience from the MailChimp audience drop-down list. All contacts will be brought into MailChimp in this single Audience, tagged with the name of the GrowthZone List/Committee. When sending your emails from MailChimp, you will select this audience, filtered by the desired tag. See more info on Mailchimp Tags and How to Send Emails Filtered by Tags
- Click Save.
After initial connection, click the Sync button. This will synchronize all of your existing lists/committees, that are set to you Synchronize Contacts with authorized third party newsletter solution, with Mail Chimp. NOTE: Only contacts with a default/primary email address and where Do Not Contact is not enabled, will be synchronized to Mail Chimp.
Mail Chimp Synchronization
Once your system is connected, the following additions, edits, and deletions performed in GrowthZone will be sent to Mail Chimp in near real-time (usually within ten minutes):
- A new List/Committee is added to GrowthZone with “Synchronize contacts with authorized third party newsletter” set: The new list/committee is added to Mail Chimp.
- A new contact (with valid default/primary email address) is added to the List/Committee in GrowthZone: The new contact is added within that group in Mail Chimp.
- A new contact (with valid default/primary email address) is added to the List/Committee in GrowthZone with Do Not Contact set: The new contact is NOT synchronized to Mail Chimp.
- The “Do Not Contact” check-box is set for an existing contact in the List/Committee within GrowthZone: The existing contact is unsubscribed in Mail Chimp, and removed from the list/committee in Mail Chimp.
- The "Do Not Contact" check-box is cleared for an existing contact in the List/Committee within GrowthZone: If the contact, that would previously have been disabled in Mail Chimp, is re-enabled.
- An existing contact's name and/or default email address is changed (and the contact belongs to the List/Committee synched to Mail Chimp): The updated contact information is sent to Mail Chimp.
- An existing contact is removed from a List/Committee in GrowthZone: The contact is removed from the List/Committee in Mail Chimp. If the contact is not a part of other lists, the contact is disabled.
- If a List/Committee is deleted from GrowthZone: The List/Committee is deleted from Mail Chimp. If there are contacts in the Lists/Committees, and those contacts belong to no other Lists/Committees, they are disabled in Mail Chimp.
- A contact who is in multiple Lists/Committees in GrowthZone is deleted from GrowthZone: The contact is deactivated in Mail Chimp.
NOTE: If a user unsubscribes from a list via MailChimp, Do Not Contact will be set for the contact on that list in GrowthZone. |
GoToWebinar Integration
With GoToWebinar integration, you can create your events in GrowthZone and have the corresponding event create in GoToWebinar. To enable GoToWebinar integration:
- Click Setup in the left-hand navigation panel.
- Click GoToWebinar in the Integrations section.
- Enter your GoToWebinar user name and password.
- Click Connect.
Once you have connected, you will be able to sync your events to GoToWebinar on the event's Overview tab, under General Information. Events synced, will automatically be created in GoToWebinar. When attendees register, they will receive confirmations from GoToWebinar with login instructions.
SYNCING PAID EVENTS: If you wish to charge for a webinar and sync the event from GrowthZone, your event in GoToWebinar must be set up as a free event, as all payments will be processed through GrowthZone and not GoToWebinar. Setting the GoToWebinar event as a paid event will cause GoToWebinar to reject registrations coming from GrowthZone and will not sync registrants. |
Zoom Integration
We now have the ability to integrate GrowthZone Events with Zoom Meetings. Once enabled, you'll be able to sync your event in GrowthZone to Zoom, and when synced, GrowthZone will automatically create the event in Zoom. Attendees will utilize the GrowthZone event registration form and be tracked in GrowthZone just like any other attendee. Once registered, they'll be captured in your Zoom event, and will automatically be sent the confirmation email from Zoom.
GrowthZone will automatically pass over the following information to Zoom if available: First Name, Last Name, Email Address, City, Country, Postal Code, State/Province, Phone, Organization and Job Title.
Best practice: Do not select any Zoom registration Questions or Custom Questions in your Zoom registration setup.
More details: It is not necessary to select any of these fields in your Zoom registration setup; it won't affect the registration if you do but it does not make any difference because the data noted above is automatically passed through. However, please note that marking any of the registration questions or custom questions as required in Zoom registration setup is not supported and will cause the registration to fail.
IMPORTANT: You must have at minimum a Pro subscription to Zoom to use the Zoom Integration with GrowthZone. |
Please note:
- If a registrant comes to the event LIVE, they will not be marked as attended in GrowthZone.
- At this time we are not able to sync Webinar-type events in Zoom (i.e. Zoom + Webinar).
Connecting to Zoom
With Zoom integration, you can create your events in GrowthZone and have the corresponding meeting created in Zoom. To enable Zoom integration:
- Click Setup in the left-hand navigation panel.
- Click Zoom in the Integrations section.
- Click Connect.
- Enter your Zoom credentials to login to Zoom and Authorize access to your Zoom account.
Once you have connected, you will be able to sync your events to Zoom on the event's Overview tab, under General Information. Events synced, will automatically be created in Zoom. When attendees register, they will receive confirmations from Zoom with login instructions.
Uninstalling the GrowthZone Zoom Add-On
To uninstall the GrowthZone Add-On from your Zoom account:
- Log in to your Zoom Account and navigate to the Zoom App Marketplace.
- Click Manage > Installed Apps, or search for the GrowthZone App.
- Click the GrowthZone App.
Disconnecting from Zoom
To disconnect from Zoom:
- Click Setup in the left-hand navigation panel.
- Click Zoom in the Integrations section.
- Click Disconnect.
Syncing an Event with Zoom
An event can be synced to Zoom through two different screens.
- Events -> Add New Event (Button on top right) -> Enable the "Sync with Zoom" option toward the bottom of the screen.
- If an event is already created, click on the event from the “Events” module. Then you should be able to click on the pencil within the “General Information” section, and enable the "Sync with Zoom" option.
NOTE: GrowthZone does not let you create a Zoom Meeting with a Start Date / Time prior to the current date time.
Joining the Zoom Meeting
As an Organizer
- Log in to Zoom.
- Navigate to "Meetings" on the left navigation menu.
- Find your meeting and click "Start".
As an Attendee
- Register for an event via the GrowthZone event registration page.
- You will receive an email from Zoom.
- Follow the link in the email to join the Zoom meeting.
Misc Zoom Info
All Zoom Meetings are created with the following settings, all other settings are defaulted to Zoom’s defaults.
- Video Host: On
- Video Participant: Off
- Meeting Options: Enable Waiting Room
Below are the mappings of GrowthZone event fields to Zoom Meeting fields.
- Event Name -> Meeting Topic
- Event Start At -> Time
- Description -> Agenda
Higher Logic
The integration between the GrowthZone AMS and your Higher Logic Community site drives object creation in the community from the vast amount of up to date member data that you already track in the GrowthZone AMS. The integration ensures that your members interact with the most up to date member data, boosting member participation, collaboration and retention. Through your GrowthZone software you can sync your lists/committees to Higher Logic.
After the integration is in place, it is not necessary to complete any additional work to ensure that the data reflected on your community site remains synchronized with the GrowthZone AMS. GrowthZone uses Higher Logic's Push API Integration methodology. This type of integration allows GrowthZone to send updates directly to Higher Logic.
NOTE: The integration allows active individual members of lists/committees set to sync with a third party newsletter solution to use their InfoHub credentials to sign in to your Higher Logic communities. Data synced to Higher Logic is used for sharing the login information and cannot be edited in Higher Logic and synced back to GrowthZone. |
Higher Logic Authentication
To authenticate with Higher Logic an API Gateway Key and Tenant Code are needed for the Push API method. The API Gateway Key is generated by Higher Logic and the Tenant Code is specific to the client’s Higher Logic’s instance. The Tenant Code is generated by Higher Logic, and is entered into GrowthZone in the Higher Logic integration settings. Click Here for Higher Logic documentation on integration. Please contact support@higherlogic.com and ask for an API key that can be used to integrate your GrowthZone account. If you are just starting with Higher Logic, mention this integration to your Higher Logic Account Manager and he will give you this key.
Higher Logic Synchronization
When synchronized to Higher Logic, GrowthZone will push (near real-time) changes to the following records:
- Contact Information
- Organizations
- Membership Types
- Lists/committees to which the contact is assigned
We do NOT currently support the following types of updates via our Higher Logic integration:
- Security Groups
- Demographics
- Events
- Job History
- Education
NOTE: Individuals are pushed to Higher Logic, not organizations. When setting up lists/committees for synchronization to Higher Logic, ensure that individual contacts are added to the list/committee not a business/organization. |
Only the records of Active members associated to groups for which the Synchronize Contacts with authorized third party newsletter solution is enabled will be pushed to Higher Logic. Click Here for information on configuring groups to synchronize to a third party.
Higher Logic refers to lists/committees as Communities. If a new list/committee is pushed to Higher Logic, Higher Logic will automatically create the community, however it will be hidden. These communities will require further configuration in Higher Logic for the correct use, but they will not need to be created. A Higher Logic user with administrative rights would need to access the communities area, configure the community appropriately and un-hide it. Click Here for Higher Logic documentation on managing communities.
Set Up Higher Logic Integration
- Select Setup in the Navigation Panel.
- Select Higher Logic in the Integrations section. This will open the Higher Logic Integration dialog box.
- Click Enabled.
- Enter the Tenant Code provided by Higher Logic.
- Enter the Tenant API Key from Higher Logic
- Click Save.
- Once the integration settings have been saved, click the Sync button. This will synchronize all of the lists/committees for which you have enabled Synchronize Contacts with authorized third party newsletter solution to Higher Logic. If you plan on using Single Sign-on, it is important that you do this initial synchronization prior to enabling single sign-on. This ensures that Higher Logic has a record of the users who are attempting to access Higher Logic from the Info Hub.
After initial synchronization, the system will look for additions, changes, and deletions from list/committees that are set to synchronize with Higher Logic and push these changes to Higher Logic within 30 minutes. As access to Higher Logic is intended to be a member benefit, only Active members in the lists/committees will be pushed over to Higher Logic. The List/Committee Setting Do Not Contact has no impact on synchronization for Higher Logic. Higher Logic is used as a community forum, not for email purposes.
Higher Logic Single Sign-on
GrowthZone AMS’s API provides a seamless Web experience across the GrowthZone AMS and other third-party systems. It allows users to login to your Info Hub (Members Only Area) and gain secure access to all related Web sites, including your Higher Logic Community using the same login credentials they would use with the GrowthZone AMS Info Hub. Single Sign-On (SSO) is accomplished by using GrowthZone’s implementation of OAuth 2.0, an industry-standard protocol for authorization.
Only Active members, assigned to lists/committees that are synchronized to Higher Logic will be able to access Higher Logic. If a member is dropped, or removed from a list/committee they will no longer be able to access Higher Logic. Your active staff members will also have access via single sign-on to Higher Logic.
Setting Up Single Sign-on
NOTE: You must complete the Higher Logic Integration setup prior to setting up Single Sign On. Your members will not be able to sign in if the integration has not been setup. |
- Select Setup in the Navigation Panel.
- Select Higher Logic in the Integrations section. This will open the Higher Logic Integration dialog box.
- Click the Show Single Sign-On link in the Info Hub check-box.
- Link to HigherLogic Community Site: This is automatically populated and should be the URL for your Higher Logic site. Best practice is to verify that this link is correct.
- Optional Custom Term for Community Link: You can customize the Info Hub link, by default the link is named Community.
- Optional Custom Icon for Community Link: (Optional) You may enter a a Font Awesome icon to be displayed on the navigation panel for this item in the Info Hub. Visit the Font Awesome website. The icons you choose must be for supported FREE icons version 5.
- Click Save.
The first time a member clicks the Community (or the terminology you have configured) link in the Info Hub, an authorization page will be displayed. The member must click the Grant button to access Higher Logic. The next time the member accesses Higher Logic, the member will automatically be logged in.
NOTE: Within Higher Logic there is an Edit Profile option. When this option is selected, the member is re-directed to the GrowthZone Info Hub to update information. This ensures that GrowthZone, the system of record, is accurately updated. |
Voter Voice
Overview
Voter Voice is a third-party advocacy and lobbying platform. When enabled and linked, Growthzone provides a nightly sync of contact information to Voter Voice, updating records in Voter Voice to reflect changes made in Growthzone. The sync in GrowthZone will batch Active and Courtesy Member contact records and send them to the Voter Voice customer tenant nightly at 00:00 UTC; This is also a one-way sync/push, you should update the contact record in GrowthZone and let it push to Voter Voice.
Use the following steps to enable Voter Voice:
- Select Setup in the Navigation Panel.
- Select Voter Voice in the Integrations section.
- Click the Is Enabled check-box.
- Enter the Voter Voice API Key. You must contact Voter Voice to receive this key.
- Enter the Voter Voice List Name. . The default list name is “Default List”. The can find this in the Voter Voice admin panel.
- Click Save.
Data Sent
When the integration between GrowthZone and Voter Voice is enabled, the following fields from GrowthZone are sent to Voter Voice:
Field Name |
Description |
ContactID |
The unique identifier of the contact's/member's GrowthZone record.
|
FullName |
Member’s first and last name |
Prefix |
Formal title which precedes member’s name Mr. Ms. Mrs. etc |
FName |
Member’s first name |
MName |
Member’s middle name |
LName |
Member’s last name |
Suffix |
Family generation and other suffixes - e.g. Jr., Sr., III, Esq. Note: do not enter designations here. There is a separate field for those. |
Address |
Street name and address number of member’s address. |
Address2 |
This is a second line of address to be used for additional address information (building number, etc.). |
Address3 |
This is a third line of address to be used for additional address information (building number, etc.). |
City |
Name of city for the address. |
State |
State abbreviation. |
Zip |
The 5-digit US Postal zip code. |
B_Name |
Name of the primary business associated to the member. |
B_Title |
Member’s business title. |
B_Phone |
Phone number of the primary business associated to the member. |
B_Fax |
Fax Number of the primary business associated to the member. |
B_Address |
Street name and address of the primary business associated to the member. |
B_Address2 |
This is a second line of address to be used for additional address information (building number, etc.) of the primary business associated to the member. |
B_City |
City of the primary business associated to the member |
B_State |
State of the primary business associated to the member |
B_Zip |
The 5-digit US Postal zip code of the primary business associated to the member. |
Builder Edition Integrations
WMS Export
See article in the GrowthZone Knowledge Base
REALTOR Edition Integrations
See Real Estate Edition Integration.
IIABA State Integration
GrowthZone APIs
Using the GrowthZone APIs is a way to easily integrate your GrowthZone data into other systems. Examples may include incorporating content like directories, events, etc. into a CMS, creating an SSO with your website or another application, or tying a mobile app to your GrowthZonedatabase. The API is a standard REST-based API with the ability to access many areas of the software.
Click Here to view a full list of available GrowthZone APIs. GrowthZone's APIs are under active development and changes or additions can occur. This documentation is updated regularly and always represents the current state. APIs in GrowthZone are broadly organized by areas of use (i.e. modules).
NOTE: In order to begin making calls to GrowthZone, you will need to first have API access enabled in your tenant and obtain an API Client ID and Secret. For authentication options, we currently support standard oAuth2 flows and SAML. If you have questions or need help regarding API authentication, integration or support, please call 800.825.9171 or email support@growthzone.com. |