Dreamdata IO Destination

Dreamdata IO 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 IO. For any issues with the destination, please reach out to their team.

_NOTE: Dreamdata IO is currently in beta, which means that there may still be some bugs for us to iron out. This doc was last updated on February 21, 2019, and we would love to hear your feedback. If you are interested in joining our beta program or have any feedback to help us improve the Dreamdata IO Destination and its documentation, please let us know!_

Getting Started

The first step is to make sure Dreamdata IO supports the source type and connection mode you’ve chosen to implement. You can learn more about what dictates the connection modes we support here.

WebMobileServer
📱 Device-mode
☁️ Cloud-mode
  1. From your Segment UI’s Destinations page click on “Add Destination”.
  2. Search for “Dreamdata IO” within the Destinations Catalog and confirm the Source you’d like to connect to.
  3. Drop in the “API Key” into your Segment Settings UI which you can find from your Dreamdata IO settings.
  4. You will be able to verify that data is flowing into Dreamdata IO from your Dreamdata IO settings.

Page

If you haven’t had a chance to review our spec, please take a look to understand what the Page method does. An example call would look like:

analytics.page()

Page calls will be sent to Dreamdata IO as a pageview.

Screen

If you haven’t had a chance to review our spec, please take a look to understand what the Screen method does. An example call would look like:

[[SEGAnalytics sharedAnalytics] screen:@"Home"];

Screen calls will be sent to Dreamdata IO as a screenview.

Identify

If you haven’t had a chance to review our spec, please take a look to understand what the Identify method does. An example call would look like:

analytics.identify('userId123', {
  email: 'john.doe@segment.com'
});

Identify calls will be sent to Dreamdata IO as an identify event.

Track

If you haven’t had a chance to review our spec, please take a look to understand what the Track method does. An example call would look like:

analytics.track('Clicked Login Button')

Track calls will be sent to Dreamdata IO as a track event.

Group

If you haven’t had a chance to review our spec, please take a look to understand what the Group method does. An example call would look like:

analytics.group("userId123", {
  name: "Initech",
  industry: "Technology",
  employees: 329,
  plan: "enterprise"
});

Group calls will be sent to Dreamdata IO as a group event where it is used to join users to accounts.

By default, Dreamdata IO uses user emails and your CRM data to map user activites to accounts and attribute the value correctly. Adding Group calls via Segment will give a more precise attribution and ensure that all activities are attributed to the right account.


Personas

You can send computed traits and audiences generated through Segment Personas to this destination as a user property. To learn more about Personas, reach out for a demo.

For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property order_completed_last_30days: true, and when this user no longer satisfies we will set that value to false.

When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.

Settings

Segment lets you change these destination settings via your Segment dashboard without having to touch any code.

API Key

You can find your API key in your settings page.

Adding Dreamdata IO to the integrations object

To add Dreamdata IO to the integrations JSON object (for example, to filter data from a specific source), use one of the 1 valid names for this integration:
  • Dreamdata IO


  • Questions? Need help? Contact us!
    Can we improve this doc?
    Email us: docs-feedback@segment.com!