Elastic Path Source

Elastic Path is a SaaS based headless commerce platform that provides core commerce with a focus on catalog and product data management and modern merchandising capabilities so that brands can power their complex commerce experiences across multiple geographies, touchpoints, brands, and business models.

This is an Event Cloud Source which can not only export data into your Segment warehouse, but can also federate the exported data into your other enabled Segment Destinations.

This source is maintained by Elastic Path. For any issues with the source, contact the Elastic Path Support team.

Getting started

1. Navigate to Connections > Catalog and make sure you’re on the Sources tab of the catalog.
2. Search for Elastic Path in the Sources Catalog, select Elastic Path, and click Add Source.
3. Give the Source a name and configure any other settings.
   • The name identifies this source within your workspace, and typically reflects the name of the application. The name can be anything, but Segment recommends that you use something that reflects the source itself and distinguishes amongst your environments (for example, SourceName_Prod, SourceName_Staging, or SourceName_Dev).
4. Click Add Source to save your settings.
5. Copy the Write key from the Segment UI and log in to the Elastic Path Commerce Manager.
6. Navigate to Integrations Hub > Select Segment integration > configure integration where you need to use Segment key.

This integration uses JSONata templates to provide flexibility to send your custom fields to Segment.

You can configure how you want to associate an Elastic Path event with Segment event for streaming data. For example, send the Order Completed event to Segment when the Elastic Path order event is order.paid or order.authorized or if order is fulfilled, for example, order.fulfilled.

Stream

Elastic Path uses our stream Source component to send Segment event data. It uses a server-side (select from track, identify, page, group) method(s) to send data to Segment. These events are then available in any destination that accepts server-side events, and available in a schema in your data warehouse, so you can query using SQL.

The default behavior is for Elastic Path to pass the customerId associated with the order as the userId. There are instances in which Elastic Path lacks an associated customerId (e.g., in the case of a guest order). In these scenarios, the email address will be provided as anonymousId, or alternatively, you have the option to configure your own identifier.

Events

The table below lists events that Elastic Path sends to Segment. These events appear as tables in your warehouse, and as regular events in other Destinations.

Event properties

The property name tables below of the different events list the properties included in the events listed above.

Identity events

The following payload contains the properties for the following events:

• Customer Created
• Customer Updated

Note: You can add any custom fields as well as part of the traits e.g. age, gender, title, phone etc.

Order events

The following payload contains the properties for the following events:

• Checkout Started
• Order Completed
• Order Updated
• Order Cancelled
• Order Refunded

Note: Elastic path uses properties of these events from the eCommerce Spec defined by the Segment doc. Add more properties as per this documentation based on your business requirement.

Add destinations

After you configure your source, you can connect it with destinations. Log in to your downstream tools and check to see that your events appear as expected, and that they contain all of the properties you expect. If your events and properties don’t appear, check the Event Delivery tool, and refer to the destination docs for each tool for troubleshooting. If there are any issues with how the events arrive to Segment, contact the Elastic Path Support team.