How to Stop Losing Form Leads on the Way to Your CRM

Mailbox keeping letters dry in the rain
Summarize with AI:

Marketing Source Tracking is a WordPress plugin that records where a visit came from, attaches it to the form submission and passes the data to ASARI CRM, ClickMeeting or User.com. It was built by BeeClear, a developer of WordPress plugins and smartphone apps. This article follows a submission from the “Send” button to your CRM. That is where leads most often vanish – usually unnoticed. The plugin guards that path with a background queue, retries, duplicate checks and an error log.

Why do form leads get lost before they reach the CRM?

Form leads get lost before they reach the CRM because the website and the sales system are joined by a single network request. A maintenance window, an overloaded server or a rate limit on the CRM side is enough to break it. The form still shows its thank-you message, so neither the prospect nor the sales rep knows that anything went wrong. These are the usual weak spots:

  • the CRM stops responding for a few minutes and the only delivery attempt fails,
  • the form waits on the CRM until an impatient visitor closes the tab,
  • a double click creates two records for the same person,
  • the error lands in a server file nobody opens.

Marketing Source Tracking closes each of these gaps with a separate mechanism. The queue decouples the form from the CRM, and retries absorb short outages. Duplicate checks filter out repeats, while the error log keeps a trace even with logging off. Lead source and field mapping have an article of their own.

How does background sending protect a form from CRM outages?

Background sending protects a form from CRM outages because the page never talks to the CRM at the moment of submission. Instead, the plugin stores the payload as a job in a queue. The visitor gets the confirmation at once and never waits for ASARI CRM, ClickMeeting or User.com. The actual API calls run later through WP-Cron, the task scheduler built into WordPress. Even when the CRM is down, the form completes as usual.

Each system is handled independently. A missing User.com API key does not stop the lead from reaching ASARI CRM, and a ClickMeeting error does not block the others. Completed steps are remembered, so a retry never creates the same contact or registration twice. The one exception is a job that cannot be saved – then the visitor is asked to submit again.

When does Marketing Source Tracking retry a failed submission?

Marketing Source Tracking retries a failed submission after a temporary error. It treats a missing server response, a timeout (HTTP 408), a rate limit (429) and any 5xx error as temporary. The intervals are fixed at 5 minutes, one hour and one day. Together with the first try, that gives four attempts spread over more than a day. Here is the schedule for an outage that will not clear:

AttemptWhen it runsWhat happens after a temporary error
firstright after sending, or after the set delaysecond attempt in 5 minutes
second5 minutes after the first failurethird attempt in one hour
thirdone hour after the second failurelast attempt in one day
fourthone day after the third failurejob removed from the queue, error logged

A permanent error, such as a missing API key or data rejected by the API, is not retried. That system is dropped from the job, while the others carry on. The existing-contact lookup in ASARI CRM has its own safeguard. If it fails temporarily, the plugin waits for the next attempt and, on the last one, creates a new contact so the lead survives.

Why delay the first send for a specific form?

Delaying the first send for a specific form helps when another system has to create the contact first. A typical case is an account registration that creates the customer in the CRM by itself. Sent instantly, the submission would find no existing contact and create a duplicate. A short pause lets the plugin update that contact instead.

You set “Delay before the first send” in the mapping of a Contact Form 7 form or a custom form. The value is in seconds, from 0 up to 86,400 – one full day. The default of 0 means the job starts right away. The delay covers the whole submission, including ClickMeeting and User.com. Retries keep their own intervals, and on a low-traffic site WP-Cron may start slightly late.

What does the queue screen show, and when should you use “Retry now”?

The queue screen, “Async jobs” in the Marketing Source Tracking menu, shows every open job. Counters above the table show jobs queued, processing or awaiting a retry. Each row lists the job ID, the source form, the status and an attempt counter such as “2 / 4”. It also shows the next retry time, the last error and the last update. Delivered jobs disappear from the list, so an empty queue is good news.

The “Retry now” button is useful once the cause of an outage is gone. Picture the CRM going down overnight, leaving submissions that will not be retried for another day. In the morning, the button in each row puts that job on the next WP-Cron run. The attempt counter is not reset – a manual retry uses up an attempt. The list is split into pages of 50 jobs, so it still opens after a long outage.

How does the plugin filter out duplicate submissions?

The plugin filters out duplicate submissions on two levels. The first is always on and stops double clicks on the submit button. An identical submission from the same form is not queued a second time for two minutes. The same lock stops two identical submissions from being processed in parallel. If saving the job fails, the lock is released immediately so the visitor can try again.

The second level is the “Duplicate protection” option in the form mapping, and it applies to ASARI CRM. You choose the key: email or phone, email only, or phone only. Email addresses are compared regardless of letter case, and phone numbers by their digits alone. A lead already synced from that form will not be sent to the CRM again. The record of successful syncs stays in the database until the plugin data is cleared.

Where can you find the reason a CRM sync failed?

The reason a CRM sync failed shows up first on the “Logs” screen, as long as logging is enabled. Entries are grouped by form submission or background job. Each expanded group shows every step: building the payload, queuing, the API requests and the retries. You can keep between 10 and 200 log entries, with 50 as the default.

The plugin also keeps a separate record of the last 50 warnings and errors. It is written even when logging is off, so every failure leaves a trace. A job removed after its fourth failed attempt is recorded there too. Email addresses are masked to a form like j***@company.com, and phone numbers keep only the first three and last two characters. Tokens, passwords and API keys become asterisks before saving.

This error log lives in the WordPress database, not on a dashboard screen, so deployment tools can read it without a wp-admin session. Queue encryption and consent-based tracking have a separate article.

How can you check that no submission gets lost?

The quickest way to check that no submission gets lost is a test form. Send a test enquiry, then open “Async jobs” and “Logs”. An empty queue and a complete set of steps in the log mean the path to your CRM is clear. Imagine a campaign peaking just as the CRM goes down for maintenance. The enquiries do not vanish – they wait for the next attempt. Your sales team then finds them in the CRM instead of digging through an inbox.

Marketing Source Tracking protects every enquiry from a CRM outage and never creates the same contact twice. You can try retries, the first-send delay and duplicate protection on your own forms for 3 days. We are also happy to help with your first form mapping.

Summarize with AI:

Want clients and AI models to find your website?

We run website SEO for Google and for AI answers. We tidy structure, internal linking and content, and we measure results instead of promising them.