Contact Form 7 can submit attribution fields that no longer describe a visitor’s latest ad click. ClickTrail’s fix is to resolve the current attribution from the cookie at submission time, instead of trusting a hidden field that Contact Form 7 rendered earlier on the page.
The stale-field problem
Contact Form 7 renders its hidden fields on the server. If a visitor lands from one ad, then a newer touch is recorded in the browser before the form is submitted, the HTML field can still contain the older value. A same-page visit from a new ad could therefore save the previous campaign with the form entry.
Read the current touch when the form arrives
At submission, ClickTrail reads the attribution cookie sent with the request and merges that current payload over the posted hidden fields. The posted fields still provide a fallback for information the cookie does not contain, but the cookie’s current values take precedence when both sources provide the same attribution field.
For a returning visitor, the practical sequence is: first visit from Google, later visit from Meta, then a Contact Form 7 submission on the second page. The saved attribution should reflect the newest touch and its click ID, while first-touch fields remain available as a separate history.
What the project tested
The ClickTrail 1.10.5 changelog records a local end-to-end run of that Google-then-Meta scenario. Before the change, the form entry retained Google and omitted the Meta click ID; after it, the entry carried the Meta last touch, fbclid and the selected click ID. The changelog also records that Contact Form 7 conversions are recorded only after a successful mail submission, excluding aborted and failed sends.
This is implementation evidence from a local test run, not a claim about conversion lift or proof that a third-party ad platform accepted an event. The source change is documented in the ClickTrail repository.
Consent still controls collection
When consent is required, ClickTrail is configured to wait for the visitor’s decision before storing attribution. Withdrawal clears ClickTrail’s storage and removes values the plugin filled in forms and decorated links. That behavior depends on selecting and testing the correct consent source and mode for the site; installing the plugin alone does not establish legal compliance.
Where this fits
This behavior solves a specific WordPress form-integrity problem: keeping a lead’s submitted attribution aligned with the current touch. It does not identify a person across devices or decide which advertising channel deserves revenue. See FunnelSheet and ClickTrail.