Leadbox & Leadform Event Tracking

Overview

Leadbox and Leadform events are tracked by Leadferno. We push these events to Google Analytics 4 (GA4).

These events can be sent to your Google Analytics account. Both Universal Analytics (UA), i.e., codes that start with UA-, and Google Analytics 4 (GA4), via Measurement IDs, are supported. UA event tracking follows Google Analytics' anatomy of events: each event has a category, action, and label. For GA4 there is more detail sent with each event, including page location, session id, and engagement time.

Leadform events mirror Leadbox events. The only difference is the name: an event that fires as leadbox_button for a Leadbox fires as leadform_button for a Leadform, a UA event category of leadbox-{id} becomes leadform-{id}, and so on.

Leadform difference

A Leadform is embedded inline on your page, so it has no "impression", "open", or "close" state. For events sent to GA4, Leadform does not send impression, open, or close events — only the lead, button, channel, form‑field, and search events described below.

Connect Google Analytics (GA4)

Create an API Secret in GA4

1. Sign in to analytics.google.com. Create or open a GA4 account. 

2. Under Admin (gear icon) > Property > Data Streams select the appropriate website where the Leadbox is installed. Web stream details will open.

3. Copy the Measurement ID from the upper-right side of the modal to add to Leadferno.

4. Open the section Measurement Protocol API secrets. A modal will open from the side of the screen.

5. Select Create to add an API secret. Give it a nickname such as Leadbox so you understand where the secret is shared.

6. Copy the secret value for adding to Leadferno.

Add GA4 in Leadferno

1. Sign in to app.leadferno.com. The app defaults to the Inbox.

2. As an owner or admin, go to the account menu, upper-right with the user initials and select Integrations. The integrations screen will open.

3. Select Connect under Google Analytics. A dialog will appear with a text box to enter your Google Analytics 4 Measurement ID and  API Secret.

4. Enter your Google Measurement ID and API Secret obtain from Create section above. Note we store and transmit the API secret securely. Once inputed, you cannot copy the API secret from Leadferno, but it can be changed but submitting a new value.  

5. Select Save. The dialog will close and the Google Analytics integration card will be labeled Connected.

Add Universal Analytics to Leadbox

Universal Analytics no longer accepts new events. For anyone still reading historical reports, the UA anatomy of events is kept below; setup instructions have been removed. Google Analytics shows as connected if either a UA analytics code or a GA4 Measurement ID and API secret have been added.

Google Analytics will display connected if either a UA analytics code has been added or if a GA4 measurement ID and API secret have been added. 

Anatomy of Events

GA4 Events

GA4 events are considerably more flexible. We follow similar paradigms to the events sent to Universal Analytics, but instead of category / action / label we use more descriptive event names, and the Leadbox or Leadform detail becomes a parameter on each event. Where GA4 has a suitable default event — clicks, form submissions, searches, file downloads — we use it.

For Leadform, every event name below is the same with leadform substituted for leadbox:

Event Names

Event names will include the following event parameters are included with your event. In some cases, we take advantage of new default parameters including click events, form submissions, and searches. 

 Custom Leadform fields

A Leadform can collect custom questions beyond name, email, phone, and message. Custom questions are reported with the field type and their position in the form, using the naming {field_type}-{order}. These values appear in the form_field parameter of leadform_form events, and in form_field_error when a custom question fails validation.

Examples: name-1, email-2, phone-3, date-4, address-5, short_text-6, long_text-7, single_select-8, multi_select-9

UA Events

While Google has stopped accepting events to UA properties, we'll keep the events listed here for historical purposes.

Categories are Leadboxes. For a single profile Leadbox, the category appears as leadbox-{{leadbox-id}}. The leadbox-id looks like 87c56f71-3051-45be-973f-f7b49149eabd (this id for the Leadbox appearing on this site) and corresponds to the id in the embed code. For a multi-profile Leadbox, the category appears as leadbox-multiprofile-{{leadbox-id}}.

Actions are Leadbox behaviors some of which are automatic while others are user actions. 

• leadbox: impressions, leadbox closes, and form submits

• buttons: button clicks except for channel buttons

• channels: button clicks on channel buttons (phone & custom)

• form-field: successful entries in the text form

• form-field-error: errors in the text form 

• link: footer links to Leadferno and our terms of service

Labels describe the event actions above. For example, the specific button event could be labeled primary-cta is the first button of the Leadbox that loads on your site. 

Action: Leadbox

When the label name explicitly includes "impression", the event is a page load or a load of the button. 

Action: Buttons

The button actions are click events. The label describes the button being selected.

Action: Channels

The button actions are click events. The label describes the button being selected. Note that when creating a phone channel, you have the option to include any call tracking code, if you're using a call tracking provider.

Actions: Form Field & Errors

The Leadbox has a form to collect form field information, including any validation errors. 

Actions: Links

The are two links at the bottom of the leadbox that include the privacy policy and link to Leadferno. We do this so site visitors, if desired, can review our policies and terms.