SingleStore (Actions) Destination

1. From your workspace's Destination catalog page search for "SingleStore".
2. Select "SingleStore" and click Add Destination.
3. Select an existing Source to connect to SingleStore (Actions).
4. Enter a name for your SingleStore (Actions) destination, update any additional settings, then click Save.
5. Navigate to the Mappings tab for your SingleStore destination and click New Mapping.
6. Select Send Data.
7. In the Map fields section, select your database from the list presented.
8. Click Next and then Save.

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

• Send Data

Send data to SingleStore.

Send Data is a Cloud action. The default Trigger is type = "track" or type = "screen" or type = "identify" or type = "page" or type = "group" or type = "alias"

To connect Segment to SingleStore, use the SingleStore Data API (typically on port 443). Follow these steps to enable and locate your Data API connection settings:

1. Head to the SingleStore Portal.
2. Select Deployments.
3. Choose your Workspace and Database within the list of deployments.
4. From the Connect dropdown, select Connect to your own app. SingleStore will display the the key settings you need to connect your SingleStore database to Segment.

Note:

• The Data API is enabled by default for all SingleStore Cloud workspaces.
• Segment always uses the Data API (typically on port 443).
• If you use a self-hosted or development SingleStore deployment (such as the SingleStore-dev image), the Data API may run on a different port. Refer to your deployment's documentation or settings to confirm the correct port.

For more information, see the SingleStore Data API documentation.

Segment writes data to your specified table in SingleStore (by default, this is segment_data) using the following schema:

To query nested information from the traits, context, or properties JSON columns, use the :: operator to access nested properties within the JSON column. For example:

To extract a property1 from the properties column:

SELECT properties::property1 AS property_1 FROM <your_table_name>;

This query allows you to extract specific nested properties from the JSON column for analysis.

If you're unable to connect to the SingleStore database:

• Verify that the credentials are correct.
• Ensure that your SingleStore database is accessible from Segment's servers.
• Check firewall settings and network configurations.

If you encounter authentication errors when Segment attempts to connect:

• Confirm that the Username and Password are correct.
• Ensure that the user has the necessary permissions to write to the database.

If events are not recorded in the specified table:

• Verify that your sources are correctly sending data to Segment.
• Check the event types to ensure they are supported.
• Review your SingleStore database logs for any errors.

By default, the mapping stores all fields from the Segment event in separate columns in the segment_data table. If you prefer, you can customize the mapping to selectively include or exclude specific fields to be sent and written into SingleStore.

Event data is stored as JSON in the message column. This allows for flexible schema management and easy access to nested properties using SQL queries. SingleStore's ability to dynamically and quickly parse the JSON allows all types of complex events to be queried or used in notebooks.

Yes, Segment forwards data to SingleStore in near real-time, enabling immediate analysis and action on your customer data. Generally, data is available in the SingleStore database within approximately 30 seconds of Segment sending the event.

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.

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