# Using Connectors with Dr. Droid ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276520262/103d60d9-b959-4f5a-9270-27c5b2ae99cb.png align="center") You can connect Dr. Droid with various data sources such as [Segment](https://segment.com/), [Amplitude](https://amplitude.com/), [AWS CloudWatch](https://aws.amazon.com/cloudwatch/), [Sentry](https://sentry.io/), and many more using [Connectors](https://docs.drdroid.io/docs/connectors). If you are using any of these providers already, you can pipe the existing events to Dr. Droid directly. This feature is currently in private beta - request access by [signing up](https://app.drdroid.io/). In this article, we will explore how you can send Segment and Amplitude events to the Dr. Droid platform. # Segment Connector ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276523287/d2b174b3-17c0-4058-8316-f42259f684d0.png align="center") *Fig 1: Segment, credits:* [*segment.com*](http://segment.com) This section covers steps to connect your Segment account with Dr. Droid’s AWS Kinesis Firehose delivery stream and send events to Kinesis. ### Steps to Set Up Connection In the Segment’s dashboard, under the **Connections** section, the source you want to connect to your Kinesis Firehose destination, click **Add Destination.** ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276529730/882d6bbd-81c3-4c95-8a86-8041338e0ff4.png align="center") *Fig 2: Adding a new destination in the Segment console* Select **AWS Kinesis Firehose.** ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276538371/bae4fa44-11f9-438a-8daf-d0f75b83189e.png align="center") *Fig 3: Select Amazon Kinesis Firehose* ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276545497/f510ccd2-9527-4a52-8b03-ed23c921d3a1.png align="center") *Fig 4: Click on Configure Amazon Kinesis Firehose* The next step is to set up the **configuration** **of** **Amazon Kinesis Firehose.** 1. Select **Data Source,** then click Next ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276554927/b180d1eb-424a-4036-98ad-df3f169dce49.png align="center") Fig 5: Select Data Source 1. Next, enter the destination name and choose the preferred method for setting up the destination, which includes either filling out all the subsequent configurations manually or copying them from an existing destination instance. I opted to manually fill out the configuration settings, and then click **Create Destination.** ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276570512/5652ddec-054d-47f9-9c39-c4651c20e09f.png align="center") *Fig 6: Do manual setup* Now you can see the destination is created. ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276577908/389bab82-1eb1-4830-9dde-dad3a996903f.png align="center") *Fig 7: Destination Configuration in Segment* We need to configure connection settings. You can refer [here](https://segment.com/docs/connections/destinations/catalog/amazon-kinesis-firehose/#settings) for more details. 1. **Map segment events to the firehose delivery stream** and click **Save** ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276590130/8383867b-42b7-4df0-9420-5d01f2241e87.png align="center") *Fig 8: Map segment events to firehose delivery stream* 1. Enter **AWS Kinesis Firehose region** (defaults to **us-west-2**) and click **Save** ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276654510/eb9bc799-239d-4333-a759-0b57992c807e.png align="center") *Fig 9: Enter AWS Kinesis Firehose Region* 1. Enter **the Role Address** and click **Save** \[The address of the AWS role that will be written to Kinesis Firehose (ex: arn:aws:iam::xxxx:role/example-role)\] ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276664384/518238d1-932a-4394-af5a-6d84e6cdf9fd.png align="center") Fig 10: Enter Role Address You can test in the Event Tester if the connection is successful. ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276670876/e2690fd3-2e1c-498b-b850-4e281a6f1340.png align="center") *Fig 11: Event Tester* On Dr. Droid’s dashboard, you can see the events that are created. ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276677889/2b13d5ef-6ec9-4582-bf29-1fc1d49ea38c.png align="center") *Fig 12: Dr. Droid’s Dashboard* ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276689836/2b5c56dd-d415-423c-a4aa-d0a61908c05f.png align="center") ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276682366/20ffc396-4424-4505-8022-3b8049bf97bd.png align="center") Fig 13: Segment Test Event on Dr. Droid’s Dashboard Navigate to Amazon Kinesis Firehose **destination** in Segment, go to the **Settings tab,** and click the **Secret ID**. ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276806763/e0caaa4c-a566-4b75-bca5-336ec7e6a232.png align="center") *Fig 14: Secret ID* Share your *Secret ID* with the Dr. Droid team for them to configure it in the Amazon Kinesis Firehose to allow data flow from your segment account to us. Since this connector is in Beta, we will get on a call with you to convert your events into a format that Dr. Droid understands. In the upcoming days, you will be able to do the transformation by yourself on the platform. # Amplitude Connector Amplitude is a platform for analytics of products that aids businesses in monitoring visitors via collaborative analytics. Through the use of behavioral reports, the platform can comprehend how users interact with products and offer real-time insights to expedite work. This section covers the details on how you can link your Amplitude account and start sending amplitude events to Dr. Droid using AWS Kinesis Firehose Delivery streams. In the Amplitude **Data** tab, click **Catalog** and select the **Destinations tab.** In the **Warehouse Destination** section, click **Kinesis Data Firehose.** ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276827471/1e427a20-7b88-4066-a1a4-1f3472dfb8b0.png align="center") *Fig 15: Amplitude Dashboard* ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276835662/a8f7638c-5890-47ba-810d-188413611891.png align="center") *Fig 16: Select the Destination tab* In the **Kinesis Data Stream** dashboard, click **Add Destination**. ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276844967/328af0b5-3cf7-407d-a018-7dc41e3e449c.png align="center") *Fig 17: Add Destination - Kinesis Data Stream* Enter a sync name, then click **Create Sync** ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276855626/e50817e3-dea8-4e01-905f-2e2af6d8fa92.png align="center") *Fig 18: Enter Sync name for the destination* Then Click **Edit**, then enter the **AWS region**, **stream name,** and **role name,** use the **Send events** filter to select the events you want to send. You can send all events, but Amplitude recommends choosing the most important ones. When finished, **enable the destination** and **save**. ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276861767/059326ba-ffb4-4db4-8794-5ca5ff17ecf3.png align="center") Fig 19: Destination Settings Verify the connection with test data. ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276876055/d3573b0d-297c-4d18-9ea8-d8eff5fbef29.png align="center") *Fig 20: Verify the connection* On Dr. Droid’s dashboard, you can see the **amplitude\_demo\_event.** ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276887685/2eb194f5-2c96-4e6c-a610-b8ac83c1aeb3.png align="center") *Fig 21: Event received on Dr. Droid’s dashboard* ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1683276892681/9f210ad2-8a25-4d3f-bb64-856c170e0936.png align="center") *Fig 22: Attributes of the demo event* ## Summary I hope you find these Connectors useful to simplify event tracking across various systems. We are continuously working to add more connectors \[see [roadmap](https://docs.drdroid.io/docs/product-roadmap)\] and looking forward to [hearing](mailto:siddarth@drdroid.io) about your specific needs. If you haven’t tried Dr. Droid yet, do [signup](https://app.drdroid.io/signup). It is free for up to 1M events/month.