Bug Fix

Website pixel now captures forms that randomize their field names

Some website platforms — Real Estate Webmasters (REW) sites among them —
deliberately give their lead form fields randomized name attributes as spam
protection. The pixel previously identified a field by its name attribute
first, and only looked at other clues (input type, placeholder, label) when
the name was completely missing. On these sites the name was present but
meaningless, so the pixel couldn’t tell which field held the email — and
either skipped the submission entirely or captured a contact with just an
email address, leaving the name and phone blank.

The pixel now falls back to the field’s id, type, autocomplete attribute,
placeholder, and label whenever the name attribute isn’t recognizable, and the
server accepts those resolved fields the same way. Submissions from these
sites now create complete contacts with first name, last name, email, and
phone.

The capture is also now sent in a way that survives the page navigating to a
thank-you page — previously a submission fired in the same instant the browser
left the page could be lost in transit, which is why some submissions vanished
without ever reaching Sure Send.

What you may notice

  • New leads from websites with randomized form fields arrive as full contacts
    instead of email-only records.
  • Submissions on forms that redirect to a thank-you page are no longer lost.
  • Submissions that previously vanished without a trace are now captured. If a
    form genuinely has no email in it, the failed capture is recorded and shown
    in a new “Form Submissions Not Captured” section on the pixel settings page,
    so it can be diagnosed instead of disappearing silently.