> 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/LpXrIuXoRo1tuAYMfI7z/getting-started/for-admins/step-5-integrating-data-sources-with-reo.dev.md). # Step 5: Integrating data sources with Reo.Dev {% embed url="" %} In this guide, you'll learn how to set up integrations with various data sources including Github, documents, CRM and more to track developer activities across various platforms and sources and find active accounts to target. ### **Connecting Github** Connecting Github enables you to track developer actions such as pull requests, fork open issues, and more across your GitHub repositories. **Step 1:** Navigate to the **Integrations** tab

**Step 2:** Click on the **configure** button on the **Github card**

{% hint style="info" %} Here you can connect 3 main types of repositories 1. **Owned Github Repository -** These are repositories owned by your organization. 2. **Competitor Repository -** These are owned and managed by your competitors. This data helps find prospects actively engaging with your competitors' platforms. 3. **Complementary Repositories -** These are repositories of tools that are complement your product/service {% endhint %} **Step 3:** To add your company's own repositories, expand the tab for '**Owned GitHub Repositories**' and enter the URL of your repository. Add multiple repositories if needed. Follow the same process to add competitor and complementary repositories. After adding all the repositories, click **Save**.

### **Set up Tracking across Documents, Product, Website and Other key assets** Reo.Dev enables you to monitor and track developer activities across documents, product, website and other key assets. #### Documentation **Step 1:** On the integrations page, click on configure in the **'Documentation'** card

**Step 2:** **Configure Documentation URL -** Add the specific document URLs you want to track. For every URL, add a Page Name.

**Step 3:** Add your high-intent pages e.g, Troubleshooting, API Reference, Installation Guides as key pages so you can track activities on these pages separately. For every URL, add a Page Name.

**Step 4:** **Install Tracking Pixel on your Documentation -** Copy the Javascript code snippet and paste it in the \

of your site.

[Here's a more detailed guide on setting up tracking for your documentation. ](https://docs.reo.dev/integrations/input-sources/developer-insights/documentation) #### Website **Step 1:** Add the **website base URLs** you'd like to track activity on. For every URL - add a page name.

**Step 2:** Add your high-intent website pages as key pages to track activities on specific pages of your website separately. Add a page name for every key page.

**Step 3: Install Tracking Pixel -** Copy the below tracking code snippet and paste it in the of your site ```javascript !function(){var e,t,n;e="c07f38f6d83bb7e",t=function(){Reo.init({clientID:"c07f38f6d83bb7e"})},(n=document.createElement("script")).src="",n.defer=!0,n.onload=t,document.head.appendChild(n)}(); ``` [Here's a more detailed guide on setting up website tracking ](https://docs.reo.dev/integrations/input-sources/developer-insights/website) #### Code Interactions Track specific command interactions. Commands to install a package manager or execute software are high-intent signals indicating active engagement on your product. **Step 1:** On the integrations page, click on configure in the **'Code Interactions'** card

**Step 2:** Add the Key Commands you want to track. Add a command label for every command.

### **Connecting CRM** This integration helps you read life cycle stages for contacts and accounts, map customer CRM fields, and sync developer and account insights directly into your CRM. To integrate your CRM, head to CRM in the integrations section. Choose the CRM you want to connect.

Now, one of the biggest challenges SDRs face is using multiple tools for prospecting - one for finding leads and the other for sending emails. In Reo.Dev - you can do it all from one platform - Let's show you how. **Step 1:** Go to Integrations > Messaging Tools. Then, Configure the tools you want to connect.

For eg - Integrations with Apollo allows your teams to identify potential buyers and add them to your existing Apollo sequences from Reo.Dev itself.

**Step 2:** Add the API key. > [Here's a quick guide on how to create a master key on Apollo.ai](https://docs.reo.dev/integrations/output-integrations/messaging-tools/apollo.io#create-a-master-key-in-apollo.ai) In the sequences section you can see all the sequences that are on your apollo account. And in just a click you can enroll developers and buyer directly into these sequences.

--- # 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/LpXrIuXoRo1tuAYMfI7z/getting-started/for-admins/step-5-integrating-data-sources-with-reo.dev.md?ask=&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.