There are three main sources of information regarding user interactions with gates and forms:
Submission numbers in your Marketing Automation Platform
Analytics collated within Formulayt Insights reports
Tracking events raised via the Formulayt Event Manager to your own tracking platforms (e.g. Google Tag Manager, Google Analytics, Adobe Tag Manager, Tealium, Adobe Analytics etc.)
Numbers between these different sources don't always match exactly. This article explains common discrepancies and how to resolve them.
When MAP submission numbers are higher than Formulayt
If your Marketing Automation Platform shows more submissions than Formulayt or your tracking platform, this may be due to:
Content gates with gating behaviors that open on page load can create blind submissions that count in your MAP but not as user submissions in Formulayt
Formulayt respects no-track directives and opt-in tools like OneTrust, which may prevent tracking despite form interactions
On-page script errors from your website can interfere with Formulayt tracking
Network errors or timeouts can occasionally prevent tracking data from reaching its destination
When Formulayt submissions are higher than MAP numbers
This indicates a potentially serious problem that needs urgent investigation, as it could mean data loss. Before contacting support, check for:
Field validation rules on your MAP form rejecting incoming submissions (the most common cause - 95% of cases)
Incorrectly configured anti-spam features
Ad-blockers interfering with submissions
Other submission issues outlined in our troubleshooting documentation
If none of these resolves the issue, contact Formulayt support with your gate ID, affected page URLs, and details of the discrepant numbers.
Understanding minor discrepancies
Small variations between platforms are normal and generally acceptable. Analytics platforms often use different modeling methods that can produce slightly different numbers.
The exception is when Formulayt shows higher submission numbers than your MAP, which could indicate data loss as detailed above.