Skip to content

Commit 4698169

Browse files
pwsegpwseg
authored
Merge pull request #5556 from psin32/cx-studio/source
Cx studio/source
2 parents c7071ce + 333a6ce commit 4698169

File tree

1 file changed

+182
-0
lines changed
  • src/connections/sources/catalog/cloud-apps/cx-studio

1 file changed

+182
-0
lines changed

‎src/connections/sources/catalog/cloud-apps/cx-studio/index.md

Lines changed: 182 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,182 @@
1+
---
2+
title: Elastic Path CX Studio Source
3+
id: NC2jsEkA8Y
4+
beta: true
5+
hidden: true
6+
---
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.
9+
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+
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+
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){:target="_blank"}.
16+
17+
## Getting started
18+
19+
1. Navigate to **Connections > Catalog** and make sure you're on the **Sources** tab of the catalog.
20+
2. Search for **Elastic Path CX Studio** in the Sources Catalog, select **Elastic Path CX Studio**, and click **Add Source**.
21+
3. Give the Source a name and configure any other settings.
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+
4. Click **Add Source** to save your settings.
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.
26+
27+
## Stream
28+
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+
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+
33+
## Events
34+
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.
36+
37+
| Event Name | Description |
38+
| ------------------------- | ------------------------------------------------------------ |
39+
| `Products Searched` | User searched for products. |
40+
| `Product List Viewed` | User viewed a product list or category |
41+
| `Product List Filtered` | User filtered a product list or category. |
42+
| `Product Viewed` | User viewed a product details page. |
43+
| `Product Added` | User added a product to their shopping cart. |
44+
| `Product Removed` | User removed a product from their shopping cart. |
45+
| `Checkout Started` | User initiated the order process (a transaction is created). |
46+
| `Checkout Step Viewed` | User viewed a checkout step. |
47+
| `Checkout Step Completed` | User completed a checkout step. |
48+
49+
## Event properties
50+
51+
The property name tables below of the different events list the properties included in the events listed above.
52+
53+
### Browsing events
54+
55+
#### Products searched
56+
57+
| Property Name | Description |
58+
| ------------- | --------------------------------------------------- |
59+
| `query` | Query the user searched with, for example, shirt, jeans, and so on. |
60+
61+
#### Product list viewed
62+
63+
| Property Name | Description |
64+
| ----------------------- | ----------------------------------------------------- |
65+
| `category` | Product category being viewed. |
66+
| `list_id` | Product list being viewed, like search. |
67+
| `products` | Products displayed in the product list. |
68+
| `products.$.brand` | Brand associated with the product. |
69+
| `products.$.currency` | Currency in which product price is shown to customer. |
70+
| `products.$.image_url` | Image url of the product. |
71+
| `products.$.name` | Name of the product being viewed. |
72+
| `products.$.price` | Price of the product being viewed. |
73+
| `products.$.product_id` | Product ID. |
74+
| `products.$.quantity` | Quantity of a product. |
75+
76+
#### Product list filtered
77+
78+
| Property Name | Description |
79+
| ----------------------- | ----------------------------------------------------- |
80+
| `category` | Product category being viewed. |
81+
| `list_id` | Product list being viewed, like search. |
82+
| `products` | Products displayed in the product list. |
83+
| `products.$.brand` | Brand associated with the product. |
84+
| `products.$.currency` | Currency in which product price is shown to customer. |
85+
| `products.$.image_url` | Image url of the product. |
86+
| `products.$.name` | Name of the product being viewed. |
87+
| `products.$.price` | Price of the product being viewed. |
88+
| `products.$.product_id` | Product ID. |
89+
| `products.$.quantity` | Quantity of a product. |
90+
91+
### Core ordering events
92+
93+
#### Product viewed
94+
95+
| Property Name | Description |
96+
| ------------- | ----------------------------------------------------- |
97+
| `brand` | Brand associated with the product. |
98+
| `currency` | Currency in which product price is shown to customer. |
99+
| `image_url` | Image URL of the product. |
100+
| `name` | Name of the product being viewed. |
101+
| `price` | Price of the product being viewed. |
102+
| `product_id` | Product ID. |
103+
| `quantity` | Quantity of a product. |
104+
105+
#### Product added
106+
107+
| Property Name | Description |
108+
| ------------- | ----------------------------------------------------- |
109+
| `brand` | Brand associated with the product. |
110+
| `currency` | Currency in which product price is shown to customer. |
111+
| `image_url` | Image url of the product. |
112+
| `name` | Name of the product being viewed. |
113+
| `price` | Price of the product being viewed. |
114+
| `product_id` | Product ID. |
115+
| `quantity` | Quantity of a product. |
116+
117+
#### Product removed
118+
119+
| Property Name | Description |
120+
| ------------- | ----------------------------------------------------- |
121+
| `brand` | Brand associated with the product. |
122+
| `currency` | Currency in which product price is shown to customer. |
123+
| `image_url` | Image url of the product. |
124+
| `name` | Name of the product being viewed. |
125+
| `price` | Price of the product being viewed. |
126+
| `product_id` | Product ID. |
127+
| `quantity` | Quantity of a product. |
128+
129+
#### Checkout started
130+
131+
| Property Name | Description |
132+
| ----------------------- | ----------------------------------------------------- |
133+
| `currency` | Currency code associated with the transaction |
134+
| `discount` | Total discount associated with the transaction |
135+
| `order_id` | Currency in which product price is shown to customer. |
136+
| `shipping` | Shipping cost associated with the transaction. |
137+
| `tax` | Total tax associated with the transaction. |
138+
| `value` | Revenue ($) with discounts and coupons added in. |
139+
| `products` | Products displayed in the product list. |
140+
| `products.$.name` | Name of the product being viewed. |
141+
| `products.$.price` | Price of the product being viewed. |
142+
| `products.$.product_id` | Product ID. |
143+
| `products.$.quantity` | Quantity of a product. |
144+
| `products.$.sku` | Sku of the product being viewed |
145+
146+
#### Checkout step viewed
147+
148+
| Property Name | Description |
149+
| --------------- | -------------------------------------------------- |
150+
| `checkout_id` | Checkout transaction ID |
151+
| `checkout_step` | Number representing a step in the checkout process |
152+
153+
#### Checkout step completed
154+
155+
| Property Name | Description |
156+
| --------------- | -------------------------------------------------- |
157+
| `checkout_id` | Checkout transaction ID |
158+
| `checkout_step` | Number representing a step in the checkout process |
159+
160+
Note: CX Studio uses properties of these events from the [eCommerce Spec](/docs/connections/spec/ecommerce/v2){:target="_blank"} defined by the Segment doc.
161+
162+
## Identification
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 (for example, Commerce Cloud).
165+
166+
### Session initialization
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.
169+
170+
### User identification
171+
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+
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+
176+
### The role of identification in personalization
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. Refer to the Elastic Path CX Studio Personalization recipe for more information.
179+
180+
## Add destinations
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"}.

0 commit comments

Comments
 (0)