> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/~/revisions/CBft97pr7Q1KpU4KFthF/faqs-and-troubleshooting/why-am-i-seeing-more-accounts-in-crm-than-i-synced.md).

# Why Am I Seeing More Accounts in CRM Than I Synced?

When you sync a segment from **Reo.Dev** to your CRM, the total count of accounts or developers at that moment may differ from what you see in your CRM later. This happens because **segments in Reo.Dev are dynamic** and continuously update as new accounts or developers match the segment’s filter criteria.

#### Example Scenario:

1. You create an **Account Segment** in Reo.Dev.
2. At the time of syncing, the segment has **50 accounts**.
3. After 2 days, you check in your CRM and find **80 accounts** under that segment.

#### Why Did This Happen?

* **Dynamic Segments**: Any new accounts or developers that meet the segment filters will **automatically get added** and **synced to your CRM** every 24 hours.
* **Ongoing Syncing**: Reo.Dev syncs data at **a 24-hour interval** to keep your CRM updated.
* **Different Timeframes for Count Calculation** – The **total count in Reo.Dev’s Segments panel reflects only the last 30 days**, while your CRM **displays all-time records**. This difference in timeframes can lead to a higher number in the CRM compared to what you see in Reo.Dev.

***

#### How to Track New Additions:

1. **Segment Overview**:
   1. In Reo.Dev, navigate to **My Segments** and check the **Active Count** column.
   2. Hover over the number to see the **new accounts added in the past 24 hours** (displayed in green).

      <figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FZWTX1g339f0lBxnLw3kP%2Fimage.png?alt=media&amp;token=e0b4286c-12c2-44d3-8da2-b1ceacb3c9c6" alt=""><figcaption></figcaption></figure>

2. **Analytics Dashboard**:
   1. Go to **Resources > Analytics** in the side panel.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FlX7zAkh7jytyk5VppZK0%2Fimage.png?alt=media&amp;token=0a4b0e72-705a-4801-aa5c-25a00115aa73" alt=""><figcaption></figcaption></figure>

&#x20;     b. Click on **Segment Analytics**

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FKSC8xT76tVONsY2Wh5Dl%2Fimage.png?alt=media&amp;token=59c2dcc0-badb-486c-ae34-b0c4d91d01cb" alt=""><figcaption></figcaption></figure>

&#x20;       c.  Scroll down to **Key Segment Metrics**. Find your segment and click **View Monthly Metrics** for a **month-over-month breakdown** of new additions.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FLbg1UGvsuTK9kFFz6xOv%2Fimage.png?alt=media&amp;token=13fd2a2d-132b-4def-9313-111200548020" alt=""><figcaption></figcaption></figure>

***

#### Related Guides:

* [How to Sync a Segment to Salesforce/HubSpot](/~/revisions/CBft97pr7Q1KpU4KFthF/faqs-and-troubleshooting/how-to-sync-a-segment-to-crm.md)
* [How to Configure HubSpot in Reo.Dev](broken://pages/qIlng8yz565Wfi80f2uC)
* [How to Configure Salesforce in Reo.Dev](/~/revisions/CBft97pr7Q1KpU4KFthF/integrations/output-integrations/crm/salesforce.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.reo.dev/~/revisions/CBft97pr7Q1KpU4KFthF/faqs-and-troubleshooting/why-am-i-seeing-more-accounts-in-crm-than-i-synced.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.