---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/segment/connections/destinations/catalog/dreamdata-io#article
headline: Dreamdata Destination
description: Connect Segment to the Dreamdata destination to send Page, Screen, Identify, Track, and Group events for B2B multitouch, per-account revenue attribution.
url: https://www.twilio.com/docs/segment/connections/destinations/catalog/dreamdata-io
inLanguage: en
dateModified: 2026-07-15T17:40:17.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# Dreamdata Destination

## Destination Info

* Accepts [Page](/docs/segment/connections/spec/page), [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **Dreamdata IO**, **Dreamdata** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)
* This integration is **partner owned.** Please reach out to the partner's support for any issues.

[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.

This destination is maintained by Dreamdata. For any issues with the destination, [contact the Dreamdata Support team](mailto:friends@dreamdata.io).

## Getting Started

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

## Page

The [Page method](/docs/segment/connections/spec/page/) records page views on your website. An example call would look like:

```text title="Page call"
analytics.page()
```

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

## Screen

The [Screen method](/docs/segment/connections/spec/screen/) records screen views in your mobile app. An example call would look like:

```text title="Screen call"
[[SEGAnalytics sharedAnalytics] screen:@"Home"];
```

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

## Identify

The [Identify method](/docs/segment/connections/spec/identify/) associates a user with their traits. An example call would look like:

```text title="Identify call"
analytics.identify('userId123', {
  email: 'john.doe@example.com'
});
```

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

## Track

The [Track method](/docs/segment/connections/spec/track/) records actions users perform. An example call would look like:

```text title="Track call"
analytics.track('Clicked Login Button')
```

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

## Group

The [Group method](/docs/segment/connections/spec/group/) associates a user with a group, such as a company or account. An example call would look like:

```text title="Group call"
analytics.group("userId123", {
  name: "Initech",
  industry: "Technology",
  employees: 329,
  plan: "enterprise"
});
```

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.

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 activities 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.

## Engage

You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo).

For user-property destinations, an [identify](/docs/segment/connections/spec/identify/) call is sent to the destination for each user being added and removed. The property name is the snake\_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property `order_completed_last_30days: true`. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to `false`.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

## Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

| Field   | Description                                     | Required | Type   |
| ------- | ----------------------------------------------- | -------- | ------ |
| API Key | You can find your API key in your sources page. | Yes      | string |