Schematic (Actions) Destination

Schematic enables you to launch, package, meter, and monitor features with ease, so you can manage it all in one place as your business grows.

Segment is the easiest way to send events from your application to Schematic. If you already have Segment up and running in your application, Schematic recommends this approach so you don’t have to implement any additional code.

Schematic maintains this destination. For any issues with the destination, contact the Schematic Support team.

Getting started

1. From your Segment web app, navigate to Connections > Catalog > Destinations.
2. Search for Schematic, select the Schematic destination, and click Add destination.
3. Select the source that will send data to Schematic, give your destination a name, then click Create destination.
4. On the destination’s Settings tab, input your Schematic API Key. To generate an API key, navigate to your Schematic workspace settings under Settings > API Keys.

Once you’ve connected Schematic to Segment, you can configure how you want to send data to Schematic in the Schematic destination’s Mappings tab.

Destination Settings

Available Presets

Schematic has the following presets:

Available Actions

Build your own Mappings. Combine supported triggers with the following Schematic-supported actions:

• Track Event

• Identify User

Track Event

Send track events to Schematic

Track Event is a Cloud action. The default Trigger is: type = "track"

Click to show / hide fields

Identify User

Send identify events to Schematic

Identify User is a Cloud action. The default Trigger is: type = "identify"

Click to show / hide fields

Additional Context

Schematic only accepts Track event names that contain alphanumeric characters, dashes, and underscores. If Segment event names have other characters, like spaces, the Schematic destination automatically snake_cases the event name before passing to Schematic. Segment passes the raw event name as an event trait.

Engage

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule 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, 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.