FlywheelMA's forms provide an easy and powerful way to get new Contact data into your Flywheel system.
There are a variety of ways to integrate with an MA Form. You should choose the one that works best with your existing systems and technical resources. This article will briefly explain the options and provide links to specific implementation details.
Before you begin:
In order to integrate with an MA form, you first have to create one. The exact details are beyond the scope of this article, but basically you'll need to visit the forms module and create a Form with the fields that you would like to collect. A Form can also enforce field validation and start a variety of actions.
Let's dig into the integration options:
1. Flywheel MA Landing Pages:
A Landing Page is the easiest integration option for adding new forms. A Landing Page would need to replace an existing form.
Landing Pages are created in MA using the page builder. You can add text, images, etc to design the page.
Once the Landing Page is designed you have two options to integrate it with your website.
- Send users to the Landing Page url - each landing page includes a unique web address (url) - you can include this URL in emails or as a link on your webpage. Users will visit the landing page and can fill out the form.
- Use an iframe to embed the landing page on your website.
A Landing Page will properly handle field errors - it will display messages regarding any required fields or validation errors.
Landing Pages also allow you to start early-funnel analytics on visitors - tracking cookies will be applied and you'll be able to start measuring page hits and potentially begin remarking efforts.
The only downside to a Landing Page is that it may be challenging to fully match your existing html theme.
2. Submit your forms directly to Flywheel:
A second option is to create your own html forms, and submit them directly to Flywheel. Again, this acts as a replacement for existing forms because the form data will no longer go to your server, but instead will be directed to Flywheel.
This advantage of this option is that the fields match your existing theme and template. You will also receive similar start-of-funnel analytics and may be able to start tracking/remarketing cookies.
The downside is that you will need a developer/designer to create the fields and edit the submission url. This may not always be available without editing the html.
3. Use Server-side code to submit the form data to Flywheel:
A server-side integration provides a high degree of Flexibility and seamlessness.
In this scenario, you would need to have a developer (or, in some cases, a plugin) write code that sends the form data to Flywheel after it has been processed by your website.
This allows the form to continue to be themed and processed by the website, and for data to be sent to Flywheel after it has been processed by the website.
This scenario is ideal for customers who have an advanced website and technical resources who can tie into the form submission process. There are Flywheel-compatible plugins available for Wordpress or Statamic based websites.
This option provides limited analytics and tracking.
See this article for Integration Details: link
4. Use Client-side (ajax) code to submit the form data to Flywheel:
A Client-side submission provides the greatest degree of flexibility, but requires advanced technical skill.
Similar to option 3, this scenario allows your form to be fully integrated/themed with your website. However with this option, the data is sent to Flywheel before it goes to the website server. The advantage of this is simply that the data is validated by Flywheel before it is accepted. This could give you the ability to request the User to fix errors - for example an invalid email or missing field.
This option requires a sophisticated development team with great UI and javascript experience.
This option provides limited analytics and tracking.
Summary:
Option | Pros | Cons |
---|---|---|
Flywheel Landing Pages |
|
|
Submit Directly to MA |
|
|
Server-side Submission |
|
|
Client-side Submission |
|
|