Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit daafbba

Browse files
First release of Unlocking Simulation source documentation
1 parent 526f24f commit daafbba

File tree

1 file changed

+123
-0
lines changed
  • src/connections/sources/catalog/cloud-apps/unlocking-simulation

1 file changed

+123
-0
lines changed
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,123 @@
1+
# 💥 Segment Partner Source Documentation Template
2+
3+
---
4+
title: Unlocking Simulation Source
5+
---
6+
7+
8+
Unlocking Simulation(https://unlockingproducts.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) provides a way to create realistic simulated Segment events that mirror customer interactions with your application. This can help you analyze user behavior, test various scenarios, and optimize your tracking and analytics setup.
9+
10+
11+
This is an [Event Cloud Source](https://segment.com/docs/sources/#event-cloud-sources) which can not only export data into your Segment warehouse, but they can also federate the exported data into your other enabled Segment Destinations.
12+
13+
14+
This source is maintained by [Unlocking Growth](https://unlockinggrowth.co). For any issues with the source, [contact their Support team](mailto:[email protected]).
15+
16+
_**NOTE:** The Unlocking Simulation Source is currently in beta, which means that they are still actively developing the source. This doc was last updated on August 10, 2023. If you are interested in joining their beta program or have any feedback to help improve the Unlocking Simulation Source and its documentation, [let their team know](mailto:[email protected])!_
17+
18+
## Getting Started
19+
20+
21+
1. From your workspace's [Sources catalog page](https://app.segment.com/goto-my-workspace/sources/catalog) click **Add Source**.
22+
2. Search for "Unlocking Simulation" in the Sources Catalog, select Unlocking Simulation, and click **Add Source**.
23+
3. On the next screen, give the Source a nickname configure any other settings.
24+
25+
- The nickname is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The nickname can be anything, but we recommend using something that reflects the source itself and distinguishes amongst your environments (eg. SourceName_Prod, SourceName_Staging, SourceName_Dev).
26+
27+
4. Click **Add Source** to save your settings.
28+
5. Copy the Write key from the Segment UI and log in to your Unlocking Simulation account - navigate to Settings > Integrations > Segment Integration and paste the key to connect.
29+
30+
## Stream
31+
32+
Unlocking Simulation uses our stream Source component to send Segment event data. It uses server-side (`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.
33+
34+
As part of the simulated events, Unlocking Simulation generates fake userIds and emails and includes them in the relevant traits and track events.
35+
36+
37+
## Events
38+
39+
The events generated into Segment are based on what you configure within Unlocking Simulation. If, for example, you have set up Unlocking Simulation to generate a "Login" event for each new user on a daily basis, then that event will be generated into Segment.
40+
41+
42+
> (delete the below sentence and table)
43+
The table below lists events that Unlocking Simulation sends to Segment. These events appear as tables in your warehouse, and as regular events in other Destinations. Unlocking Simulation includes the `userId` if available.
44+
45+
<table>
46+
<tr>
47+
<td>Event Name</td>
48+
<td>Description</td>
49+
</tr>
50+
<tr>
51+
<td>Email Sent</td>
52+
<td>Email was sent successfully</td>
53+
</tr>
54+
<tr>
55+
<td>Email Opened</td>
56+
<td>Prospect opened the email</td>
57+
</tr>
58+
<tr>
59+
<td>Link Clicked</td>
60+
<td>Prospect clicked the tracking link</td>
61+
</tr>
62+
<tr>
63+
<td>Email Replied</td>
64+
<td>Prospect replied to the email sent</td>
65+
</tr>
66+
<tr>
67+
<td>Email Bounced</td>
68+
<td>Email servers rejected the email</td>
69+
</tr>
70+
<tr>
71+
<td>Email Unsubscribed</td>
72+
<td>Prospect clicked the unsubscribe link</td>
73+
</tr>
74+
</table>
75+
76+
## Event Properties
77+
78+
Similarly to Events, the Event Properties generated by Unlocking Simulation are entirely based on what you configure within the simulator. All property types are supported.
79+
80+
> (delete the below sentence and table)
81+
The table below list the properties included in the events listed above.
82+
83+
<table>
84+
<tr>
85+
<td>Property Name</td>
86+
<td>Description</td>
87+
</tr>
88+
<tr>
89+
<td>`event`</td>
90+
<td>Email event type</td>
91+
</tr>
92+
<tr>
93+
<td>`userId`</td>
94+
<td>Prospect email ID</td>
95+
</tr>
96+
<tr>
97+
<td>`email_id`</td>
98+
<td>ID of the email</td>
99+
</tr>
100+
<tr>
101+
<td>`fromId`</td>
102+
<td>Sender email ID</td>
103+
</tr>
104+
<tr>
105+
<td>`email_subject`</td>
106+
<td>Subject line of the email</td>
107+
</tr>
108+
<tr>
109+
<td>`link`</td>
110+
<td>URL of the link clicked</td>
111+
</tr>
112+
</table>
113+
114+
## Adding Destinations
115+
116+
Now that your Source is set up, you can connect it with Destinations.
117+
118+
Log into 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](https://segment.com/docs/connections/event-delivery/) tool, and refer to the Destination docs for each tool for troubleshooting.
119+
120+
If there are any issues with how the events are arriving to Segment, [contact the Unlocking Simulation support team](mailto:support@Unlocking Simulation.com).
121+
122+
123+
---

0 commit comments

Comments
 (0)