This preview of pull request 1639 is meant for internal use only.

Tray.io Destination

tray.io quick info

tray.io accepts Track, Page, Identify, Group, and Alias calls. If you reference it in the Integrations object, call it “tray.io”.

tray.io accepts cloud-mode data from all Segment source types. It does not offer device-mode connections.

Getting Started

Once your application is set up and instrumented with Segment, turn on tray in your Segment destinations page. After that, log in to your tray account and create a new workflow, using Segment as your trigger.

You can target up to 10 discrete tray workflows from within Segment.

Message Types

Tray supports all message types. You can filter the message type when you configure the trigger within tray.

Delete

When you trigger a user deletion using our Privacy features, we will forward a delete notification to tray so that you can automate further deletion and compliance workflows using tray.

The payload will consist of:

  • type: "delete"
  • userID: "the deleted userID"
  • timestamp: "the time of deletion"

In order to receive and process the message, we recommend starting with an “All Message Types” filter, and then removing all the default types and adding "delete" manually. We’re working with tray to add a dedicated "delete" message type filter in the dropdown pictured above.

Personas

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

For user-property destinations, an 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, Personas 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), Personas sets that value to false.

When you first create an audience, Personas 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.

Supported Sources and Connection Modes

Before you start, make sure tray.io supports the source type and connection mode you’ve chosen to implement. You can learn more about connection modes here.

Web Mobile Server
📱 Device-mode ⬜️ ⬜️ ⬜️
☁️ Cloud-mode

Segment offers an optional Device-based Connection Mode for Mobile data going to tray.io, so that you can use tray.io features that collect data directly from the mobile device. To do this, you must package the Segment-tray.io mobile SDK with the Segment mobile library.

Settings

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

Shared Secret

A optional key used when sending events to tray, to keep data flowing securely. You’ll need to also enter this secret in the Segment connector settings in the tray dashboard.

Workflow Urls (max 10)

List of the full URL (with http/https protocol) that we can send data to. eg. https://507f1352-cbc7-4abb-8dd2-538d3c09787d.trayapp.io. Limited to 10.

This page was last modified: 14 Jul 2020



Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
or
Create free account