This source is maintained by Elastic Path. For any issues with the source, contact the[Elastic Path Support team](https://support.elasticpath.com/hc/en-us){:target="_blank"}.

1. Navigate to**Connections > Catalog** and make sure you're on the**Sources** tab of the catalog.

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`.

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.