Fergus Booking Forms

Send Fergus booking form events to Google Analytics, Tag Manager and Meta

3 min read Fergus booking form

Tracking sends an event to Google Analytics, Google Tag Manager or the Meta pixel at five points as the customer moves through the form. You choose the name of each event. An event with no name sends nothing.

Before you start

  • Tracking is a Business feature. On the Free plan the page says "Want to track your form?" with "Tracking events are only available to Fergus booking form subscribers.", and every box is disabled. The form sends nothing.
  • The tracking tool has to be loaded on the web page that holds the form. Formpiece does not add it. The page tells you so for each of the three.

Step by step

  1. Open your form from Forms. On the Settings tab, open Tracking under Form responses.
  2. Under the tool you use, type a name against each event.
  3. Click Save.

Names can be up to 40 characters. The empty boxes suggest fp_first_engage, fp_service_selected, fp_date_selected, fp_time_selected and fp_form_submit. They are only suggestions and nothing is sent until you type a name.

Event Sent when
First Engagement The customer first fills in or picks something on the form
Service selected The customer chooses a service
Date selected The customer chooses a date
Time selected The customer chooses a time
Form submission The booking is sent and accepted

Google Analytics

Boxes are labelled Custom event name. The event is sent with gtag, so the page needs Google Analytics loaded. The page warns: "These events will not work on Google Analytics loaded via Google Tag Manager!"

Google Tag Manager

Boxes are labelled Custom event trigger name. Formpiece pushes the name onto the page's data layer as an event. Each name needs a matching trigger in your container:

  1. In your container, go to Triggers, click New and choose Custom Event.
  2. Enter the same name you typed here as the Event name.
  3. Go to Tags, open the tag that should fire, and add the trigger to it.

Some tags need more configuration before a trigger fires them.

Meta pixel

Boxes are labelled Custom event name. The event is sent as a custom event with fbq, so the Meta pixel has to be loaded on the page.

When it goes wrong

No events arrive

  • The tool is not loaded on the page that holds the form.
  • The name box is empty, or the account is on the Free plan.
  • Google Analytics is loaded through Tag Manager. Use the Tag Manager boxes instead.
  • Google Tag Manager has no trigger with the same name as the event.

I saved but nothing changed on the live form

Saving publishes the form. If the page says the form could not be published, use Publish again at the top of the form page.