Back to Community
Home / Community / General

How to Control HubSpot Leadin Form Tracking and Tagging on Your WordPress Site

17 threads Sep 9, 2025

Content

Many WordPress site administrators using the HubSpot – CRM, Email Marketing, Live Chat, Forms & Analytics plugin (formerly Leadin) need precise control over which forms are tracked and how contacts are tagged. A common challenge is the plugin automatically tracking all forms, including comment sections or login forms, which can clutter your CRM with irrelevant data. This guide explains the core concepts of how the plugin identifies forms and provides the most effective methods for gaining control over your form tracking and contact segmentation.

How HubSpot Leadin Identifies and Tracks Forms

The plugin operates by scanning your web pages for HTML <form> elements. It identifies and distinguishes between different forms primarily through their CSS selectors, which are typically an ID (e.g., #newsletter-form) or a class (e.g., .contact-form) assigned to the form tag. When a form with a unique selector is submitted and contains an email field, the plugin captures that submission and creates a contact.

Common Challenges and Solutions

1. Tracking Unwanted Forms (Comments, Logins, etc.)

The Problem: The plugin may track submissions from forms you don't want to log as leads, such as WordPress comment forms or user login forms.

The Solution: As confirmed in the sample threads, the plugin's development team has historically noted that the ability to toggle specific forms on or off is a highly requested feature. While a native setting for this was not available in earlier versions, the primary workaround is to ensure the forms you do want to track have unique CSS selectors. For forms you do not want to track, ensuring they lack a unique identifier that the plugin would use for tagging can sometimes prevent them from being categorized as lead-generating forms, though they may still be captured.

2. Distinguishing Between Multiple Forms of the Same Type

The Problem: If you have multiple Contact Form 7 or Gravity Forms, they might all appear as a single "Contact Form 7" entry, making it impossible to tag contacts from different forms separately.

The Solution: You must add a unique CSS selector to each form.

  • For Contact Form 7: Modify the form's shortcode to include an html_id attribute. For example: [contact-form-7 id="1234" title="Contact form 1" html_id="newsletter-signup"]. You would then use #newsletter-signup as the selector in HubSpot Leadin.
  • For Other Form Builders: The principle is the same. Consult your form plugin's documentation on how to add a custom ID or class to the <form> element it generates.

3. Auto-Tagging Contacts Based on Specific Forms

The Problem: You want contacts who fill out a "Careers" form to be tagged differently than those who fill out a "Newsletter" form.

The Solution: Once your forms have unique CSS selectors, you can create automated tagging rules within the HubSpot Leadin plugin.

  1. Navigate to Leadin > Contacts in your WordPress admin.
  2. Click on Tags and create a new tag (e.g., "Newsletter Subscriber").
  3. In the tag settings, find the option for "Automatically tag contacts who fill out any of these forms".
  4. In the input field, type the CSS selector for your form (e.g., #newsletter-signup).

Now, any contact submitting that specific form will automatically receive the tag you created. According to user reports, this allows for distinct segmentation without automatically applying a default "Subscriber" tag if that is not desired.

4. Managing Email Notifications for Specific Forms

The Problem: Your sales team receives email notifications for every form submission, but you need to suppress alerts for non-sales forms like job applications.

The Solution: Based on sample thread responses, some versions of the plugin may include a Notifications button for each form within the Leadin interface where this can be configured. If this option is not available in your version, an alternative workaround is to create a specific tag for the form you wish to mute (e.g., "Careers Form") and then set up an email filter in your inbox to archive messages with that tag name in the subject line.

Important Limitations to Be Aware Of

  • Multi-step Forms: The plugin may not reliably capture all data from multi-step forms, especially if the email field is present on the first step. Compatibility is generally best with Gravity Forms multi-step forms where the email is on the final step.
  • Tagging Based on Field Values: The plugin cannot automatically tag a contact based on a specific value selected in a checkbox or dropdown field (e.g., tagging someone as "Canada" if they select that country). Tagging is based solely on which form was submitted.
  • JavaScript-Heavy Forms: Forms that rely extensively on JavaScript for validation or functionality (like some premium form builders) may not be compatible with the plugin's tracking method.

By understanding how the HubSpot – CRM, Email Marketing, Live Chat, Forms & Analytics plugin identifies forms and leveraging unique CSS selectors, you can effectively manage which forms create contacts and how those contacts are organized within your hub.

Related Support Threads Support