# Measured events

> The 28 events the connectors report: what is recognised without configuration, what is switched on with an attribute, and what is not measured.

- Original page: https://server-side.datafirefly.com/en/docs/events.html
- Language: en
- Updated: 2026-09-05
- Publisher: DataFirefly (Datafirefly Limited), https://server-side.datafirefly.com/en/

---

What the connector recognises on its own, what you can force, and where the measurement stops.

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_content` on an article or a page, `view_item_list` on a list (blog, category, results), `select_item` on the entry opened, `search` on your internal search results page.
- **Leads**: `lead` on 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**: `subscribe` on Mailchimp for WordPress, Brevo, Newsletter and MailPoet, plus the generic shape: an email field and nothing else to fill in.
- **Direct contact**: `contact` on a `mailto:` or `tel:` click. The address itself is not transmitted.
- **Bookings, shares, trials**: `schedule` on a Calendly, Cal.com, SavvyCal, HubSpot Meetings, Zcal, TidyCal or YouCanBook.me link; `share` on standard social share URLs; `start_trial` on a free-trial link or form.
- **Applications**: `submit_application` on 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.** `search` only 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. Shopify order webhooks are the exception: they carry no consent signal.

## Cookies set by the connector

The connector sets nothing before the visitor consents. After consent, it may set two kinds of cookies, to add to your cookie policy:

- `_dfss_cid`, 90 days: a random number that lets Google Analytics count a visitor's pages as those of one person when Google's cookie is missing. Set only if the visitor accepted advertising and did not refuse audience measurement. Removed as soon as they refuse either.
- `_dfss_gclid`, `_dfss_gbraid`, `_dfss_wbraid`, `_dfss_msclkid`, `_dfss_ttclid`, `_dfss_fbc`, `_dfss_oppref`, 90 days: the identifier of the click on an ad (Google, Microsoft, TikTok, Meta, OpenAI), kept to tie a purchase to the ad that brought it.

## The visitor funnel (Insights page)

This function counts how many of your visitors reach each step of a purchase. It is off by default: switching it on is your decision as the data controller, and only an owner or an administrator of your account can do it, from the Insights page.

We open it site by site. If the “Visitor funnel” card does not appear on your Insights page, write to [support@datafirefly.com](mailto:support@datafirefly.com).

To link the steps of one visit, we use a pseudonymous key. It exists only for visitors who accepted tracking in your banner, it is kept 48 hours at most, and you only ever see numbers.

**Your consent banner** must announce this purpose, for example: “measure site traffic and the purchase journey, as statistics”. Put this sentence in the category that triggers our tracking (usually “marketing” or “analytics”), not in a category the visitor can accept separately.

By switching it on, you confirm this point and you accept the line this function adds to Annex 1 of the [Data Processing Agreement (DPA)](https://server-side.datafirefly.com/en/dpa.html), version 1.1.

**If a visitor asks you for their data or for its erasure**, you can answer that the visit identifier is deleted automatically within 48 hours and that only statistics remain afterwards, which no longer allow the visitor to be recognised.

## 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](https://server-side.datafirefly.com/en/tiktok-events-api-server-side-tracking.html), [Pinterest](https://server-side.datafirefly.com/en/pinterest-conversions-api-server-side-tracking.html), [Microsoft Advertising](https://server-side.datafirefly.com/en/microsoft-ads-conversions-api-server-side-tracking.html).

Updated: November 16, 2026
