Integrate your Forms data to flow into LGL
In this article:
A key feature of LGL Forms is its ability to integrate with your LGL account. It is not required to connect a form to LGL, but if you want some or all of the data collected by a form to end up in your LGL database, you'll definitely want to "Link" the form and set up the field mapping. This article describes how to do that.
Link a form to LGL
Every form can be "linked" to your LGL account. You can start the process from the Forms list by clicking the LGL Integration link or the Not Linked option in the LGL Status column:
From there, you will want to click the Link to LGL button above to connect this form to LGL so that its submissions can be sent automatically.
Once the form is linked to LGL, you will be automatically taken to the form mapping tool, where you can define the mapping rules that control how data from this form will be stored in LGL.
At the top of the mapping page, you will be able to set some general preferences for how this form should be connected to LGL:
- Connect to LGL Event: All of your active LGL events will be listed here. You can choose an event if you want submissions to this form to register as an event RSVP. This will also make any custom fields from that event available for mapping.
- Connect to LGL Appeal: Similar to events, you can link a form to an LGL appeal. All active appeals will be listed. Making this connection will automatically update that appeal in LGL.
- Record matching preferences: These settings are quite important and can be used all together. By default, email and name are the matching criteria selected.
- Match on email and name: Constituents will be looked up by email and first name and matched accordingly.
- Match on email only: Email alone is enough to match to an LGL constituent.
- Match on name only: First and last name must match.
- Record saving/updating preferences: These settings affect how submissions will be processed on the LGL side.
- Require review before saving?: Leave this checked (the default) if you want to review submissions in the LGL Forms submission queue before they get saved permanently. (Recommended)
- Do not update constituent name information: In the event of a constituent update, do not overwrite existing constituent name information with new information from the form. This is usually desired. Additional information such as emails, phones, categories, and so on will be added either way.
- Don't save $0 gifts: Don't create any gifts for which the amount is missing or is $0. This is not likely in the case of a donation form, but it might be possible in some other cases.
Mapping fields from your form to LGL will involve some thought. First, you need to know what information from the form you care about storing in LGL, and then you need to consider how to make the connection.
A simple example
The good news is that LGL Forms knows how a lot of the basic information can and should be mapped to LGL, and the mapping tool will take care of that for you. For instance, this simple form is almost completely mapped right from the start:
What the above example shows is that each submission will send the following information over about a single constituent:
- Name data (Prefix, First Name, Last Name, Suffix)
- Email Address (the email address)
- Street Address (Address line 1, line 2, City, State, Zip, Country)
Fields like "Phone Number" and "Payment Total" are also mapped automatically in this fashion. Note that submission date is not mapped in this example, and there’s no need to map it because LGL will stamp a new constituent record with the creation date automatically (or stamp the "updated date" for an existing record). In addition,
Please note that if a gift date is not supplied in your form submission, the date of submission will be used as the gift date.
In addition, submission date is not mapped (as shown in the example), and there’s no need to map it because LGL will stamp a new constituent record with the creation date automatically (or stamp the "updated date" for an existing record).
Once all the fields are mapped like this, you can click the Save & Finish button to save the mapping and finalize the connection to LGL. From that point forward, any submission to the form will be sent over to LGL with this mapping in place.
A complex example
Simple and automatic is good, but let's say you want to connect a donation form. This might be your "Donate now" form that is also aimed at collecting a bit of extra information about your donors and asking if they want to join your mailing list.
Here's an example:
With a form like this, the automated mapping logic will take care of the following fields:
- Gift amount (from the gift Amount field)
And the starting point will look like this:
As you can see, it needs some work before you can get the full benefit of the integration. Namely, the following needs to be done:
- Make sure that donors get onto your mailing list, if they choose to be added, and record the volunteer interests
- Set some default values for the contact information and gift information so these donations end up in the right place
Step 1. Connect unmapped fields
As a first step, you can map the fields you want to capture information from that have not been mapped already. You can easily see which fields have not been mapped at least once in the Form Fields column:
To map one of these fields, you can click on it, which will pop open the following form:
You first select the LGL Field Type (in this case Constituent Category) and then choose the appropriate LGL Field within that category. Saving the above selections will add a mapping like this:
In this case, each form submission will pass the value for "Join our mailing list?" into the LGL constituent category "Constant Contact Lists". In other words, you'll see constituents with a "Yes" or "No" as a value in the "Constant Contact Lists" category in LGL.
Value normalization/mapping One other thing to keep in mind about this case is that you need to consider the values from this field and how they translate to the equivalent field in LGL. To address this, there is a "Value mapping" component to the field mapping, which you can get to by clicking on the light blue "compass" icon:
Clicking that opens up the value mapping form, as shown below, and it is possible to determine which values should be mapped or ignored. In this case, Yes from the form field will be set to align with the LGLU Test 1 value in LGL, and given the way in which the LGL/Constant Contact integration works, this person will be added to the LGLU Test 1 mailing list in Constant Contact.
The Interests field would be handled in a similar way: first choosing to map the field, and then picking Constituent Category and selecting the appropriate LGL Field for that, followed by a value mapping exercise to make sure that things end up in the right place.
For another mapping example, we can look at the Submission Date field, which is typically mapped to Gift Date in LGL. Since the Submission Date might be used for a lot of purposes, it does not map automatically:
But you can take care of that quickly by:
- Clicking on the Submission Date field
- Choosing the "Gift" LGL Field Type
- Selecting the "Gift date" LGL Field
Keep in mind that if a gift date is not provided through a form submission, the date of submission will be used as the gift date.
...which will add the field to the Gift record like this:
After completing the mapping process for any fields like these, you can move on to setting defaults.
Step 2. Add default values to improve data quality
To add a default, you can choose the record that you want to update and click the Add default button:
Then choose the field to set the default for:
Next enter or select the appropriate value (LGL Forms will pull values from LGL where possible):
And, finally, save the default, so things end up like this:
This configuration is now telling LGL to attach the address type of "Home" to every email address sent into this particular field by this form.
You might also add defaults to the Gift record, setting any desired campaign, fund, appeal, event, or other gift information:
Note: Defaults come into play only if the information you need for this field is not going to be supplied by the form fields directly.
Save your work
With all the fields mapped, and defaults set, please click the Save & Finish button to make sure your mappings are saved.