How to Track Contact Form Submissions with Meta Pixel

To track contact form submissions with Meta Pixel, fire a Lead event after the form confirms a successful submission. Do not attach it only to the submit-button click: invalid fields, spam checks or a delivery failure can stop the enquiry from being accepted.

Use your form plugin's documented success event or its supported tracking integration. For Contact Form 7 in AJAX mode, that event is wpcf7mailsent. If Niwa answers a visitor's questions before they enquire, measure the accepted form outcome rather than treating every chat or button click as a lead.

Define what your lead means

Write a short definition before setting up a tag. For a basic enquiry form, it might be: this specific form completed successfully and its message was sent. A newsletter registration or a support request may need a different event and reporting purpose.

A successfully sent message is not a sale and does not prove the email reached the recipient's inbox. Confirm your actual business process separately.

Inspect your current tracking integration first. If it already records the form's success, do not add a second handler.

Use the success signal your form provides

The Contact Form 7 DOM-event reference distinguishes successful mail sending from invalid, spam and mail-failed results. Its general submit event also covers unsuccessful outcomes.

For an AJAX form, use the form's stable ID to scope your handler. Do not inspect the button's English label or the visitor's message to decide whether it counts. Stable plugin events and IDs work across translated versions of the same form.

Other form plugins have their own documented hooks or integrations. Confirm their success definition instead of copying the Contact Form 7 event into a different plugin.

A scoped Contact Form 7 example

The following JavaScript records Lead for form ID 123. Replace 123 with the intended form's real ID. This assumes your consent-approved Pixel base code has already initialized, and that this code is registered once.

function trackConfirmedEnquiry(event) {
if (Number(event.detail.contactFormId) !== 123) return;
if (typeof window.fbq !== 'function') return;
window.fbq('track', 'Lead');
}
document.addEventListener('wpcf7mailsent', trackConfirmedEnquiry);

Put the handler in your maintained site-code or tag-management setup. The code does not create a Pixel or manage consent itself. Register it only through the advertising-consent-approved path. On withdrawal, your consent integration must stop advertising delivery and remove this listener if it remains active.

The matching removal call is:

document.removeEventListener('wpcf7mailsent', trackConfirmedEnquiry);

If the Pixel was not initialized when submission succeeded, this example skips the event. It deliberately does not store the enquiry for later replay. Investigate a missing permitted event through loader order and consent state.

If you use multiple forms, decide which ones should count as leads and configure their stable IDs explicitly. A translated form with a different ID needs its own assignment. No user-input language detection is necessary.

Respect consent and keep form contents private

For UK visitors, non-essential advertising tracking requires valid consent. The ICO's guidance explains the requirement.

Do not send the enquiry text, email address, phone number or other submitted fields in this event's parameters. Also inspect the page URL and any confirmation URL: sensitive details in URLs can reach tracking systems even when the event has no extra fields.

For sensitive services, review whether advertising tracking is suitable on the enquiry flow at all. A generic event name does not make sensitive underlying data acceptable.

Test failure and success separately

Open a clean permitted test session with the correct Pixel ID. Use Meta's browser diagnostics and Events Manager to inspect the result.

Try an invalid submission first. It should not fire Lead. Where you can safely simulate spam rejection or a mail failure in a test environment, check those too.

Then submit the intended form successfully and confirm one Lead. Submit a different form and confirm it does not use this handler. Finally, revoke advertising consent and check that subsequent submissions do not send advertising events.

Contact Form 7's AJAX guidance explains that these DOM events do not fire in non-AJAX mode. If your form works through a full-page submission, choose that flow's supported success mechanism instead.

Connect the enquiry to a useful next step

Niwa's website assistant can explain products and business information so the visitor arrives at the form with a clearer question. The form and your follow-up process still need to handle the enquiry reliably.

Existing WordPress owners can use the standalone Niwa plugin. Niwa Business is USD 150 for a custom WordPress website or migration, hosting, maintenance and AI tools adapted to the business. Contact Niwa about your enquiry workflow with the form plugin and next step your team currently uses.