Skip to content

Commit 237463a

Browse files
author
Thomas Gilbert
committed
change name to remove IO
1 parent 4b9d5cf commit 237463a

File tree

1 file changed

+12
-12
lines changed
  • src/connections/destinations/catalog/dreamdata-io

1 file changed

+12
-12
lines changed

src/connections/destinations/catalog/dreamdata-io/index.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
2-
title: Dreamdata IO Destination
2+
title: Dreamdata Destination
33
rewrite: true
44
id: 5c6ef3322a6fb40001a71bf7
55
---
6-
[Dreamdata IO](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) uses your Segment data to deliver multitouch, per account attribution. This enables B2B companies to understand the impact on revenue of every touch in their customer journey.
6+
[Dreamdata](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) uses your Segment data to deliver multitouch, per account attribution. This enables B2B companies to understand the impact on revenue of every touch in their customer journey.
77

8-
This destination is maintained by Dreamdata IO. For any issues with the destination, [contact the Dreamdata Support team](mailto:[email protected]).
8+
This destination is maintained by Dreamdata. For any issues with the destination, [contact the Dreamdata Support team](mailto:[email protected]).
99

1010
{% include content/beta-note.md %}
1111

@@ -14,9 +14,9 @@ This destination is maintained by Dreamdata IO. For any issues with the destinat
1414
{% include content/connection-modes.md %}
1515

1616
1. From the Segment web app, click **Catalog**.
17-
2. Search for "Dreamdata IO" in the Catalog, select it, and choose which of your sources to connect the destination to.
18-
3. Enter the "API Key" into your Segment Settings UI which you can find from your [Dreamdata IO settings](https://app.dreamdata.io/settings).
19-
4. You will be able to verify that data is flowing into Dreamdata IO from your [Dreamdata IO settings](https://app.dreamdata.io/settings).
17+
2. Search for "Dreamdata" in the Catalog, select it, and choose which of your sources to connect the destination to.
18+
3. Enter the "API Key" into your Segment Settings UI which you can find from your [Dreamdata settings](https://app.dreamdata.io/settings).
19+
4. You will be able to verify that data is flowing into Dreamdata from your [Dreamdata settings](https://app.dreamdata.io/settings).
2020

2121

2222
## Page
@@ -27,7 +27,7 @@ If you're not familiar with the Segment Specs, take a look to understand what th
2727
analytics.page()
2828
```
2929

30-
Page calls will be sent to [Dreamdata IO](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) as a `pageview`.
30+
Page calls will be sent to [Dreamdata](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) as a `pageview`.
3131

3232

3333
## Screen
@@ -38,7 +38,7 @@ If you're not familiar with the Segment Specs, take a look to understand what th
3838
[[SEGAnalytics sharedAnalytics] screen:@"Home"];
3939
```
4040

41-
Screen calls will be sent to [Dreamdata IO](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) as a `screenview`.
41+
Screen calls will be sent to [Dreamdata](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) as a `screenview`.
4242

4343

4444
## Identify
@@ -51,7 +51,7 @@ analytics.identify('userId123', {
5151
});
5252
```
5353

54-
Identify calls will be sent to [Dreamdata IO](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) as an `identify` event.
54+
Identify calls will be sent to [Dreamdata](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) as an `identify` event.
5555

5656

5757
## Track
@@ -62,7 +62,7 @@ If you're not familiar with the Segment Specs, take a look to understand what th
6262
analytics.track('Clicked Login Button')
6363
```
6464

65-
Track calls will be sent to [Dreamdata IO](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) as a `track` event.
65+
Track calls will be sent to [Dreamdata](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) as a `track` event.
6666

6767

6868
## Group
@@ -78,6 +78,6 @@ analytics.group("userId123", {
7878
});
7979
```
8080

81-
Group calls will be sent to [Dreamdata IO](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) as a `group` event where it is used to join users to accounts.
81+
Group calls will be sent to [Dreamdata](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) as a `group` event where it is used to join users to accounts.
8282

83-
By default, [Dreamdata IO](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) uses user emails and your CRM data to map user activites to accounts and attribute the value correctly. Adding Group calls using Segment will give a more precise attribution and ensure that all activities are attributed to the right account.
83+
By default, [Dreamdata](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) uses user emails and your CRM data to map user activites to accounts and attribute the value correctly. Adding Group calls using Segment will give a more precise attribution and ensure that all activities are attributed to the right account.

0 commit comments

Comments
 (0)