You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/sources/catalog/cloud-apps/cx-studio/index.md
+30-30Lines changed: 30 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,14 +5,14 @@ beta: true
5
5
hidden: true
6
6
---
7
7
8
-
[Elastic Path CX Studio](https://www.elasticpath.com/products/cx-studio?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} enables brands to build and deploy hosted storefronts and shoppable landing pages with dynamic personalization powered by your Segment data. All in a no-code visual editor.
8
+
[Elastic Path CX Studio](https://www.elasticpath.com/products/cx-studio?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} enables brands to build and deploy hosted storefronts and shoppable landing pages with dynamic personalization powered by your Segment data, all in a no-code visual editor.
9
9
10
-
This is an [Event Cloud Source](/docs/sources/#event-cloud-sources){:target="_blank"} which can not only export data into your Segment warehouse, but can also federate the exported data into your other enabled Segment Destinations.
10
+
This is an [Event Cloud Source](/docs/sources/#event-cloud-sources){:target="_blank"} that can not only export data into your Segment warehouse but also federate the exported data into your other enabled Segment Destinations.
11
11
12
-
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"}.
12
+
Elastic Path maintains this source. For any issues with the source, contact the [Elastic Path Support team](https://support.elasticpath.com/hc/en-us){:target="_blank"}.
13
13
14
14
> info ""
15
-
> The Elastic Path CX Studio Source is currently in beta, which means that they are still actively developing the source. If you are interested in joining their beta program or have any feedback to help improve the Elastic Path CX Studio Source and its documentation, [let the Elastic Path team know](https://support.elasticpath.com/hc/en-us).
15
+
> The Elastic Path CX Studio Source is currently in beta, which means that they are still actively developing the source. If you are interested in joining their beta program or have any feedback to help improve the Elastic Path CX Studio Source and its documentation, [let the Elastic Path team know](https://support.elasticpath.com/hc/en-us){:target="_blank"}.
16
16
17
17
## Getting started
18
18
@@ -22,17 +22,17 @@ This source is maintained by Elastic Path. For any issues with the source, conta
22
22
- 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, `ElasticPath_Prod`, `ElasticPath_Staging`, or `ElasticPath_Dev`).
23
23
4. Click **Add Source** to save your settings.
24
24
5. Copy the Write key from the Segment UI and [log in to the Elastic Path CX Studio](https://app.unstack.com/login){:target="_blank"}.
25
-
6. Navigate to Settings > Integrations > Select Segment integration, and input the Segment write key.
25
+
6. Navigate to **Settings > Integrations > Select Segment integration**, and input the Segment write key.
26
26
27
27
## Stream
28
28
29
-
Elastic Path CX Studio uses our stream Source component to send Segment event data. It uses a client-side (select from `track`, `identify`, `page`, `group`) method(s) to send data to Segment. These events are then available in any destination that accepts client-side events, and available in a schema in your data warehouse, so you can query using SQL.
29
+
Elastic Path CX Studio uses the stream Source component to send Segment event data. It uses a client-side (select from `track`, `identify`, `page`, `group`) method(s) to send data to Segment. These events are then available in any destination that accepts client-side events, and available in a schema in your data warehouse, so you can query using SQL.
30
30
31
-
The default behavior is for Elastic Path CX Studio to pass the `anonymousId` if user is not logged in or pass `userId` if user is logged in. `anonymousId` is nothing but session id generated by Elastic Path CX Studio.
31
+
The default behavior is for Elastic Path CX Studio to pass the `anonymousId` if user is not logged in or pass `userId` if user is logged in, where `anonymousId` is a session ID generated by Elastic Path CX Studio.
32
32
33
33
## Events
34
34
35
-
The table below lists events that Elastic Path CX Studio sends to Segment. These events appear as tables in your warehouse, and as regular events in other Destinations.
35
+
The following table lists events that Elastic Path CX Studio sends to Segment. These events appear as tables in your warehouse and as regular events in other destinations.
@@ -161,22 +161,22 @@ Note: CX Studio uses properties of these events from the [eCommerce Spec](/docs/
161
161
162
162
## Identification
163
163
164
-
Elastic Path CX Studio automatically identifies users in Segment at certain points in their Elastic Path CX Studio session, to optimally connect your data across sessions and connections to other platforms (e.g. Commerce Cloud).
164
+
Elastic Path CX Studio automatically identifies users in Segment at certain points in their Elastic Path CX Studio session, to optimally connect your data across sessions and connections to other platforms (for example, Commerce Cloud).
165
165
166
-
### Session Initialization
166
+
### Session initialization
167
167
168
-
Elastic Path CX Studio initializes your Segment unify stream with an anonymous id that corresponds to the Elastic Path CX Studio session id. This enables simple continuity of event streams. This session id is further passed to Commerce Cloud, and used to identify backend events with the same anonymous id, for simple unification of all events in Segment.
168
+
Elastic Path CX Studio initializes your Segment unify stream with an anonymous ID that corresponds to the Elastic Path CX Studio session id. This enables simple continuity of event streams. This session ID is further passed to Commerce Cloud and used to identify backend events with the same anonymous ID, for simple unification of all events in Segment.
169
169
170
-
### User Identification
170
+
### User identification
171
171
172
172
When a user has filled a form with an email address, that email is used to identify the user in a more permanent way. Specifically, forms with an email address may include any contact form or a checkout form. Checkout forms will identify the user even if abandoned after successfully completing the email field. This allows later retargeting of abandoned sessions.
173
173
174
-
When a user has registered an account in Elastic Path CX Studio and Commerce Cloud, the user is further identified in Segment with their Commerce Cloud user id. This provides an additional connection point
174
+
When a user has registered an account in Elastic Path CX Studio and Commerce Cloud, the user is further identified in Segment with their Commerce Cloud user ID. This provides an additional connection point.
175
175
176
-
### The Role of Identification in Personalization
176
+
### The role of identification in personalization
177
177
178
-
Elastic Path CX Studio's Segment-unify personalization tooling is dependent on identity persistence. When a user revisits a session that has previously been identified, profile data can be retrieved from Segment including any augmented audience and trait data, which are referenceable within Elastic Path CX Studio for personalization. Please refer to the Elastic Path CX Studio Personalization recipe for more information.
178
+
Elastic Path CX Studio's Segment-unify personalization tooling is dependent on identity persistence. When a user revisits a session that has previously been identified, profile data can be retrieved from Segment including any augmented audience and trait data, which are referenceable within Elastic Path CX Studio for personalization. Refer to the Elastic Path CX Studio Personalization recipe for more information.
179
179
180
180
## Add destinations
181
181
182
-
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](https://support.elasticpath.com/hc/en-us){:target="_blank"}.
182
+
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](https://support.elasticpath.com/hc/en-us){:target="_blank"}.
0 commit comments