Missivia follows a prospect from their first interaction until they become a customer, and beyond.
Native and business events set off nurturing sequences, journeys, campaigns and service messages, with scoring, conditions, delays and conversion goals.
Every message honours consent per purpose and an authorisation computed server-side; e-mail is the first channel, others will follow.
It starts with what happens — an event —, turns it into a reaction, decides who may do what with it, composes the message, proves the consent, plugs in your tools, and delivers. The detail — the grammar of events and journeys, the authorisation matrix, data classes, API conventions — lives on its own page.
Native events — open, click, bounce, unsubscribe, entry into a segment — and business events posted by your tools with their payload set off what comes next: nurturing sequences, branching journeys, campaigns, service messages. Conditions, delays, de-duplication, waits for an event, A/B tests, and conversion goals that end the journey the moment the order is placed or the appointment booked.
See the detailAn organisation, its spaces, its roles and its API keys compose into a single authorisation, computed by the server on every call. Rights are inherited from the role, added to by named permissions, and capped by the class of the key. A resource belonging to another space is not found, never forbidden.
See the detailA template editor with no code execution, reusable fragments frozen into every sent version, a live preview. Content that reads the latest event of each type, so you write from what just happened. The import of an HTML kit delivered by an agency, a file library inside the perimeter, and unsubscribe and preference pages in your own branding.
See the detailA prospect comes in with their proof of consent: a register of acts per purpose that keeps the exact wording presented, the date, the source and the address of the form. Two tracking pixels kept under two distinct regimes. Sensitive attributes encrypted outside the record and readable on a named permission. An append-only audit log, retention periods, irreversible anonymisation and a reversibility export.
See the detailA contract published before the code: opaque identifiers, cursor pagination, idempotent creations, standard errors. This is where your tools post their events and read back what happens: signed webhooks, an event log, exports with no personal data. A sandbox where nothing leaves, and a path to production made of artefacts, with no manual operation.
See the detailThe first channel open, e-mail is delivered by the platform itself: messages are handed directly to the recipients’ mail servers, from its own IP addresses. Sending domains verified with SPF, DKIM and DMARC, per-IP warm-up, bounce and complaint handling, automatic pause when a space’s thresholds are crossed.
See the detailNothing starts from an intention: everything starts from a fact. Here is what happens between the event and the inbox.
Native — an open, a click, a bounce, an entry into a segment — or business, posted by your tools with its payload: “order placed”, “appointment booked”.
A condition on the payload and on the record, a delay from zero to thirty days, an explicit de-duplication rule: every time, once only, or at most once per period.
Every decision — fired, skipped with its reason, executed — is written to the contact’s log.
Relative or dated waits, waits for an event, conditions, switches, weighted splits, A/B tests.
Any step that depends on an open or a click has three outcomes, never two: did it, did not do it in time, cannot be measured. As soon as the conversion goal is reached, the enrolment ends, wherever it stands.
Consent for the purpose is checked at render time, the authorisation is computed server-side, and delivery goes through the first channel open: e-mail, handed straight to the recipient’s mail server.
Five elements compose the authorisation — and the interface making the call decides none of them.
Derived from the token. The call cannot name another one.
A set of capabilities inherited as a whole, not a checkbox per screen.
Cumulative, granted to a designated person, and logged.
It caps the whole: what it cannot reach, no role gives back.
A single matrix decides, and writes its decision — refusals included.
A resource belonging to another space is not found, never forbidden: the existence of an access to people is not observable from the outside.
An attribute’s class decides, server-side, where the value is written, who may read it back and what is logged about it. A sensitive value is never a merge variable: the message is differentiated by choosing the journey.
Missivia is the engagement platform behind Dataventure Group’s lead-collection tools, opened to partners as a multi-space platform. Each space gets its own keys, domains, quotas and roles. E-mail is the channel served today; the platform is built to take on others, with the same consent register and the same authorisation.