How to Fix lead generation tracking with Jetpack and GTM

If you have ever run into a problem in conversion tracking where your setup works perfectly during testing but breaks the moment your campaign goes live, you are not alone.

May businesses experienced this exact scenario while setting up Meta Lead Generation campaigns. Before starting the campaign, the form submissions test was successful, and everything was reading perfectly in the Meta Events Manager’s Test Events tool for the dataset. However, shortly after launching the live campaign, it mysteriously stopped tracking the leads.

If you are dealing with dropped leads or unrecorded conversions on Jetpack forms, here is why it happens and the exact steps that we took to slove it for an institution in the Education Sector in Laval.

The Problem: Dynamic Form IDs

When setting up a form submission trigger in Google Tag Manager (GTM), the standard approach is to fire the tag based on the Form ID. Initially, our trigger was configured to fire when the Form ID contained a specific, long string of characters, such as jp-form-fcebc79d1a57aeb39b89b81578758f1f450e5a59. 

The issue is that Jetpack contact forms generate dynamic, randomized alphanumeric strings at the end of their form IDs. While the ID matched perfectly during our initial tests in the Meta Test Events tool, it regenerated for subsequent real-user submissions on the live page. Because our trigger was set to look for that exact original string, GTM could not match the condition, and the tag failed to fire.

The Solution: Adjusting the Match Type

Instead of targeting the full string, the fix requires targeting the static prefix that Jetpack applies to all of its forms.

Here are the exact steps to change this setting in Google Tag Manager:

1. Log in to your Google Tag Manager workspace and navigate to the Triggers menu.
2. Click on your existing form submission trigger (e.g., « Website Form Trigger ») to edit its configuration.
3. Look at the conditions under the « Filters » section where your rules are defined.
4. Locate the condition for Form ID and change the dropdown match type from contains to starts with.
5. In the value field, enter the static prefix: jp-form-.
6. Ensure your other standard conditions (like _event equals gtm.formSubmit) remain intact.
7. Save the trigger and publish your workspace container.

This simple adjustment tells GTM to look for the consistent beginning of the ID while ignoring the randomized characters at the end. Once we made this update, the trigger condition was met consistently, and the Meta tag successfully fired upon every submission.

Setting up a robust tracking infrastructure is crucial for accurate digital advertising. Making small technical adjustments like this ensures your campaign data remains reliable so you can focus on scaling your results.

Read More: Why Local SEO and Google Maps Are the best tools for driving foot traffic?