# Reo.Dev Chrome Plugin
Reo’s chrome plugin brings Reo.Dev’s developer intelligence right into your CRM and any company website. Using this plugin you can easily access key account insights, developer activity data, de-anonymized developers and even find technical decision makers directly from your CRM or any company website, without switching tabs.
### **Installing the chrome plugin**
To use the Chrome extension, you need to have a [Reo.Dev](https://www.reo.dev/) account.
1. Open the chrome web store from [here](https://chromewebstore.google.com/detail/reodev/bdobidbjnimmpknddljenmdapnimepag)
2. Click on ‘add to chrome’ to install the extension.
{% hint style="info" %}
Note: Chrome may display a “not trusted by Enhanced Safe Browsing” notice during installation. This is a standard message for newly published extensions and can be safely ignored.
{% endhint %}
### **Using the plugin**
Once you’ve installed the plugin you can access it from the extension bar on chrome.
You will also see a floating widget on supported pages (Hubspot, Salesforce, and any company website). Click the widget to access Reo.Dev insights directly.
{% hint style="info" %}
Note: Currently, the extension supports viewing Reo insights from Hubspot, Salesforce and any company Website.
{% endhint %}
### **CRM**
**From a Company/Account Page**
1. **Overview:** This includes company name, firmographic details, developer funnel stage, and other key insights like Customer fit score, developer activity score, active developers and an overview of all developer activities tracked by Reo.Dev.
2. **Timeline:** Here you can see the complete log of developer activities. You can further filter activities by activity type (Github, documentation, product, website and others) and Repository type (owned, competition, complimentary).
3. **Active devs:** View all de-anonymized and active developers here and directly access their contact information.
You can also add developers to your CRM or email sequences directly from here.
4. **Prospects:** Discover developers and technical buyers that haven’t engaged with your tracked assets yet.
1. Choose the relevant ones and click on reveal to access their contact IDs.
b. Add all revealed contacts into your CRM or email sequences directly from here.
**From a contact page:**
1. **Insights:** View details like developer activity score, first and last and other activities across your tracked sources: Github, website, Communities & more.
2. **Timeline:** View the entire log of developer activity
3. **Add to CRM/sequence** - You can directly add contacts to your CRM or email sequences from here.
### Company Website Page
1. **Overview:** This includes company name, firmographic details, developer funnel stage, and other key insights like Customer fit score, developer activity score, active developers and activities including Github actions, documentation visits, product usage and other activities tracked by Reo.
2. **Timeline:** Here you can see the complete log of developer activities. You can further filter activities by activity type (Github, documentation, product, website and others) and Repository type (owned, competition, complimentary).
3. **Active devs:** View all de-anonymized developers here. Access their contact information like email ID, LinkedIn profile.
You can also **add developers to CRM and email sequences** directly from here. Plus, you can click on an individual developer to view their entire activity history.
3. **Prospects:** Discover developers and technical buyers that haven’t engaged with your tracked assets yet.
1. Choose the relevant ones and click on reveal to access their contact IDs.
b. Add all revealed contacts into your CRM or email sequences directly from here.
{% hint style="info" %}
Note: A status indicator appears on the floating widget - giving you instant context on whether an account is tracked on Reo or not:
* **Green** dot indicates the account is tracked on Reo and data is available.
* **Red** dot indicates the account is not tracked by Reo
 
{% endhint %}
### **Reo Chrome Extension – Permissions & Data Usage**
Reo’s Chrome extension is designed to surface **existing Reo intent signals and activity data directly within your workflow**—on websites and supported CRMs (Salesforce and HubSpot). To do this securely and accurately, the extension requires a limited set of browser permissions.
**What the Extension Does**
* Detects the **current page context** (website domain, Salesforce record, or HubSpot record)
* Matches that context to **existing data already available in Reo**
* Displays intent signals, activity timelines, and active developers in an in-page panel
**Permissions Required**
| Permission | Why You Need It |
| ------------- | ---------------------------------------- |
| Execute JS | To detect page context (website vs CRM) |
| Read DOM | To extract Salesforce/HubSpot record IDs |
| UI overlays | To show Reo intent panel |
| Backend calls | To fetch intent data |
| Local storage | Cache session/state (not user data) |
**Permissions & why are they needed?**
1. **Read the Current Tab’s URL -** To identify the domain you’re visiting or extract the CRM record ID (Account or Contact).
**What this means:**
* Only the **active tab URL** is read
* Browsing history is **not stored or tracked**
2. **Run Scripts on Pages (Content Scripts) -** To determine whether the page is a public website, a Salesforce record or HubSpot record. This allows the extension to load the correct Reo data.
**What this means:**
* Scripts are used for **context detection only**
* The extension does **not scrape page content**
* The extension does **not capture form inputs, passwords, or keystrokes**
3. **Read Page Structure (DOM Access)-** To locate CRM identifiers (e.g., Account ID or Contact ID) when viewing Salesforce or HubSpot records.
**What this means:**
* No page content is modified
* No sensitive information is collected
4. **Display UI Elements -** To render the Reo sidebar or overlay showing intent signals and activity timelines.
**What this means:**
* The extension adds a visual layer only
* It does not interfere with page functionality
5. **Communicate with Reo Servers -** To fetch relevant intent data from Reo when a matching domain or CRM record is detected.
**What this means:**
* Data is sent **only to `.reo.dev`**
* No third-party services are involved
6. **Local Storage -** To store session state and extension preferences.
**What this means:**
* No personal browsing data is stored
* No content from visited pages is saved
{% hint style="info" %}
**Please note,the Extension Does NOT Do:**
❌ Track or store browsing history
❌ Capture user inputs, passwords, or form data
❌ Read emails, messages, or private content
❌ Modify website or CRM data
❌ Send data to third parties
{% endhint %}
**Data & Security Commitment**
* The extension only surfaces **data that already exists in your Reo account**
* All communication is encrypted
* Access is strictly limited to what is required for functionality
* Permissions are reviewed regularly as the product evolves
### FAQs/Troubleshooting
#### **1. Why can’t I log in to the Chrome Extension?**
If you’re experiencing login issues with the Chrome extension, it may be due to **corrupted or outdated cookies** that interrupt the authentication process. To resolve this, please try clearing your cookies by following either of the below options.
**Option 1: Delete all cookies**
{% hint style="info" %}
**Important**: Clearing cookies may sign you out of websites and remove saved preferences. Proceed only if you’re comfortable with this.
{% endhint %}
**Steps**
1. Open **Chrome** on your computer.
2. Click the **More (⋮)** icon in the top-right corner → select **Delete browsing data**.
3. Choose **Basic** or **Advanced** and ensure **Cookies and other site data** is selected.
4. Under **Time range**, choose:
* Last hour
* Last 24 hours
* Last 7 days
* Last 4 weeks
* All time *(recommended)*
5. Select any additional items you want to delete.
6. Click **Delete data** to confirm.
\
**Option 2: Delete cookies for a specific website**
If you prefer to not delete all cookies, you can remove them only for the affected site.
**Steps**
1. Open **Chrome**.
2. Click **More (⋮)** → **Settings**.
3. Select **Privacy and security** → **Third-party cookies**.
4. Click **See all site data and permissions**.
5. Use the search bar in the top-right to find the website name.
6. Click **Delete (🗑️)** next to the site.
7. Confirm by selecting **Delete**.
\
**Next Steps:**
After clearing the cookies, **restart the Reo Chrome Extension** and try logging in again. If the issue persists, please contact support. To understand Cookies, refer this article:
#### 2. Why is a Contact or Account I’m researching not appearing in the Reo Chrome Extension?
If a contact or an account from your CRM is not being detected in the Reo plugin, it is typically due to one of the following reasons:\
\
**For contacts**
| Possible Reason | Explanation | What to Check |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| No recent activity | The contact has no qualifying intent or product activity tracked in Reo.Dev | Check if the contact is already in your Reo.Dev tenant. The Chrome Extension surfaces only those contacts with tracked activity. |
| Missing email in Reo profile | Reo.Dev identifies contacts primarily through email. If we don’t have an email associated with the profile, we cannot match it. |
Ensure the email exists in the contact record on Reo.Dev We’re actively improving our detection capabilities for LinkedIn, so coverage will continue to get better.
|
| Email mismatch | The email of the contact in your CRM does not match the email stored in Reo.Dev Even small variations result in mismatch (e.g., vs ). | Compare the CRM email to the email displayed in Reo.Dev and align them if needed. |
**For Accounts**
| Possible Reason | | |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| Domain mismatch | Reo.Dev identifies accounts based on domain structure. Different variations are treated as separate accounts. Example: microsoft.com vs microsoft.inc → counted separately. | Verify that the domain used in your CRM matches the domain used in Reo.Dev |
| No recent account activity | The account currently has no active signals, usage, or intent attributed to it. | Check whether the account exists in your Reo.Dev tenant. Accounts only appear in the Chrome Extension once Reo.Dev has detected activity for them. |
\
**Next Steps**
If you’ve confirmed the above scenarios and the issue persists:
* Refresh the page and reopen the plugin.
* Contact support with the CRM record link and the expected contact/account so we can assist.
.png?alt=media&token=81e2bed8-878a-4c19-bb89-ae8b400e1372)
.png?alt=media&token=b4e5a1dd-9506-4e87-b6b8-213fbda3bd07)
