Skip to content

Commit eebedd1

Browse files
forstisabellaforstisabella
committed
converting table from html -> md
1 parent bfd4f0f commit eebedd1

File tree

1 file changed

+23
-84
lines changed
  • src/connections/sources/catalog/cloud-apps/formsort

1 file changed

+23
-84
lines changed

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

Lines changed: 23 additions & 84 deletions
Original file line numberDiff line numberDiff line change
@@ -23,98 +23,37 @@ This source is maintained by Formsort. For any issues with the source, [contact
2323

2424
The table below lists events that Formsort sends to Segment. These events appear as tables in your warehouse, and as regular events in other Destinations. The default behavior is for Formsort to pass the `responderUuid` associated with the user as the `userId`. This can be changed in the Formsort integration.
2525

26-
<table>
27-
<tr>
28-
</tr>
29-
<tr>
30-
<td>EmailCollected</td>
31-
<td>Responder's email was collected successfully, and the email has the data classification of "responder_email"</td>
32-
</tr>
33-
<tr>
34-
<td>FlowClosed</td>
35-
<td>Responder clicked the exit button to leave the flow</td>
36-
</tr>
37-
<tr>
38-
<td>FlowFinalized</td>
39-
<td>Responder has finished the flow and they are redirected or shown the completion screen</td>
40-
</tr>
41-
<tr>
42-
<td>FlowLoaded</td>
43-
<td>Flow has finished loading</td>
44-
</tr>
45-
<tr>
46-
<td>PhoneCollected</td>
47-
<td>Responder's phone number was collected successfully, and the phone number has the data classification of "responder_phone"</td>
48-
</tr>
49-
<tr>
50-
<td>StepCompleted</td>
51-
<td>Responder completed the step</td>
52-
</tr>
53-
<tr>
54-
<td>StepLoaded</td>
55-
<td>Step was loaded</td>
56-
</tr>
57-
<tr>
58-
<td>UrlOpened</td>
59-
<td>Responder clicked a link and was redirected to a new URL</td>
60-
</tr>
61-
</table>
26+
| Property Name | Description |
27+
| ------------- | -------------------------------------------------------------------------------------------------------------------------- |
28+
| EmailCollected | Responder's email was collected successfully, and the email has the data classification of "responder_email" |
29+
| FlowClosed | Responder clicked the exit button to leave the flow |
30+
| FlowFinalized | Responder has finished the flow and they are redirected or shown the completion screen |
31+
| FlowLoaded | Flow has finished loading |
32+
| PhoneCollected | Responder's phone number was collected successfully, and the phone number has the data classification of "responder_phone" |
33+
| StepCompleted | Responder completed the step |
34+
| StepLoaded | Step was loaded |
35+
| UrlOpened | Responder clicked a link and was redirected to a new URL |
6236

6337
## Event Properties
6438

6539
The following table lists event properties included with all events Segment receives from Formsort.
6640

67-
<table>
68-
<tr>
69-
<td>Property Name</td>
70-
<td>Description</td>
71-
</tr>
72-
<tr>
73-
<td>`event`</td>
74-
<td>Flow event type</td>
75-
</tr>
76-
<tr>
77-
<td>`flowLabel`</td>
78-
<td>Label of the flow</td>
79-
</tr>
80-
<tr>
81-
<td>`variantLabel`</td>
82-
<td>Label of the variant</td>
83-
</tr>
84-
<tr>
85-
<td>`variantUuid`</td>
86-
<td>UUID of the variant</td>
87-
</tr>
88-
<tr>
89-
<td>`responderUuid"</td>
90-
<td>UUID of the responder</td>
91-
</tr>
92-
<tr>
93-
<td>`userId`</td>
94-
<td>Identifying id for the responder</td>
95-
</tr>
96-
</table>
41+
| Property Name | Description |
42+
| -------------- | ------------------------- |
43+
| `event` | Flow event type |
44+
| `flowLabel` | Label of the flow |
45+
| `variantLabel` | Label of the variant |
46+
| `variantUuid` | UUID of the variant |
47+
| `responderUuid` | UUID of the responder |
48+
| `userId` | Identifying id for the responder |
9749

9850
This table lists event-specific properties Formsort sends to Segment:
9951

100-
<table>
101-
<tr>
102-
<td>Property Name</td>
103-
<td>Description</td>
104-
</tr>
105-
<tr>
106-
<td>stepId</td>
107-
<td>For step events, the named id of the step</td>
108-
</tr>
109-
<tr>
110-
<td>stepIndex</td>
111-
<td>For step events, the index of the step in the flow.</td>
112-
</tr>
113-
<tr>
114-
<td>msSpentOnStep</td>
115-
<td>For StepCompleted events, the time in millesconds the responder spent on the step.</td>
116-
</tr>
117-
</table>
52+
| Property Name | Description |
53+
| ------------- | ----------------------------------------------------------------------------------- |
54+
| stepId | For step events, the name of the step |
55+
| stepIndex | For step events, the index of the step in the flow. |
56+
| msSpentOnStep | For StepCompleted events, the time in milliseconds the responder spent on the step. |
11857

11958
Optionally, form answers submitted by responders can also be included in events sent to Segment. If enabled, responder answers will appear in an `answers` object for each event.
12059

0 commit comments

Comments
 (0)