The connectors report 28 events. Most are recognised without configuration; a few are switched on with an attribute, for want of a reliable generic shape. This page says which, and why.
Recognised without configuration
- The checkout funnel:
view_content,add_to_cart,remove_from_cart,view_cart,initiate_checkout,add_shipping_info,add_payment_info,purchase,refund,customize_product. - Content:
view_contenton an article or a page,view_item_liston a list (blog, category, results),select_itemon the entry opened,searchon your internal search results page. - Leads:
leadon any POST form asking for an email address. Search, sign-in and comments are excluded by their role; a GET form by its method. - Form plugins: Contact Form 7, WPForms, Gravity Forms, Elementor and Ninja Forms are recognised and the event fires on success, not on submit: a form rejected in validation did not produce a lead.
- The newsletter:
subscribeon Mailchimp for WordPress, Brevo, Newsletter and MailPoet, plus the generic shape: an email field and nothing else to fill in. - Direct contact:
contacton amailto:ortel:click. The address itself is not transmitted. - Bookings, shares, trials:
scheduleon a Calendly, Cal.com, SavvyCal, HubSpot Meetings, Zcal, TidyCal or YouCanBook.me link;shareon standard social share URLs;start_trialon a free-trial link or form. - Applications:
submit_applicationon a form asking for a file and an address. A file field alone is an avatar or a support attachment, not an application. - Sign-in:
login, sent from the WordPress server. It is the one conversion the browser cannot witness honestly: it leaves the form before knowing whether the password was right.
Switched on with an attribute
Two events have no reliable generic shape. Guessing would have produced a donation on every click of a button with a similar label, so they are switched on by setting an attribute, once, on the element concerned.
<a href="/donate" data-df-donate>Donate</a>
<a href="/stores" data-df-find-location>Find a store</a>Forcing or preventing detection
Automatic detection rarely gets it wrong, but your site is yours. These attributes have the last word:
| Attribute | Effect |
|---|---|
data-df-lead | Treat this form as a lead, even if it asks for no address. |
data-df-no-lead | Never make it a lead. For an internal or test form. |
data-df-subscribe | Treat this form as a newsletter sign-up. |
data-df-register | Treat this form as an account creation. |
data-df-application | Treat this form as an application. |
data-df-contact | Count a contact on an element that is not a mailto: link. |
data-df-schedule | Count a booking on a tool we do not recognise. |
data-df-share | Count a share on a home-made button. |
data-df-trial | Count a trial start. |
data-df-wishlist | Count a wishlist add on a plugin we do not recognise. |
What is not measured
- Not Google queries.
searchonly reports searches run in your site's own search engine. - No personal data in the clear. A search term containing an address or a number is replaced by a redaction before anything is stored, and identifiers are hashed before leaving.
- Nothing without consent. Every event carries the state your banner decided; going through the server bypasses nothing.
Not every destination accepts everything
Each platform's vocabulary is closed, except Microsoft's. An event with no official equivalent is not sent to that destination: it goes to the others, without error. Each destination page publishes its exact mapping: TikTok, Pinterest, Microsoft Advertising.
Updated: September 1, 2026