subscribed_newsletter

Someone signed up for a mailing list.

Banner-exempt: the sign-up is an explicit action with its own lawful basis, so the SDK sends it before analytics consent, without an anonymous id. The address becomes an identifier and a claimed edge to the device; the double opt-in click (confirmed_subscription) verifies it. The consent itself is a separate granted_consent from the system that holds the form text. From v2 a platform key may send it too: the CRM's sign-up forms record a sign-up from the server, with the anonymous id the widget read from the SDK when the visitor had given analytics consent.

Sent with	browser, server, platform keys (see write keys)
Mode	strict: exactly the declared fields; an undeclared key, a wrong type or a missing required key quarantines the event
Version	2 (_schema_version on the stored row)
State	active
Required fields	none
Revenue	none: the revenue block is refused
Identity evidence	device ↔ email, strength 20, claimed device ↔ phone, strength 20, claimed
Before consent	yes: the browser SDK may send it before analytics consent, without an anonymous id

Fields

The activity's own fields, sent as features. Identifier and attribute fields are moved out of features by the processor; see identifiers and attributes.

Field	Type	Required	What happens to it	Meaning
email	string	no	becomes the email identifier; it leaves features	An email address; it becomes an identifier and leaves features.
list	string	no, may be null	stays in features	The mailing list the message or the subscription concerns.
phone	string	no	becomes the phone identifier; it leaves features	A phone number; it becomes an identifier and leaves features.

Example

One activity in a batch to POST /v1/activities, with debug so the answer says what the processor made of it. The envelope page explains every top-level field.

{
  "batch": [
    {
      "activity_id": "0192f1a4-22a7-731b-8000-22a731be0000",
      "activity": "subscribed_newsletter",
      "ts": "2026-10-17T20:00:00+02:00",
      "anonymous_customer_id": "evx_web_8f21c0",
      "features": {
        "email": "ana@example.com",
        "list": "summer-fest-2027",
        "phone": "+31624681357"
      }
    }
  ],
  "debug": true
}

Try it

Sends this request from your browser. The key and the endpoint are kept in this browser only.

ServiceWrite key

POST /v1/activities{ "batch": [ { "activity_id": "0192f1a4-22a7-731b-8000-22a731be0000", "activity": "subscribed_newsletter", "ts": "2026-10-17T20:00:00+02:00", "anonymous_customer_id": "evx_web_8f21c0", "features": { "email": "ana@example.com", "list": "summer-fest-2027", "phone": "+31624681357" } } ], "debug": true }

Versions

Version	Mode	Key classes	Change
1	strict	browser, server	first version
2 (current)	strict	browser, server, platform	same fields; key classes changed

A published version never changes; a change is a new version, and every stored row says which version it was checked against.