> For the complete documentation index, see [llms.txt](https://docs.clearout.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clearout.io/data-pulse/supported-data-sources.md).

# Supported Data Sources

Data Pulse connects to the systems where your contacts live and keeps that data clean automatically. This page explains what a data source is, what Data Pulse does with one once it is connected, and which sources are supported today.

{% hint style="info" %}
New to Data Pulse? Start with the [Overview](/data-pulse/overview.md) to understand the pulsing engine, then come back here to connect your first source.
{% endhint %}

### What is a data source?

A data source is any system that stores your contact records and that Data Pulse can connect to, monitor, and write results back into. In most cases this is your CRM (for example, HubSpot or Salesforce).

When you connect a data source, Data Pulse becomes a live data-quality layer on top of it. It does not replace your CRM and it does not move your data out of it. It listens for new contacts, validates them, and returns the results to the same records.

{% hint style="warning" %}
Write-back is append-only. Data Pulse only adds or updates its own Clearout fields on a contact. Your original CRM values are never changed or removed.
{% endhint %}

### Supported sources at a glance

<table><thead><tr><th width="127">Data source</th><th width="97">Status</th><th width="177">Connection method</th><th width="162">What it monitors</th><th>Setup performed by</th></tr></thead><tbody><tr><td><a href="/pages/CpdjEJvdFSZ8qarMjxIB#how-data-pulse-works">HubSpot</a></td><td>Live</td><td>OAuth</td><td>New contacts</td><td>Any user with HubSpot install permission</td></tr><tr><td><a href="/pages/b1xIoNihr0LYSAjOE8Lr#how-salesforce-two-way-sync-works">Salesforce</a></td><td>Live</td><td>Managed package plus OAuth-connected app</td><td>New leads</td><td>Salesforce administrator (one-time), then any assigned user</td></tr></tbody></table>

{% hint style="info" %}
Want a source that is not listed here? We prioritize the next integration based on customer demand. [Tell us which CRM](https://changelog.clearout.io/?_gl=1*7ajw74*_gcl_au*MjEyMDI0OTQyOC4xNzc4NzU2NTkzLjEzOTA5ODUyODcuMTc4NTE0OTI1NS4xNzg1MTQ5MjU0LjczMjc1MjA4Ni4xNzg1MTI5MDE4LjE3ODUxNDkyNTQ.*_ga*MTY5NTc4NTA3NS4xNzMxOTk3OTQy*_ga_QWRSQT3D41*czE3ODUxMjQwOTMkbzUzMCRnMSR0MTc4NTE1MzYzMSRqNTUkbDAkaDEyMTYzMTU1MTU.) your team runs and we'll move it up the queue.
{% endhint %}

### Fields Data Pulse validates

Across every supported source, Data Pulse currently validates three field types. You choose which ones to enable during setup, and at least one must be selected.

* **Email** - deliverability status, safe-to-send, disposable, role-based, free-domain, and gibberish checks.
* **Phone** - reachability, line type (mobile, fixed, or VoIP), carrier, country, and timezone.&#x20;
* **Name** - normalization plus gibberish and placeholder detection.

For the full list of input and output fields, see Implementation & Setup.

### Fields Data Pulse Updates

Post real-time verification Data Pulse appends its own set of Clearout result properties to your contact records. These carry the validation status and metadata for the fields you enabled, for example email status, safe-to-send, phone line type, and normalized name. Your existing properties are not touched.

<table data-header-hidden="false" data-header-sticky data-search="false"><thead><tr><th>Label</th><th width="111">Field Type</th><th>Description</th><th>Use Case</th><th>Property</th></tr></thead><tbody><tr><td>Clearout Email Safe To Send</td><td>Text</td><td>Indicates whether the contact's email is safe to send to based on its verification result.</td><td>Filter emails that are guaranteed to deliver without bouncing by selecting <strong>Safe to Send = Yes</strong>.</td><td>co_dp_e_safe</td></tr><tr><td>Clearout Email Status</td><td>Text</td><td>The email verification status such as Valid, Invalid, Catch-all, or Unknown.</td><td>Segment contacts by deliverability and decide which emails are worth contacting.</td><td>co_dp_e_status</td></tr><tr><td>Clearout Email Reason</td><td>Text</td><td>The sub-status explaining why the email received its verification result.</td><td>Understand and triage invalid or risky emails before deciding how to act on them.</td><td>co_dp_e_reason</td></tr><tr><td>Clearout Email SMTP Provider</td><td>Text</td><td>The SMTP or email service provider hosting the email's domain, such as Google or Microsoft.</td><td>Identify provider-specific deliverability patterns and tailor your sending strategy.</td><td>co_dp_e_smtp</td></tr><tr><td>Clearout Email Free Domain</td><td>Text</td><td>Indicates whether the contact's email belongs to a free email provider such as Gmail or Yahoo.</td><td>Distinguish personal email addresses from business email addresses when segmenting contacts.</td><td>co_dp_e_free</td></tr><tr><td>Clearout Email Role Email</td><td>Text</td><td>Indicates whether the contact's email is role based, such as info@, support@, or sales@.</td><td>Filter out shared mailboxes that are not tied to an individual.</td><td>co_dp_e_role</td></tr><tr><td>Clearout Email Disposable Email</td><td>Text</td><td>Indicates whether the contact's email belongs to a disposable or temporary email provider.</td><td>Exclude temporary email addresses from your CRM and outreach campaigns.</td><td>co_dp_e_disposable</td></tr><tr><td>Clearout Email Gibberish Email</td><td>Text</td><td>Indicates whether the email's local part appears to contain random or meaningless characters.</td><td>Flag low quality or fake email records to improve CRM quality.</td><td>co_dp_e_gibberish</td></tr><tr><td>Clearout Email Suggested Email</td><td>Text</td><td>A suggested correction for a likely mistyped email address.</td><td>Recover contacts entered with common email typos before discarding them.</td><td>co_dp_e_suggested</td></tr><tr><td>Clearout Name Gibberish</td><td>Text</td><td>Indicates whether the contact's name appears to contain random or meaningless characters.</td><td>Identify fake or low quality contact records.</td><td>co_dp_n_gibberish</td></tr><tr><td>Clearout Name Status</td><td>Text</td><td>The validation status of the contact's name.</td><td>Determine whether the provided value appears to be a person's name.</td><td>co_dp_n_status</td></tr><tr><td>Clearout Name Normalized</td><td>Text</td><td>The contact's name cleaned and standardized into a consistent format.</td><td>Keep name records consistent across your CRM and improve personalization.</td><td>co_dp_n_normalized_name</td></tr><tr><td>Clearout Phone Status</td><td>Text</td><td>The validation status of the phone number.</td><td>Filter out unreachable phone numbers before calling or texting.</td><td>co_dp_p_status</td></tr><tr><td>Clearout Phone Carrier</td><td>Text</td><td>The telecom carrier associated with the phone number.</td><td>Support carrier aware routing, cost optimization, or compliance checks.</td><td>co_dp_p_carrier</td></tr><tr><td>Clearout Phone Line Type</td><td>Text</td><td>The type of phone line, such as Mobile, Fixed Line, or VoIP.</td><td>Target SMS capable numbers and choose the appropriate communication channel.</td><td>co_dp_p_line_type</td></tr><tr><td>Clearout Phone Country Name</td><td>Text</td><td>The country associated with the phone number.</td><td>Segment contacts by country for regional campaigns.</td><td>co_dp_p_country_name</td></tr><tr><td>Clearout Phone E164 Format</td><td>Text</td><td>The phone number formatted according to the international E.164 standard.</td><td>Ensure consistent storage, reliable dialing, and duplicate detection.</td><td>co_dp_p_e164_format</td></tr><tr><td>Clearout Phone Location</td><td>Text</td><td>The geographic location associated with the phone number.</td><td>Target contacts based on location and localize outreach.</td><td>co_dp_p_location</td></tr><tr><td>Clearout Phone Country Timezone</td><td>Text</td><td>The timezone associated with the phone number's country.</td><td>Schedule calls and text messages at appropriate local times.</td><td>co_dp_p_country_timezone</td></tr><tr><td>Clearout Phone DST Observed</td><td>Text</td><td>Indicates whether Daylight Saving Time is currently observed.</td><td>Avoid contacting people too early or too late because of daylight saving adjustments.</td><td>co_dp_p_dst</td></tr><tr><td>Clearout Pulsed On</td><td>Date</td><td>The date and time when the contact was last enriched by Data Pulse.</td><td>Identify stale records that are due for revalidation or refresh.</td><td>co_dp_pulsed_on</td></tr></tbody></table>

> Property names may be prefixed or suffixed depending on the naming conventions supported by the destination platform.

### Next steps

* [Connect HubSpot](/integrations/hubspot/hubspot-crm.md#how-the-hobspot-two-way-sync-works)
* [Connect Salesforce](/integrations/salesforce.md#how-salesforce-two-way-sync-works)
* [Review Features & Functionality and FAQs](/data-pulse/faqs.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.clearout.io/data-pulse/supported-data-sources.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
