Skip to content

Commit 61b1275

Browse files
Adjust documentation for Quin AI source integration
1 parent 75e19dc commit 61b1275

File tree

1 file changed

+11
-9
lines changed
  • src/connections/sources/catalog/cloud-apps/quin-ai

1 file changed

+11
-9
lines changed

src/connections/sources/catalog/cloud-apps/quin-ai/index.md

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,9 @@
1+
---
2+
title: Quin AI Source
3+
id: WGp9SQFRVu
4+
---
15

2-
### Quin AI Source
3-
4-
Quin AI is the first deep learning, real-time behavior prediction system dedicated to e-commerce conversion optimization, for growth and profitability.
6+
Quin AI is the first deep learning, real-time behavior prediction system dedicated to e-commerce conversion optimization for growth and profitability.
57

68
This source is maintained by Quin Audience Engine. For any issues with the source, [contact the Quin Audience Engine Support team](mailto:[email protected]).
79

@@ -10,21 +12,21 @@ This source is maintained by Quin Audience Engine. For any issues with the sourc
1012
1. From your workspace's Source page, click **Add Source**.
1113
2. Search for "Quin AI" in the Sources Catalog, select Quin AI, and click **Add Source**.
1214
3. On the next screen, give the Source a name configure any other settings.
13-
- The name is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The name 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).
15+
- The name is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The name can be anything, but we recommend using something that reflects the source itself and distinguishes amongst your environments (eg. QuinAI_Prod, QuinAI_Staging, QuinAI_Dev).
1416
4. Click **Add Source** to save your settings.
1517
5. Copy the Write key from the Segment UI.
16-
6. Log in to your [Quin account](https://portal.quinengine.com/) and navigate to Integrations > Segment > Settings.
18+
6. Log in to your [Quin account](https://portal.quinengine.com/){:target="_blank”} and navigate to Integrations > Segment > Settings.
1719
7. On the Settings page, paste your Segment write key to connect.
1820

1921
## Stream
2022

21-
Quin AI uses a stream Source component to send Segment event data. It uses server-side Track and Identify methods 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 that you can query using SQL.
23+
Quin AI uses a stream Source component and Track and Identify methods to send event data to Segment. These events are then available in any destination that accepts server-side events and as a schema in your data warehouse that you can query using SQL.
2224

23-
The default behavior is for Quin AI to pass the event data associated with the anonymous userId.
25+
The default behavior is for Quin AI to pass the event data associated with the anonymousId.
2426

2527
## Events
2628

27-
The table below lists events that Quin sends to Segment. These events appear as tables in your warehouse, and as regular events in other Destinations.
29+
The table below lists events that Quin sends to Segment. These events appear as tables in your warehouse and as regular events in other Destinations.
2830

2931
| Event Name | Description |
3032
|------------|------------------------------------|
@@ -78,4 +80,4 @@ Now that your Source is set up, you can connect to Destinations.
7880

7981
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.
8082

81-
If there are any issues with how the events are arriving to Segment, [contact the Quin AI support team](mailto:hello@<quinengine.com).
83+
If there are any issues with how the events are arriving to Segment, [contact the Quin AI support team](mailto:[email protected]).

0 commit comments

Comments
 (0)