> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fuseai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Engagement on contacts

> The Fuse engagement fields written onto each person in Attio, HubSpot, Zoho and Pipedrive, covering opened, clicked, replied and bounced, so you can filter your CRM by who is responding.

Knowing an email was sent is useful. Knowing whether the person **opened it, clicked it or replied** is what tells you who to follow up with.

Fuse writes that straight onto the contact record, so you can filter and build views on it in your CRM.

<Note>
  This is available on **Attio**, **HubSpot**, **Zoho** and **Pipedrive**. It is not available on Salesforce.
</Note>

## The fields Fuse creates

| Field | What it holds |
| - | - |
| **Fuse engagement** | Opened, Clicked, Replied, Bounced, in any combination |
| **Fuse last engaged at** | When they last engaged: the latest first open, click, reply or bounce in any campaign. Repeat clicks in the same campaign do not move it. On Pipedrive it holds the date only. |
| **Fuse last campaign** | The campaign they last engaged with |

Fuse creates these fields itself the first time engagement sync runs, so there is nothing to set up. On Zoho they are named **Fuse Engagement**, **Fuse Last Engaged At** and **Fuse Last Campaign**. They are named distinctly enough that they will not collide with your own attributes, and Fuse only ever writes to these three.

## Availability

| CRM | Where the fields live | Status |
| - | - | - |
| Attio | Attributes on the Person | Available |
| HubSpot | Properties on the Contact | Available |
| Zoho | Custom fields on Contacts | Available |
| Pipedrive | Custom fields on the Person | Available |
| Salesforce | | Not available |

<Warning>
  A few limits apply:

  * **Zoho** writes engagement to the Contacts module only, so people pushed as Leads get no engagement fields. Zoho Standard edition allows only 10 custom fields per module.
  * **HubSpot** portals connected before Fuse asked for permission to create contact properties need to reconnect once.
  * **Salesforce** is not supported yet.
</Warning>

## The whole picture, not per campaign

These fields describe the **person**, not a single campaign. Someone in three campaigns gets one combined view: if they opened one and clicked another, they show both **Opened** and **Clicked**.

**Fuse last engaged at** and **Fuse last campaign** always refer to their most recent engagement across everything.

This is deliberate. Your CRM holds one record per person, and the question a salesperson asks is "has this person engaged?", not "what did they do in campaign four?". For per-campaign detail, use the campaign report in Fuse.

## Always current

Unlike sent emails, these fields are **kept up to date**. When someone who had opened later clicks, their record is updated to show both. The fields always reflect where that person stands today.

## What it needs

Engagement sync is on by default. It does need **Push contact records** enabled, under **Settings → Integrations → *your CRM*** on the **Sync** tab, because engagement is written onto contact records. While contact pushing is off, engagement is held back, and it catches up once you turn it on.

## A note on opens

**Opened** only appears for campaigns with open tracking turned on, which is off by default. Open tracking uses a tracking pixel, and some email clients and security scanners load that pixel automatically before a person has read anything, so **Opened** is a softer signal than the others.

**Clicked** and **Replied** are far stronger indicators of genuine interest. If you are building a follow-up list, prefer those.

## Timing

Engagement sync runs every hour, alongside activity sync, so a click usually appears on the contact within the hour.

The first run backfills everyone who has engaged historically, which can take a few passes on a large account.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.