Skip to content

Commit ce8b957

Browse files
Apply suggestions from code review
Co-authored-by: rchinn-segment <[email protected]>
1 parent a1491de commit ce8b957

File tree

1 file changed

+6
-6
lines changed
  • src/connections/destinations/catalog/devrev

1 file changed

+6
-6
lines changed

src/connections/destinations/catalog/devrev/index.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,24 +7,24 @@ id: 649adeaa719bd3f55fe81bef
77

88
{% include content/plan-grid.md name="actions" %}
99

10-
DevRev is a business software company that brings developers (dev) and customers (rev) together in the era of product-led growth. We are building an API-first dev-centric CRM that uses data, design, and machine intelligence to empower devs to build, support, and grow their revs. Learn more at [devrev.ai](https://devrev.ai){:target="\_blank”}, Twitter [@devrevinc](https://twitter.com/devrevinc){:target="\_blank”} and [Medium](https://medium.com/devrev){:target="\_blank”}.
10+
DevRev is a business software company that brings developers (dev) and customers (rev) together in the era of product-led growth. DevRev is building an API-first dev-centric CRM that uses data, design, and machine intelligence to empower devs to build, support, and grow their revs. Learn more at [devrev.ai](https://devrev.ai){:target="\_blank”}, Twitter [@devrevinc](https://twitter.com/devrevinc){:target="\_blank”}, and [Medium](https://medium.com/devrev){:target="\_blank”}.
1111

1212
The DevRev destination uses Segment's action framework to take action in your DevOrg when particular events or activity is sent from enabled Segment Sources.
1313

14-
## Use Cases of the DevRev Destination (Actions)
14+
## DevRev Destination (Actions) use cases
1515

1616
With this destination, website or external events can trigger action within DevRev.
1717

1818
For example:
1919

20-
- When a user requests a demo, create work (ticket or issue) with the details
20+
- When a user requests a demo, DevRev creates a work ticket or issue with the details
2121
- When a user fills out a form, create a RevUser (lead) object
2222
- Track user events within DevRev
2323
<!-- The section below explains how to enable and configure the destination. Include any configuration steps not captured below. For example, obtaining an API key from your platform and any configuration steps required to connect to the destination. -->
2424

2525
## Getting started
2626

27-
1. Generate an API key from the [DevRev app](https://app.devrev.ai/). Be sure you're in the DevOrg you want the events sent to and then go to Settings (the gear in the top left) > Account > New Token. Copy this API key, as you'll need it when setting up your DevRev (Actions) destination in Segment.
27+
1. Generate an API key from the [DevRev app](https://app.devrev.ai/){:target="_blank"}. Be sure you're in the DevOrg you want the events sent to and then navigate to **Settings** (the gear in the top left) > **Account** > **New Token**. Copy this API key, as you'll need it when setting up your DevRev (Actions) destination in Segment.
2828
2. Open the Segment web app, click **Catalog**, then click **Destinations**.
2929
3. Search for DevRev (Actions) and click it.
3030
4. Click **Configure DevRev**.
@@ -36,7 +36,7 @@ For example:
3636

3737
By default, the `createRevUser` function will create a new RevUser (Contact) object in DevRev. This contact will be associated with an Account as well, based on the following rules:
3838

39-
1. If the email address is a personal email address (defined by having a domain in the domain blacklist), then the Account will be searched for using the email address specifically (aka `[email protected]` would look for an account with external_ref of `[email protected]`)
40-
2. If the email address is a company address (defined by having a domain not in the domain blacklist), then we will look for an account with the company domain. If found, the RevUser will be created attached to this Account. If there is no existing account, a new one will be created with the company domain (aka `[email protected]` would be added under the Account with the domain `company.com`)
39+
1. If the email address is a personal email address (defined by having a domain in the domain blacklist), then the Account will be searched for using the email address specifically (for example, `[email protected]` would look for an account with external_ref of `[email protected]`)
40+
2. If the email address is a company address (not having a domain in the domain blacklist), then DevRev looks for an account with the company domain. If found, the RevUser will be attached to this Account. If there is no existing account, a new one will be created with the company domain (for example, DevRev would add `[email protected]` under the Account with the domain `company.com`)
4141

4242
{% include components/actions-fields.html %}

0 commit comments

Comments
 (0)