Building the Email Delivery & Tracking Layer in NurtureHub

v1.0.47 — Released now

One of the harder infrastructure problems in any email platform is making sure the send path and the measurement path are both reliable, flexible, and don't know too much about each other. v1.0.47 ships the full solution to both problems in NurtureHub.

---

The Problem We Were Solving

Property agents work across a wide ecosystem of CRMs and email providers. Some agencies send from their agentOS or Reapit account. Others are deep into Google Workspace. A growing number run Microsoft 365. Any email platform that locks an agency into a single send path creates immediate friction — and often becomes shelfware.

At the same time, the entire value of NurtureHub's intent scoring and hot lead alerts depends on knowing when a contact opens an email or clicks a link. If that tracking layer is tightly coupled to one delivery provider, you lose data every time an agency switches tools.

The answer to both problems is the same: build delivery and tracking as independent, provider-agnostic layers.

---

How Delivery Works

Every tenant now configures a delivery mode: CRM native, Google Workspace, or Microsoft 365. That choice lives in their tenant configuration and doesn't affect anything else on the platform.

When a sequence step is due to send, it enters a send queue rather than firing immediately. The queue handles scheduling and, crucially, retry logic — if a send fails because of a rate limit or a momentary provider hiccup, the platform retries it automatically. Agents never need to notice or act on transient failures.

A provider-agnostic dispatcher sits between the queue and the actual delivery providers. It reads the tenant's configured mode and routes the send to the right adapter. Adding a new provider in the future is a matter of writing a new adapter — nothing else in the platform needs to change.

---

How Tracking Works

Regardless of which delivery path an email took, tracking works the same way.

When an email is dispatched, it gets a unique tracking token — a compact identifier that ties every subsequent event back to the exact email, contact, and tenant.

Opens are recorded via a server-side 1×1 pixel endpoint. When a mail client loads the image, the platform records the open event and returns a valid transparent GIF. No JavaScript, no client-side code — just a standard image request.

Clicks are recorded through a link proxy. Links in outbound emails are rewritten before sending so that when a recipient clicks, the request hits NurtureHub first, the click is recorded, and the recipient is immediately redirected to where they were going. The whole thing is invisible to the recipient.

Both event types flow into the same engagement event store. That store is what feeds intent scoring and hot lead alerts in real time. Because every delivery path produces identical tracking events, the scoring and alerting logic doesn't need to care how the email was sent.

---

What This Enables

With delivery and tracking infrastructure in place, a number of things that were previously blocked can now move forward:

• Real-time intent scoring has live engagement signal to work with as emails go out and are interacted with.
• Hot lead alerts can fire based on actual open and click events rather than placeholder data.
• Multi-provider support is a first-class capability — agencies can switch their delivery mode without losing historical tracking data or breaking any downstream feature.
• Per-tenant isolation means one agency's configuration never affects another's, which matters at scale.

This release is infrastructure — agents won't see a new UI for most of it — but it's the foundation that everything engagement-related in NurtureHub is built on top of.