Short answers to the questions people ask most about SmartDingo Form Tracker. Each one links
out to a full guide if you need more detail.

Does it work with my form plugin?

It depends on the plugin. Capture is reliable for these form plugins, because SmartDingo
listens for their AJAX “submission succeeded” events: Contact Form 7, Gravity Forms, WPForms,
Fluent Forms, Elementor Pro, WS Form, Formidable Forms, Ninja Forms.

Other or unknown form plugins — and any form that submits with a full-page reload or redirects to
a “thank you” page — are handled on a best-effort basis and may not capture every submission.
SmartDingo does not replace your form plugin; it runs alongside it. See
Supported form plugins.

Note Auto-fill of tracking data into your fields works regardless of the form plugin — it’s
only lead capture that depends on the plugin firing a recognisable success event.

Will it slow my site down?

No meaningfully. The front end is a single lightweight JavaScript file (sdft-tracker.js) that
reads/writes a little browser storage and fills your mapped fields. There is no external call on
page load — lead submission only happens after a visitor submits a form, and it goes to your own
site’s admin-ajax.php.

Is it GDPR-compliant? What data do you store, and where?

Tracking data (UTM parameters, referrer, landing page, device type, etc.) is stored in the
visitor’s own browser. On paid plans, when a mapped form is submitted, that data plus the
submitted form values is saved as a lead in your own WordPress database — nothing is sent to
SmartDingo.

Because a lead links visitor data to a real person’s contact details, it is personal data.
SmartDingo gives you consent modes (Off / WP Consent API / Manual), lead retention/auto-delete
(Starter), and deletion tools to help you stay compliant. Configuring this correctly is your
responsibility — see GDPR & consent.

Where are leads stored?

In a dedicated table in your WordPress database: {prefix}sdft_leads (for a standard install
that’s wp_sdft_leads). Leads never leave your server unless you export them yourself.

Can I export leads?

Yes. From SmartDingo Form Tracker → Leads, use Export CSV to download your leads — the
export respects the filters you have applied. CSV export is a paid feature (Starter). See
Exporting.

Note Lead export (CSV) is separate from settings export/import (JSON) on the Tools page.
The JSON export backs up your configuration, not your leads.

Does it work with caching (LiteSpeed, WP Rocket, Cloudflare)?

Yes. The one gotcha is the lead-submission security token, which is only valid for 5 minutes and
would otherwise be frozen inside cached HTML. To avoid that, the tracker fetches a fresh token
from admin-ajax.php right before each submission (admin-ajax is never full-page cached).

For this to work, visitors must be served the current tracker script, so always purge every
cache (page cache, CDN, browser) after installing or updating — then confirm the page loads
sdft-tracker.js?ver=<current version>. See
Before you go live and
Troubleshooting.

What’s the difference between Free, Starter and Pro?

The free plan does full UTM/visitor tracking and auto-fill. Paid plans add lead capture, the Leads
page and dashboard, CSV export, and higher limits.

For the full matrix and how to activate a plan, see
Licenses & plans.

Can I track more than one form, or multiple forms on one page?

Yes. You create one configuration per form, each with its own CSS-selector mappings. Your plan
sets how many configurations you can have (1 / 5 / 25). Give each form its own configuration and
distinct selectors — if two forms on a page share a selector, only one gets filled reliably. See
Field mapping & auto-fill.

Why don’t I see leads from all my forms?

SmartDingo only captures a submission when the form contains a mapped selector from one of your
configurations. A form with no configuration pointing at it — or whose mapped selector doesn’t
exist on the page — is simply not tracked.

If a form should be logging leads but isn’t, confirm it has a configuration whose selectors match a
field on that form (for example a hidden utm_source input), and check it’s one of the supported
AJAX plugins. See Capturing leads and
Troubleshooting.

Does it capture the actual form field values?

Yes. When a mapped form is submitted, SmartDingo records the contact details it can detect —
email, name and phone, matched by field type and name — plus every named field in the form for
extra context, alongside all the stored tracking data. That gives each lead both who submitted and
where they came from.

GDPR Because SmartDingo captures all named fields, a lead can include whatever a visitor
typed into the form. Keep that in mind for retention and for any sensitive fields — see
GDPR & consent.

Next steps

• Troubleshooting
• Supported form plugins
• Managing leads
• GDPR & consent