[object Object]

A sales rep sends a discovery email Monday morning. By Tuesday, the engagement panel says it was opened nine times across three locations. The rep calls it a hot lead. It was the prospect’s spam filter pre-fetching the tracking pixel three times, then a forward to two colleagues who never read it. Email Engagement is useful, but only if you understand what each event actually represents.

What the Tracking Pixel Sees

Email Engagement injects an invisible 1x1 image and rewrites links to redirect through a Dynamics endpoint. The open event fires when the recipient’s mail client requests the pixel. The click event fires when they hit a tracked link. Both are stored on the email message record and rolled up to the parent contact or lead.

The pixel does not care who the actual human is. Image proxies, mail security scanners, and pre-fetchers all trigger it. Apple Mail Privacy Protection routes the pixel through a relay and pre-fetches it on receive, which means every opened email from an Apple Mail user looks read within seconds of delivery.

The Three Reliable Signals

Reliable:
- Click on a link in a message you wrote yourself
- Reply to the thread (uses headers, not pixels)
- Attachment download from the tracking link

Unreliable:
- First open within 10 seconds of send
- Multiple opens from one geography in a row
- Opens with no click after seven days

Train reps to weight clicks five times more than opens and replies ten times more. Updating the lead score model to reflect this avoids false positives in the daily pipeline call.

Filtering Out the Noise in FetchXML

When you build the Engaged This Week view, exclude opens from known scanner IPs and bound the open count to a sane range.

<fetch>
  <entity name="email">
    <attribute name="subject" />
    <attribute name="opencount" />
    <attribute name="lastopenedtime" />
    <filter>
      <condition attribute="directioncode" operator="eq" value="1" />
      <condition attribute="opencount" operator="gt" value="1" />
      <condition attribute="opencount" operator="lt" value="20" />
      <condition attribute="lastopenedtime" operator="last-x-days" value="7" />
    </filter>
  </entity>
</fetch>

The upper bound of 20 strips obvious scanner activity. The lower bound of 1 ignores the first auto-fetch.

Configuring Per-User Opt-In

Email Engagement is enabled at the org level but each user must opt in through their personal options. A common rollout failure is enabling the feature, training the team, then discovering half the team has not flipped the personal toggle. Push the setting through a personalization preference Power Automate flow on user creation.

const url = `/api/data/v9.2/usersettingscollection(${userId})`;
await fetch(url, {
  method: "PATCH",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({ allowemailcredentials: true })
});

Privacy and Compliance

The tracking pixel is a personal data event under most privacy regimes. Email Engagement supports honoring a per-recipient do not track preference through the marketing optionsetattribute on the contact, and it logs each open with the recipient identifier. If your organization operates in the EU, document the lawful basis in your privacy notice and offer a clear unsubscribe-from-tracking path.

Sales Insights Versus Engagement

Email Engagement is a free Sales feature. The richer who-replied-when, sentiment, and conversation context live in Sales Insights or Conversation Intelligence, which require separate licenses. Do not promise the engagement panel can do sentiment, because it cannot.

What to do this week

Pull last month’s emails with open counts above 20 and tag them as scanner noise in your reporting. Add the FetchXML filter above to your team’s Engaged This Week view, and update the lead scoring model to weight clicks and replies above raw opens.

[object Object]
Share