> For the complete documentation index, see [llms.txt](https://helpdocs.yoxel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.yoxel.com/yoxel-sync/org-level-sync-reporting-and-unmatched-activity-intelligence.md).

# Org-Level Sync Reporting & Unmatched Activity Intelligence

### Overview

***

Yoxel Sync provides Salesforce Admins and SalesOps leaders with cross-user, org-wide visibility into captured engagement data. Rather than allowing unlinked interactions or skipped sync events to drop off the radar, Yoxel centralizes these signals - turning potential data blind spots into actionable data hygiene insights.

### Why Org-Level Reporting Belongs in SalesOps & Admin Hands

***

Activity tracking isn't just a individual rep concern - it is an operational data integrity issue. Giving SalesOps and Admins org-level visibility enables team leads to:

* **Audit CRM Health:** Identify revenue risks caused by missing records or unlogged engagement without relying on rep self-reporting.
* **Fix Systemic Sync Issues:** Spot recurring domain typos, missing secondary emails, and outdated contacts across entire teams.
* **Refine Sync Exclusions:** Monitor how sync exclusion rules (e.g., internal domains or sensitive deals) are executing in real time to verify that only intended activities are being skipped.
* **Ensure Pipeline Accuracy:** Validate that pipeline reviews reflect true buyer engagement rather than missing data.

### Key Reports & Operational Value

***

* **Missing CRM Contacts:** Highlights emails and meetings involving individuals who do not exist in Salesforce.
  * *Ops Value:* Instantly spot missing prospect records and accelerate account expansion.
* **Past Meetings & Follow-Up Tracking:** Reviews completed calendar events to verify if post-meeting follow-ups were sent and logged.
  * *Ops Value:* Ensures SLAs for key prospect meetings are met.
* **Unmatched (Orphaned) Activities:** Centralizes emails, calls, and meetings captured by Yoxel that failed to link to an Account, Lead, or Contact.
  * *Ops Value:* Captures interactions trapped in "digital no-man's land" due to typos, secondary emails, domain changes, or exclusion rules.

### Where to Find Org-Level Reports

***

1. Log into Salesforce as a **Yoxel Admin** or **SalesOps Admin**.
2. Navigate to the **Yoxel Manager** tab.
3. Select **Sync Reporting** from the top navigation bar.

<figure><img src="https://2347016775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpfahWVY94WP1EHugi6X6%2Fuploads%2FMkyK9ExhoW5XOqYSOGAf%2FMonosnap%20yoxel__Yoxel%20Manager%20%7C%20Salesforce%202026-08-20%2016-24-14.png?alt=media&amp;token=7df838ab-4b1f-4584-8f8c-9c14934d2c83" alt=""><figcaption></figcaption></figure>

### Core Report Configurations & Recommended Filters

***

Org-level reporting can help admins investigate activity that was captured by Yoxel Sync but was not successfully linked to Salesforce records.

**1. Unsynced Activities / Events**

**Primary Purpose:** Identify emails and meetings that could not be linked to a Salesforce Contact, Lead, or Account.

Review these activities to identify potential CRM data gaps, such as:

* New contacts who have not yet been added to Salesforce.
* Secondary or personal email addresses that are not stored on the Salesforce record.
* Typos or differences between the email address in Salesforce and the address used in the interaction.
* Outdated contact records, including contacts who have changed jobs or domains.
* Activities affected by sync exclusion rules.

**Recommended Review:**

When reviewing unsynced activities, check:

* Who the activity was with.
* Whether the person already exists in Salesforce.
* Whether the email address matches an existing Salesforce record.
* Whether the activity was excluded by a sync rule and, if so, why.

**Actionable Step:** Create or update the relevant Salesforce record when appropriate. Once the underlying issue is resolved, previously unmatched activities can be linked to the correct record to restore the engagement history.

<figure><img src="https://2347016775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpfahWVY94WP1EHugi6X6%2Fuploads%2FAk7au5KRJ4cGmIkGDd9w%2FMonosnap%20yoxel__Yoxel%20Manager%20%7C%20Salesforce%202026-08-20%2016-48-10.png?alt=media&amp;token=1ea1334f-e898-4a5d-9cb4-4404e4d28341" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2347016775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpfahWVY94WP1EHugi6X6%2Fuploads%2FSb5CZ07lnidBjNO0KBtK%2Fimage.png?alt=media&amp;token=4620caa9-ec0d-4f82-99f1-298465ac850e" alt=""><figcaption></figcaption></figure>

**2. Past Events**

**Primary Purpose:** Review completed meetings and identify potential gaps in post-meeting activity.

Past events can help SalesOps and admins verify whether important customer or prospect meetings were followed by the expected activity, such as a follow-up email.

**Recommended Review:**

Use the report to review:

* Recently completed customer and prospect meetings.
* Meetings that may require follow-up.
* Whether follow-up activity was sent and logged in Salesforce.

**Actionable Step:** Follow up with the responsible rep when a meeting appears to require follow-up or when the expected activity is missing from Salesforce.

**What to Look For**

When reviewing org-level reports, focus on patterns that may indicate broader CRM or sync issues:

* Multiple activities involving people who are not present in Salesforce.
* Repeated unmatched activity for the same person.
* Activities involving outdated or incorrect email addresses.
* Activities consistently excluded by the same sync rule.
* Meetings followed by missing or unlogged follow-up activity.

These patterns can help Salesforce Admins and SalesOps teams distinguish individual data gaps from recurring sync or CRM data-quality issues.

<figure><img src="https://2347016775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpfahWVY94WP1EHugi6X6%2Fuploads%2FJ41jLlMwbLr0rnzk3U2O%2Fimage.png?alt=media&amp;token=57e515c6-d11f-42dc-9028-2051ce97a627" alt=""><figcaption></figcaption></figure>