From ae179422cf3e5d98efbb4be10cfef3aabaf66e9f Mon Sep 17 00:00:00 2001 From: Sneha Shashidhar <97519099+sneha-shashidhar@users.noreply.github.com> Date: Tue, 6 Aug 2024 14:20:41 +0100 Subject: [PATCH 01/17] Update user-deletion-and-suppression.md --- src/privacy/user-deletion-and-suppression.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/privacy/user-deletion-and-suppression.md b/src/privacy/user-deletion-and-suppression.md index ab97bca482..7ac0062c44 100644 --- a/src/privacy/user-deletion-and-suppression.md +++ b/src/privacy/user-deletion-and-suppression.md @@ -71,7 +71,7 @@ Note that list only includes `SUPPRESS_ONLY` regulations. If you created a User To create a suppression regulation and add a `userId` to this list, click **Suppress New User**, and enter the `userId` in the field that appears. Then click **Request Suppression**. -Segment creates a `SUPPRESS` regulation, and adds the `userId` to your suppression list, mostly processed within 24 hours. In some cases, the suppression request can take up to 30 days to process. +Segment creates a `SUPPRESS` regulation, and adds the `userId` to your suppression list, mostly processed within 24 hours. In some cases, the suppression request can take up to 30 days to process. You can suppress up to 5000 userIds per call via Public API. ### Remove a user from the suppression list From 2fec51643426590263dffb5d443d2183ec0a4f3c Mon Sep 17 00:00:00 2001 From: Niall Date: Fri, 23 Aug 2024 14:08:26 +0100 Subject: [PATCH 02/17] add model number info --- src/connections/spec/common.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/spec/common.md b/src/connections/spec/common.md index 32559d39ae..e044908df9 100644 --- a/src/connections/spec/common.md +++ b/src/connections/spec/common.md @@ -139,7 +139,7 @@ Context is a dictionary of extra information that provides useful context about | `active` | Boolean | Whether a user is active.

This is usually used to flag an `.identify()` call to just update the traits but not "last seen." | | `app` | Object | dictionary of information about the current application, containing `name`, `version`, and `build`.

This is collected automatically from the mobile libraries when possible. | | `campaign` | Object | Dictionary of information about the campaign that resulted in the API call, containing `name`, `source`, `medium`, `term`, `content`, and any other custom UTM parameter.

This maps directly to the common UTM campaign parameters. | -| `device` | Object | Dictionary of information about the device, containing `id`, `advertisingId`, `manufacturer`, `model`, `name`, `type`, and `version`. | +| `device` | Object | Dictionary of information about the device, containing `id`, `advertisingId`, `manufacturer`, `model`, `name`, `type`, and `version`.

**Note:** `model` for iOS may not exactly correspond to an iPhone model number. For example, an `iPhone 15 Pro Max` has a model number of `iPhone16,2`. These values are set by iOS. | | `ip` | String | Current user's IP address. | | `library` | Object | Dictionary of information about the library making the requests to the API, containing `name` and `version`. | | `locale` | String | Locale string for the current user, for example `en-US`. | @@ -258,7 +258,7 @@ Every API call has four timestamps, `originalTimestamp`, `timestamp`, `sentAt`, | Timestamp | Calculated | Description | | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `originalTimestamp` | Time on the client device when call was invoked
**OR**
The `timestamp` value manually passed in through server-side libraries. | Used by Segment to calculate `timestamp`.

**Note:** `originalTimestamp` is not useful for analysis since it's not always trustworthy as it can be easily adjusted and affected by clock skew. | -| `sentAt` | Time on client device when call was sent.
**OR**
`sentAt` value manually passed in. | Used by Segment to calculate `timestamp`.

**Note:** `sentAt` is not useful for analysis since it's not always trustworthy as it can be easily adjusted and affected by clock skew. | +| `sentAt` | Time on client device when call was sent.
**OR**
`sentAt` value manually passed in. | Used by Segment to calculate `timestamp`.

**Note:** `sentAt` is not useful for analysis since it's not always by clock skew. | | `receivedAt` | Time on Segment server clock when call was received | Used by Segment to calculate `timestamp`, and used as sort key in Warehouses.

**Note:** For max query speed, `receivedAt` is the recommended timestamp for analysis when chronology does not matter as chronology is not ensured. | | `timestamp` | Calculated by Segment to correct client-device clock skew using the following formula:
`receivedAt` - (`sentAt` - `originalTimestamp`) | Used by Segment to send to downstream destinations, and used for historical replays.

**Note:** Recommended timestamp for analysis when chronology does matter. | From b79d8057d0bffdb87aa13dbf8df6371e03b05fc0 Mon Sep 17 00:00:00 2001 From: eren-quinengine Date: Tue, 27 Aug 2024 16:30:27 +0300 Subject: [PATCH 03/17] Create documentation for Quin AI source integration --- .../catalog/cloud-apps/quin-ai/index.md | 85 +++++++++++++++++++ 1 file changed, 85 insertions(+) create mode 100644 src/connections/sources/catalog/cloud-apps/quin-ai/index.md diff --git a/src/connections/sources/catalog/cloud-apps/quin-ai/index.md b/src/connections/sources/catalog/cloud-apps/quin-ai/index.md new file mode 100644 index 0000000000..ad29217157 --- /dev/null +++ b/src/connections/sources/catalog/cloud-apps/quin-ai/index.md @@ -0,0 +1,85 @@ +# Quin AI Documentation + +--- +Quin AI Source +--- + +Quin AI is the first deep learning, real-time behaviour prediction system dedicated to e-commerce conversion optimisation, for growth and profitability. + +This source is maintained by Quin Audience Engine. For any issues with the source, [contact their Support team](mailto:hello@quinengine.com). + +## Getting started + +1. From your workspace's Source page, click **Add Source**. +2. Search for "Quin AI" in the Sources Catalog, select Quin AI, and click **Add Source**. +3. On the next screen, give the Source a name configure any other settings. + +- 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). + +4. Click **Add Source** to save your settings. +5. Copy the Write key from the Segment UI. +6. Log in to your [Quin account](https://portal.quinengine.com/) - navigate to Integrations > Segment > Settings and paste the write key to connect. + +## Stream + +Quin AI uses our stream Source component to send Segment event data. It uses a server-side `track` and `identify` 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. + +The default behavior is for Quin AI to pass the event data associated with the anonymous userId. + +## Events + +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. + +| Event Name | Description | +|--------------------|------------------------------------| +| pageview | Get an action after viewing a page | +| click | Get an action after a click | + + +## Event Properties + +The table below list the properties included in the events listed above. + +| Property Name | Description | +|----------------------------|-------------------------------------------------------------| +| `ActionAudienceId` | ID of the target audience for the action | +| `ActionControlGroup` | Boolean indicating if the action is part of a control group | +| `ActionId` | Unique identifier for the action | +| `ActionIsCustom` | Boolean indicating if the action is custom | +| `ActionName` | Name of the action | | | +| `ActionType` | Type of the action | | | +| `BasketPrice` | Total price of the items in the basket | | | +| `BasketQuantity` | Total quantity of items in the basket | | | +| `EventAction` | Type of event action (e.g., pageview, click) | | | +| `EventCategory` | Category of the event | | | | | +| `EventCount` | Number of events | | | | | +| `EventCustomAttributes` | Map of custom attributes associated with the event | | | | | +| `EventDuration` | Duration of the event in seconds | | | | | +| `EventLabel` | Label of the event | | | | | +| `EventPlatform` | Platform on which the event occurred (e.g., web, mobile) | | | | | +| `EventTimestamp` | Timestamp when the event occurred | | | | | +| `EventURL` | URL associated with the event | | | | | +| `GoogleClientId` | Google Analytics client ID | | | | | +| `ItemCategory` | Category of the item | | +| `ItemCurrency` | Currency of the item price (e.g., TRY) | | +| `ItemCustomAttributes` | Map of custom attributes associated with the item | | +| `ItemId` | Unique identifier for the item | | +| `ItemName` | Name of the item | | +| `ItemPrice` | Price of the item | | +| `MostVisitedCategory` | List of most visited categories | | +| `MostVisitedCategoryCount` | Number of times the most visited categories were visited | | +| `Prediction` | Map of prediction probabilities for various outcomes | +| `ReturningUser` | Boolean indicating if the user is a returning user | | +| `SessionId` | Unique identifier for the session | | +| `UTMCampaign` | UTM campaign parameter | | +| `UTMMedium` | UTM medium parameter | | +| `UTMSource` | UTM source parameter | | + + +## Adding Destinations + +Now that your Source is set up, you can connect it with Destinations. + +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 there are any issues with how the events are arriving to Segment, [contact the Quin AI support team](mailto:hello@ Date: Wed, 28 Aug 2024 11:11:25 +0300 Subject: [PATCH 04/17] Adjust documentation for Quin AI source integration --- .../catalog/cloud-apps/quin-ai/index.md | 74 +++++++++---------- 1 file changed, 35 insertions(+), 39 deletions(-) diff --git a/src/connections/sources/catalog/cloud-apps/quin-ai/index.md b/src/connections/sources/catalog/cloud-apps/quin-ai/index.md index ad29217157..57aaf9663e 100644 --- a/src/connections/sources/catalog/cloud-apps/quin-ai/index.md +++ b/src/connections/sources/catalog/cloud-apps/quin-ai/index.md @@ -1,28 +1,24 @@ -# Quin AI Documentation ---- -Quin AI Source ---- +### Quin AI Source -Quin AI is the first deep learning, real-time behaviour prediction system dedicated to e-commerce conversion optimisation, for growth and profitability. +Quin AI is the first deep learning, real-time behavior prediction system dedicated to e-commerce conversion optimization, for growth and profitability. -This source is maintained by Quin Audience Engine. For any issues with the source, [contact their Support team](mailto:hello@quinengine.com). +This source is maintained by Quin Audience Engine. For any issues with the source, [contact the Quin Audience Engine Support team](mailto:hello@quinengine.com). ## Getting started 1. From your workspace's Source page, click **Add Source**. 2. Search for "Quin AI" in the Sources Catalog, select Quin AI, and click **Add Source**. 3. On the next screen, give the Source a name configure any other settings. - -- 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). - + - 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). 4. Click **Add Source** to save your settings. 5. Copy the Write key from the Segment UI. -6. Log in to your [Quin account](https://portal.quinengine.com/) - navigate to Integrations > Segment > Settings and paste the write key to connect. +6. Log in to your [Quin account](https://portal.quinengine.com/) and navigate to Integrations > Segment > Settings. +7. On the Settings page, paste your Segment write key to connect. ## Stream -Quin AI uses our stream Source component to send Segment event data. It uses a server-side `track` and `identify` 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. +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. The default behavior is for Quin AI to pass the event data associated with the anonymous userId. @@ -46,39 +42,39 @@ The table below list the properties included in the events listed above. | `ActionControlGroup` | Boolean indicating if the action is part of a control group | | `ActionId` | Unique identifier for the action | | `ActionIsCustom` | Boolean indicating if the action is custom | -| `ActionName` | Name of the action | | | -| `ActionType` | Type of the action | | | -| `BasketPrice` | Total price of the items in the basket | | | -| `BasketQuantity` | Total quantity of items in the basket | | | -| `EventAction` | Type of event action (e.g., pageview, click) | | | -| `EventCategory` | Category of the event | | | | | -| `EventCount` | Number of events | | | | | -| `EventCustomAttributes` | Map of custom attributes associated with the event | | | | | -| `EventDuration` | Duration of the event in seconds | | | | | -| `EventLabel` | Label of the event | | | | | -| `EventPlatform` | Platform on which the event occurred (e.g., web, mobile) | | | | | -| `EventTimestamp` | Timestamp when the event occurred | | | | | -| `EventURL` | URL associated with the event | | | | | -| `GoogleClientId` | Google Analytics client ID | | | | | -| `ItemCategory` | Category of the item | | -| `ItemCurrency` | Currency of the item price (e.g., TRY) | | -| `ItemCustomAttributes` | Map of custom attributes associated with the item | | -| `ItemId` | Unique identifier for the item | | -| `ItemName` | Name of the item | | -| `ItemPrice` | Price of the item | | -| `MostVisitedCategory` | List of most visited categories | | -| `MostVisitedCategoryCount` | Number of times the most visited categories were visited | | +| `ActionName` | Name of the action | +| `ActionType` | Type of the action | +| `BasketPrice` | Total price of the items in the basket | +| `BasketQuantity` | Total quantity of items in the basket | +| `EventAction` | Type of event action (e.g., pageview, click) | +| `EventCategory` | Category of the event | +| `EventCount` | Number of events | +| `EventCustomAttributes` | Map of custom attributes associated with the event | +| `EventDuration` | Duration of the event in seconds | +| `EventLabel` | Label of the event | +| `EventPlatform` | Platform on which the event occurred (e.g., web, mobile) | +| `EventTimestamp` | Timestamp when the event occurred | +| `EventURL` | URL associated with the event | +| `GoogleClientId` | Google Analytics client ID | +| `ItemCategory` | Category of the item | +| `ItemCurrency` | Currency of the item price (e.g., TRY) | +| `ItemCustomAttributes` | Map of custom attributes associated with the item | +| `ItemId` | Unique identifier for the item | +| `ItemName` | Name of the item | +| `ItemPrice` | Price of the item | +| `MostVisitedCategory` | List of most visited categories | +| `MostVisitedCategoryCount` | Number of times the most visited categories were visited | | `Prediction` | Map of prediction probabilities for various outcomes | -| `ReturningUser` | Boolean indicating if the user is a returning user | | -| `SessionId` | Unique identifier for the session | | -| `UTMCampaign` | UTM campaign parameter | | -| `UTMMedium` | UTM medium parameter | | -| `UTMSource` | UTM source parameter | | +| `ReturningUser` | Boolean indicating if the user is a returning user | +| `SessionId` | Unique identifier for the session | +| `UTMCampaign` | UTM campaign parameter | +| `UTMMedium` | UTM medium parameter | +| `UTMSource` | UTM source parameter | ## Adding Destinations -Now that your Source is set up, you can connect it with Destinations. +Now that your Source is set up, you can connect to Destinations. 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. From 31ca014ceb1957f3073e79b1bc4dd9f08f8c0ebc Mon Sep 17 00:00:00 2001 From: Annie Zhao Date: Thu, 12 Sep 2024 14:32:39 -0700 Subject: [PATCH 05/17] Update redshift privatelink step --- src/connections/aws-privatelink.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/aws-privatelink.md b/src/connections/aws-privatelink.md index d099c5187f..8caddde756 100644 --- a/src/connections/aws-privatelink.md +++ b/src/connections/aws-privatelink.md @@ -60,7 +60,7 @@ If any updates are made to the Availability Zones (AZs) enabled for your NLB, pl ### Configure PrivateLink for Redshift Implement Segment's PrivateLink integration by taking the following steps: 1. Let your Customer Success Manager (CSM) know that you're interested in PrivateLink. They will share information with you about Segment’s Edge account and VPC. -2. After you receive the Edge account ID and VPC ID, [grant cluster access to Segment's Edge account and VPC](https://docs.aws.amazon.com/redshift/latest/gsg/rs-gsg-connect-to-cluster.html){:target="_blank”}. +2. After you receive the Edge account ID and VPC ID, [grant cluster access to Segment's Edge account and VPC](https://docs.aws.amazon.com/redshift/latest/mgmt/managing-cluster-cross-vpc-console-grantor.html){:target="_blank”}. 3. Reach back out to your CSM and provide them with the Cluster identifier for your cluster and your AWS account ID. 4. Segment creates a Redshift managed VPC endpoint within the Segment Redshift subnet on your behalf, which creates a PrivateLink Endpoint URL. Segment then provides you with the internal PrivateLink Endpoint URL. 5. After Segment provides you with the URL, use it to update or create new Redshift integrations. The following integrations support PrivateLink: From 8809823c098b9a50183c3b7b64f77c2d478e66db Mon Sep 17 00:00:00 2001 From: Niall Date: Fri, 13 Sep 2024 14:16:29 +0100 Subject: [PATCH 06/17] fix text deleted by mistake --- src/connections/spec/common.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/spec/common.md b/src/connections/spec/common.md index e044908df9..ddb5475e83 100644 --- a/src/connections/spec/common.md +++ b/src/connections/spec/common.md @@ -258,7 +258,7 @@ Every API call has four timestamps, `originalTimestamp`, `timestamp`, `sentAt`, | Timestamp | Calculated | Description | | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `originalTimestamp` | Time on the client device when call was invoked
**OR**
The `timestamp` value manually passed in through server-side libraries. | Used by Segment to calculate `timestamp`.

**Note:** `originalTimestamp` is not useful for analysis since it's not always trustworthy as it can be easily adjusted and affected by clock skew. | -| `sentAt` | Time on client device when call was sent.
**OR**
`sentAt` value manually passed in. | Used by Segment to calculate `timestamp`.

**Note:** `sentAt` is not useful for analysis since it's not always by clock skew. | +| `sentAt` | Time on client device when call was sent.
**OR**
`sentAt` value manually passed in. | Used by Segment to calculate `timestamp`.

**Note:** `sentAt` is not useful for analysis since it's not always trustworthy as it can be easily adjusted and affected by clock skew. | | `receivedAt` | Time on Segment server clock when call was received | Used by Segment to calculate `timestamp`, and used as sort key in Warehouses.

**Note:** For max query speed, `receivedAt` is the recommended timestamp for analysis when chronology does not matter as chronology is not ensured. | | `timestamp` | Calculated by Segment to correct client-device clock skew using the following formula:
`receivedAt` - (`sentAt` - `originalTimestamp`) | Used by Segment to send to downstream destinations, and used for historical replays.

**Note:** Recommended timestamp for analysis when chronology does matter. | From 3998fc431187ef9141f7c4cf5d87888052f9dfb5 Mon Sep 17 00:00:00 2001 From: Niall Date: Fri, 13 Sep 2024 14:21:32 +0100 Subject: [PATCH 07/17] fix text deleted by mistake --- src/connections/spec/common.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/spec/common.md b/src/connections/spec/common.md index ddb5475e83..3cd863c2db 100644 --- a/src/connections/spec/common.md +++ b/src/connections/spec/common.md @@ -258,7 +258,7 @@ Every API call has four timestamps, `originalTimestamp`, `timestamp`, `sentAt`, | Timestamp | Calculated | Description | | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `originalTimestamp` | Time on the client device when call was invoked
**OR**
The `timestamp` value manually passed in through server-side libraries. | Used by Segment to calculate `timestamp`.

**Note:** `originalTimestamp` is not useful for analysis since it's not always trustworthy as it can be easily adjusted and affected by clock skew. | -| `sentAt` | Time on client device when call was sent.
**OR**
`sentAt` value manually passed in. | Used by Segment to calculate `timestamp`.

**Note:** `sentAt` is not useful for analysis since it's not always trustworthy as it can be easily adjusted and affected by clock skew. | +| `sentAt` | Time on client device when call was sent.
**OR**
`sentAt` value manually passed in. | Used by Segment to calculate `timestamp`.

**Note:** `sentAt` is not useful for analysis since it's not always trustworthy as it can be easily adjusted and affected by clock skew. | | `receivedAt` | Time on Segment server clock when call was received | Used by Segment to calculate `timestamp`, and used as sort key in Warehouses.

**Note:** For max query speed, `receivedAt` is the recommended timestamp for analysis when chronology does not matter as chronology is not ensured. | | `timestamp` | Calculated by Segment to correct client-device clock skew using the following formula:
`receivedAt` - (`sentAt` - `originalTimestamp`) | Used by Segment to send to downstream destinations, and used for historical replays.

**Note:** Recommended timestamp for analysis when chronology does matter. | From 02427fb8a51910cf63b0371a823310dceb394872 Mon Sep 17 00:00:00 2001 From: prigiattiperrut <47340158+prigiattiperrut@users.noreply.github.com> Date: Fri, 13 Sep 2024 15:18:44 +0100 Subject: [PATCH 08/17] Update index.md --- .../sources/catalog/libraries/website/javascript/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/sources/catalog/libraries/website/javascript/index.md b/src/connections/sources/catalog/libraries/website/javascript/index.md index a36ba0f3fa..5b75840e9f 100644 --- a/src/connections/sources/catalog/libraries/website/javascript/index.md +++ b/src/connections/sources/catalog/libraries/website/javascript/index.md @@ -362,7 +362,7 @@ analytics.identify("hello world") The `ready` method lets you pass in a method that gets called after Analytics.js finishes initializing and after all enabled device-mode destinations load. It's like [jQuery's `ready` method](https://api.jquery.com/ready/){:target="_blank"}, except for Destinations. Because it doesn't fire until all enabled device-mode destinations are loaded, it can't be used to change configuration options for downstream SDKs. That can only be done if the SDK is loaded natively. -The `ready` method isn't invoked if any Destination throws an error (for example, for an expired API key, incorrect settings configuration, or when a Destination is blocked by the browser) during initialization. If you're looking to detect when Analytics.js has loaded, instead of using the `ready` method, you can listen for the `initialize` event to be emitted (`window.analytics.initialized`). This event returns `true` even when a destination is blocked. +The `ready` method isn't invoked if any Destination throws an error (for example, for an expired API key, incorrect settings configuration, or when a Destination is blocked by the browser) during initialization. If you want to check when Analytics.js has loaded, you can look at the value of `window.analytics.initialized`. When it’s true, the library has successfully initialized, even if some destinations are blocked. Please note, window.analytics.initialized is a simple boolean, not an event or a pub/sub system. This means you can't subscribe to changes in its value. If you need to detect when it changes from false to true, you’ll need to set up a polling mechanism to monitor the value. The code in the `ready` function only executes after `ready` is emitted. From 3e77b9f566d3ec40b68eff4b9c1360cd5becf70b Mon Sep 17 00:00:00 2001 From: Annie Zhao Date: Fri, 13 Sep 2024 09:44:09 -0700 Subject: [PATCH 09/17] Include new region offerings --- src/connections/aws-privatelink.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/aws-privatelink.md b/src/connections/aws-privatelink.md index 8caddde756..299d0a57a3 100644 --- a/src/connections/aws-privatelink.md +++ b/src/connections/aws-privatelink.md @@ -5,7 +5,7 @@ title: Amazon Web Services PrivateLink [Amazon Web Services' PrivateLink](https://aws.amazon.com/privatelink/){:target="_blank”} is an AWS service that provides private connectivity between VPCs without exposing traffic to the public Internet. Keeping traffic in the Amazon network reduces the data security risk associated with exposing your Warehouse traffic to the Internet. > info "" -> Segment's PrivateLink integration is currently in private beta and is governed by Segment’s [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank”}. Only warehouses located in region `us-east-1` are eligible for PrivateLink. You might incur additional networking costs while using AWS PrivateLink. +> Segment's PrivateLink integration is currently in private beta and is governed by Segment’s [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank”}. Only warehouses located in regions `us-east-1`, `us-west-`, or `eu-west-1` are eligible for PrivateLink. You might incur additional networking costs while using AWS PrivateLink. During the Private Beta, you can set up AWS PrivateLink for [Databricks](#databricks), [RDS Postgres](#rds-postgres), and [Redshift](#redshift). From d880e0c814da9e83e0069f094e8d55b553e97936 Mon Sep 17 00:00:00 2001 From: Annie Zhao Date: Fri, 13 Sep 2024 09:57:36 -0700 Subject: [PATCH 10/17] Fix region --- src/connections/aws-privatelink.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/aws-privatelink.md b/src/connections/aws-privatelink.md index 299d0a57a3..851f5470b8 100644 --- a/src/connections/aws-privatelink.md +++ b/src/connections/aws-privatelink.md @@ -5,7 +5,7 @@ title: Amazon Web Services PrivateLink [Amazon Web Services' PrivateLink](https://aws.amazon.com/privatelink/){:target="_blank”} is an AWS service that provides private connectivity between VPCs without exposing traffic to the public Internet. Keeping traffic in the Amazon network reduces the data security risk associated with exposing your Warehouse traffic to the Internet. > info "" -> Segment's PrivateLink integration is currently in private beta and is governed by Segment’s [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank”}. Only warehouses located in regions `us-east-1`, `us-west-`, or `eu-west-1` are eligible for PrivateLink. You might incur additional networking costs while using AWS PrivateLink. +> Segment's PrivateLink integration is currently in private beta and is governed by Segment’s [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank”}. Only warehouses located in regions `us-east-1`, `us-west-2`, or `eu-west-1` are eligible for PrivateLink. You might incur additional networking costs while using AWS PrivateLink. During the Private Beta, you can set up AWS PrivateLink for [Databricks](#databricks), [RDS Postgres](#rds-postgres), and [Redshift](#redshift). From 75e19dcc57a8deae0676d4fbc2dfdadcb792a247 Mon Sep 17 00:00:00 2001 From: eren-quinengine Date: Mon, 16 Sep 2024 11:13:20 +0300 Subject: [PATCH 11/17] Adjust documentation for Quin AI source integration --- .../catalog/cloud-apps/quin-ai/index.md | 76 +++++++++---------- 1 file changed, 38 insertions(+), 38 deletions(-) diff --git a/src/connections/sources/catalog/cloud-apps/quin-ai/index.md b/src/connections/sources/catalog/cloud-apps/quin-ai/index.md index 57aaf9663e..a11fa4c8e3 100644 --- a/src/connections/sources/catalog/cloud-apps/quin-ai/index.md +++ b/src/connections/sources/catalog/cloud-apps/quin-ai/index.md @@ -26,50 +26,50 @@ The default behavior is for Quin AI to pass the event data associated with the a 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. -| Event Name | Description | -|--------------------|------------------------------------| -| pageview | Get an action after viewing a page | -| click | Get an action after a click | +| Event Name | Description | +|------------|------------------------------------| +| Page View | Get an action after viewing a page | +| Click | Get an action after a click | ## Event Properties The table below list the properties included in the events listed above. -| Property Name | Description | -|----------------------------|-------------------------------------------------------------| -| `ActionAudienceId` | ID of the target audience for the action | -| `ActionControlGroup` | Boolean indicating if the action is part of a control group | -| `ActionId` | Unique identifier for the action | -| `ActionIsCustom` | Boolean indicating if the action is custom | -| `ActionName` | Name of the action | -| `ActionType` | Type of the action | -| `BasketPrice` | Total price of the items in the basket | -| `BasketQuantity` | Total quantity of items in the basket | -| `EventAction` | Type of event action (e.g., pageview, click) | -| `EventCategory` | Category of the event | -| `EventCount` | Number of events | -| `EventCustomAttributes` | Map of custom attributes associated with the event | -| `EventDuration` | Duration of the event in seconds | -| `EventLabel` | Label of the event | -| `EventPlatform` | Platform on which the event occurred (e.g., web, mobile) | -| `EventTimestamp` | Timestamp when the event occurred | -| `EventURL` | URL associated with the event | -| `GoogleClientId` | Google Analytics client ID | -| `ItemCategory` | Category of the item | -| `ItemCurrency` | Currency of the item price (e.g., TRY) | -| `ItemCustomAttributes` | Map of custom attributes associated with the item | -| `ItemId` | Unique identifier for the item | -| `ItemName` | Name of the item | -| `ItemPrice` | Price of the item | -| `MostVisitedCategory` | List of most visited categories | -| `MostVisitedCategoryCount` | Number of times the most visited categories were visited | -| `Prediction` | Map of prediction probabilities for various outcomes | -| `ReturningUser` | Boolean indicating if the user is a returning user | -| `SessionId` | Unique identifier for the session | -| `UTMCampaign` | UTM campaign parameter | -| `UTMMedium` | UTM medium parameter | -| `UTMSource` | UTM source parameter | +| Property Name | Description | +|-------------------------------|-------------------------------------------------------------| +| `action_audience_id` | ID of the target audience for the action | +| `action_control_group` | Boolean indicating if the action is part of a control group | +| `action_id` | Unique identifier for the action | +| `action_is_custom` | Boolean indicating if the action is custom | +| `action_name` | Name of the action | +| `action_type` | Type of the action | +| `basket_price` | Total price of the items in the basket | +| `basket_quantity` | Total quantity of items in the basket | +| `event_action` | Type of event action (e.g., pageview, click) | +| `event_category` | Category of the event | +| `event_count` | Number of events | +| `event_custom_attributes` | Map of custom attributes associated with the event | +| `evet_duration` | Duration of the event in seconds | +| `event_label` | Label of the event | +| `event_platform` | Platform on which the event occurred (e.g., web, mobile) | +| `event_timestamp` | Timestamp when the event occurred | +| `event_url` | URL associated with the event | +| `google_client_id` | Google Analytics client ID | +| `item_category` | Category of the item | +| `item_currency` | Currency of the item price (e.g., TRY) | +| `item_custom_attributes` | Map of custom attributes associated with the item | +| `item_id` | Unique identifier for the item | +| `item_name` | Name of the item | +| `item_price` | Price of the item | +| `most_visited_category` | List of most visited categories | +| `most_visited_category_count` | Number of times the most visited categories were visited | +| `prediction` | Map of prediction probabilities for various outcomes | +| `returning_user` | Boolean indicating if the user is a returning user | +| `session_id` | Unique identifier for the session | +| `utm_campaign` | UTM campaign parameter | +| `utm_mdedium` | UTM medium parameter | +| `utm_source` | UTM source parameter | ## Adding Destinations From 61b12754fa8f130c6df66293c10e6d60d27d81ba Mon Sep 17 00:00:00 2001 From: eren-quinengine Date: Mon, 16 Sep 2024 15:56:13 +0300 Subject: [PATCH 12/17] Adjust documentation for Quin AI source integration --- .../catalog/cloud-apps/quin-ai/index.md | 20 ++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/src/connections/sources/catalog/cloud-apps/quin-ai/index.md b/src/connections/sources/catalog/cloud-apps/quin-ai/index.md index a11fa4c8e3..e01d94a8a7 100644 --- a/src/connections/sources/catalog/cloud-apps/quin-ai/index.md +++ b/src/connections/sources/catalog/cloud-apps/quin-ai/index.md @@ -1,7 +1,9 @@ +--- +title: Quin AI Source +id: WGp9SQFRVu +--- -### Quin AI Source - -Quin AI is the first deep learning, real-time behavior prediction system dedicated to e-commerce conversion optimization, for growth and profitability. +Quin AI is the first deep learning, real-time behavior prediction system dedicated to e-commerce conversion optimization for growth and profitability. This source is maintained by Quin Audience Engine. For any issues with the source, [contact the Quin Audience Engine Support team](mailto:hello@quinengine.com). @@ -10,21 +12,21 @@ This source is maintained by Quin Audience Engine. For any issues with the sourc 1. From your workspace's Source page, click **Add Source**. 2. Search for "Quin AI" in the Sources Catalog, select Quin AI, and click **Add Source**. 3. On the next screen, give the Source a name configure any other settings. - - 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). + - 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). 4. Click **Add Source** to save your settings. 5. Copy the Write key from the Segment UI. -6. Log in to your [Quin account](https://portal.quinengine.com/) and navigate to Integrations > Segment > Settings. +6. Log in to your [Quin account](https://portal.quinengine.com/){:target="_blank”} and navigate to Integrations > Segment > Settings. 7. On the Settings page, paste your Segment write key to connect. ## Stream -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. +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. -The default behavior is for Quin AI to pass the event data associated with the anonymous userId. +The default behavior is for Quin AI to pass the event data associated with the anonymousId. ## Events -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. +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. | Event Name | Description | |------------|------------------------------------| @@ -78,4 +80,4 @@ Now that your Source is set up, you can connect to Destinations. 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 there are any issues with how the events are arriving to Segment, [contact the Quin AI support team](mailto:hello@ Date: Mon, 16 Sep 2024 17:06:39 +0300 Subject: [PATCH 13/17] Adjust documentation for Quin AI source integration --- src/connections/sources/catalog/cloud-apps/quin-ai/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/sources/catalog/cloud-apps/quin-ai/index.md b/src/connections/sources/catalog/cloud-apps/quin-ai/index.md index e01d94a8a7..3ce742eed1 100644 --- a/src/connections/sources/catalog/cloud-apps/quin-ai/index.md +++ b/src/connections/sources/catalog/cloud-apps/quin-ai/index.md @@ -12,10 +12,10 @@ This source is maintained by Quin Audience Engine. For any issues with the sourc 1. From your workspace's Source page, click **Add Source**. 2. Search for "Quin AI" in the Sources Catalog, select Quin AI, and click **Add Source**. 3. On the next screen, give the Source a name configure any other settings. - - 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). + - 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 Segment recommends using something that reflects the source itself and distinguishes amongst your environments (eg. QuinAI_Prod, QuinAI_Staging, QuinAI_Dev). 4. Click **Add Source** to save your settings. 5. Copy the Write key from the Segment UI. -6. Log in to your [Quin account](https://portal.quinengine.com/){:target="_blank”} and navigate to Integrations > Segment > Settings. +6. 6. Log in to your [Quin account](https://portal.quinengine.com/){:target="_blank”} and navigate to **Integrations > Segment > Settings**. 7. On the Settings page, paste your Segment write key to connect. ## Stream From 079e31f45bb41012a886a13328706b4f4c4576f4 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Mon, 16 Sep 2024 11:13:56 -0400 Subject: [PATCH 14/17] Apply suggestions from code review --- .../sources/catalog/libraries/website/javascript/index.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/connections/sources/catalog/libraries/website/javascript/index.md b/src/connections/sources/catalog/libraries/website/javascript/index.md index 5b75840e9f..1dc5df0565 100644 --- a/src/connections/sources/catalog/libraries/website/javascript/index.md +++ b/src/connections/sources/catalog/libraries/website/javascript/index.md @@ -362,7 +362,9 @@ analytics.identify("hello world") The `ready` method lets you pass in a method that gets called after Analytics.js finishes initializing and after all enabled device-mode destinations load. It's like [jQuery's `ready` method](https://api.jquery.com/ready/){:target="_blank"}, except for Destinations. Because it doesn't fire until all enabled device-mode destinations are loaded, it can't be used to change configuration options for downstream SDKs. That can only be done if the SDK is loaded natively. -The `ready` method isn't invoked if any Destination throws an error (for example, for an expired API key, incorrect settings configuration, or when a Destination is blocked by the browser) during initialization. If you want to check when Analytics.js has loaded, you can look at the value of `window.analytics.initialized`. When it’s true, the library has successfully initialized, even if some destinations are blocked. Please note, window.analytics.initialized is a simple boolean, not an event or a pub/sub system. This means you can't subscribe to changes in its value. If you need to detect when it changes from false to true, you’ll need to set up a polling mechanism to monitor the value. +The `ready` method isn't invoked if any Destination throws an error (for example, for an expired API key, incorrect settings configuration, or when a Destination is blocked by the browser) during initialization. If you want to check when Analytics.js has loaded, you can look at the value of `window.analytics.initialized`. When it’s true, the library has successfully initialized, even if some destinations are blocked. + +**Note**: `window.analytics.initialized` is a simple boolean, not an event or a pub/sub system. This means you can't subscribe to changes in its value. If you need to detect when it changes from `false` to `true`, you must set up a polling mechanism to monitor the value. The code in the `ready` function only executes after `ready` is emitted. From fff5022f359c6d3e86048364a5799e11064c9dee Mon Sep 17 00:00:00 2001 From: stayseesong <83784848+stayseesong@users.noreply.github.com> Date: Mon, 16 Sep 2024 13:10:15 -0700 Subject: [PATCH 15/17] Update src/privacy/user-deletion-and-suppression.md --- src/privacy/user-deletion-and-suppression.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/privacy/user-deletion-and-suppression.md b/src/privacy/user-deletion-and-suppression.md index 7ac0062c44..84b7488d31 100644 --- a/src/privacy/user-deletion-and-suppression.md +++ b/src/privacy/user-deletion-and-suppression.md @@ -71,7 +71,7 @@ Note that list only includes `SUPPRESS_ONLY` regulations. If you created a User To create a suppression regulation and add a `userId` to this list, click **Suppress New User**, and enter the `userId` in the field that appears. Then click **Request Suppression**. -Segment creates a `SUPPRESS` regulation, and adds the `userId` to your suppression list, mostly processed within 24 hours. In some cases, the suppression request can take up to 30 days to process. You can suppress up to 5000 userIds per call via Public API. +Segment creates a `SUPPRESS` regulation, and adds the `userId` to your suppression list, mostly processed within 24 hours. In some cases, the suppression request can take up to 30 days to process. You can suppress up to 5000 userIds per call through the Public API. ### Remove a user from the suppression list From 3cd9339590de1b654790620737f09da6e5d3c5f6 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 17 Sep 2024 11:56:37 -0400 Subject: [PATCH 16/17] Update src/connections/spec/common.md --- src/connections/spec/common.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/spec/common.md b/src/connections/spec/common.md index 3cd863c2db..e664aed2b3 100644 --- a/src/connections/spec/common.md +++ b/src/connections/spec/common.md @@ -139,7 +139,7 @@ Context is a dictionary of extra information that provides useful context about | `active` | Boolean | Whether a user is active.

This is usually used to flag an `.identify()` call to just update the traits but not "last seen." | | `app` | Object | dictionary of information about the current application, containing `name`, `version`, and `build`.

This is collected automatically from the mobile libraries when possible. | | `campaign` | Object | Dictionary of information about the campaign that resulted in the API call, containing `name`, `source`, `medium`, `term`, `content`, and any other custom UTM parameter.

This maps directly to the common UTM campaign parameters. | -| `device` | Object | Dictionary of information about the device, containing `id`, `advertisingId`, `manufacturer`, `model`, `name`, `type`, and `version`.

**Note:** `model` for iOS may not exactly correspond to an iPhone model number. For example, an `iPhone 15 Pro Max` has a model number of `iPhone16,2`. These values are set by iOS. | +| `device` | Object | Dictionary of information about the device, containing `id`, `advertisingId`, `manufacturer`, `model`, `name`, `type`, and `version`.

**Note:** If you collect information about iOS devices, note that the `model` value set by Apple might not exactly correspond to an iPhone model number. For example, an `iPhone 15 Pro Max` has a `model` value of `iPhone16,2`. | | `ip` | String | Current user's IP address. | | `library` | Object | Dictionary of information about the library making the requests to the API, containing `name` and `version`. | | `locale` | String | Locale string for the current user, for example `en-US`. | From 94b2a2ba9f8e7061ac020acc5d5d679ca8db4ba4 Mon Sep 17 00:00:00 2001 From: pwseg Date: Tue, 17 Sep 2024 13:14:58 -0500 Subject: [PATCH 17/17] catalog update --- src/_data/catalog/destination_categories.yml | 2 +- src/_data/catalog/destinations.yml | 130 +++++++++---------- src/_data/catalog/destinations_private.yml | 2 +- src/_data/catalog/regional-supported.yml | 9 ++ src/_data/catalog/source_categories.yml | 2 +- src/_data/catalog/sources.yml | 22 +++- 6 files changed, 98 insertions(+), 69 deletions(-) diff --git a/src/_data/catalog/destination_categories.yml b/src/_data/catalog/destination_categories.yml index f06995b16f..092861b7a8 100644 --- a/src/_data/catalog/destination_categories.yml +++ b/src/_data/catalog/destination_categories.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# destination categories last updated 2024-09-12 +# destination categories last updated 2024-09-17 items: - display_name: A/B Testing slug: a-b-testing diff --git a/src/_data/catalog/destinations.yml b/src/_data/catalog/destinations.yml index 1252cae10a..9f80a84af3 100644 --- a/src/_data/catalog/destinations.yml +++ b/src/_data/catalog/destinations.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# destination data last updated 2024-09-12 +# destination data last updated 2024-09-17 items: - id: 637e8d185e2dec264895ea89 display_name: 1Flow @@ -57151,7 +57151,7 @@ items: hidden: false defaultTrigger: event = "updated" or event = "new" fields: - - id: ob9uczev9JQwvr2qn1pwos + - id: eVUh5No6HC6JLnJFDESZBN sortOrder: 0 fieldKey: record_identifier label: Record Identifier @@ -57166,7 +57166,7 @@ items: dynamic: false allowNull: false hidden: false - - id: iYHn1zLcAXefPcDmYSbrWG + - id: hNKpTfo7wPvo3W25NDxkq2 sortOrder: 2 fieldKey: spreadsheet_id label: Spreadsheet ID @@ -57183,7 +57183,7 @@ items: dynamic: false allowNull: false hidden: false - - id: gEtw7nseVKHXHRULB3oLSY + - id: udYnVfwPGro8ZFBEGzg3uC sortOrder: 3 fieldKey: spreadsheet_name label: Spreadsheet Name @@ -57200,7 +57200,7 @@ items: dynamic: false allowNull: false hidden: false - - id: iAsmY9nGZtHtHJ4fXvrpck + - id: uNgDLL7fSgj1cvfAkizPMq sortOrder: 4 fieldKey: data_format label: Data Format @@ -57224,7 +57224,7 @@ items: dynamic: false allowNull: false hidden: false - - id: wmCfxsUh1piWcugvvKoxwT + - id: veT2tCVuDzQ7N6JXVzAHqs sortOrder: 5 fieldKey: fields label: Fields @@ -57247,7 +57247,7 @@ items: dynamic: false allowNull: false hidden: false - - id: ryHB4sxoEtCpNFER38u74V + - id: v9hQvbLs6yZgVygQTLUXrb sortOrder: 6 fieldKey: enable_batching label: Batch Data to Google Sheets @@ -57271,7 +57271,7 @@ items: hidden: false defaultTrigger: event = "updated" or event = "new" fields: - - id: 5tSMqy3ehomxjp4i3Kz7BA + - id: gpPUgyoYS5JuVgqY9boJ7H sortOrder: 0 fieldKey: record_identifier label: Record Identifier @@ -57285,7 +57285,7 @@ items: choices: null dynamic: false allowNull: false - - id: hWxt1cyMckuVMUkZffVSuT + - id: 7AQUBRhhkFiAh65gfMb45o sortOrder: 1 fieldKey: spreadsheet_id label: Spreadsheet ID @@ -57301,7 +57301,7 @@ items: choices: null dynamic: false allowNull: false - - id: wchxabRTr1Fgax8XTQqccb + - id: qg8MnAYPLAhv2GUw5Gz35J sortOrder: 2 fieldKey: spreadsheet_name label: Spreadsheet Name @@ -57317,7 +57317,7 @@ items: choices: null dynamic: false allowNull: false - - id: gFWZLekb2CFfzL9vz46X9v + - id: xaBag6fibBdAVFtYdWzKo5 sortOrder: 3 fieldKey: data_format label: Data Format @@ -57340,7 +57340,7 @@ items: value: USER_ENTERED dynamic: false allowNull: false - - id: wcMpHcrYSo1yWeCF8YtT4U + - id: dgquPwzAcMEruR1F9a9Xxr sortOrder: 4 fieldKey: fields label: Fields @@ -57362,7 +57362,7 @@ items: choices: null dynamic: false allowNull: false - - id: 8Z6jGQ82uyVjtGbjf2NzPn + - id: pg39kFzTwgBiWb3fhgp485 sortOrder: 5 fieldKey: enable_batching label: Batch Data to Google Sheets @@ -58812,7 +58812,7 @@ items: hidden: false defaultTrigger: type = "track" fields: - - id: bdP65buKAm47gumo3giXpC + - id: d1PJdezkc7DV1ZR16cwtLV sortOrder: 0 fieldKey: eventName label: Event Name @@ -58830,7 +58830,7 @@ items: choices: null dynamic: true allowNull: false - - id: j4G2wQBuUR3EtZkWiaxodr + - id: dTb68ddbJSP7WF2HZ4gW6i sortOrder: 1 fieldKey: occurredAt label: Event Timestamp @@ -58846,7 +58846,7 @@ items: choices: null dynamic: false allowNull: false - - id: 9zZJCoanVLKtiUafmues6N + - id: 2SzRNyByzZ3ywuxcGkyYT1 sortOrder: 2 fieldKey: email label: Email Address @@ -58868,7 +58868,7 @@ items: choices: null dynamic: false allowNull: false - - id: sBRaKHkXSESz345sAAVbfc + - id: utwgG6yWobRtGSkG5hsPox sortOrder: 3 fieldKey: utk label: User Token @@ -58882,7 +58882,7 @@ items: choices: null dynamic: false allowNull: false - - id: dNLsoSRt9aXa6HFwaN8tA5 + - id: qgYf4DHyTv3VpVfJct41SL sortOrder: 4 fieldKey: objectId label: Object ID @@ -58897,7 +58897,7 @@ items: choices: null dynamic: false allowNull: false - - id: jJFPKpkep7eAsxUysVekXg + - id: cedAboYx9M3fN7MCEfxbmc sortOrder: 5 fieldKey: properties label: Event Properties @@ -58922,7 +58922,7 @@ items: hidden: false defaultTrigger: null fields: - - id: hcucFBiEgMCECjJfPLJEQ4 + - id: e2bZHtAb14WkpCp19rVWVv sortOrder: 0 fieldKey: createNewCustomRecord label: Create Custom Object Record if Not Found @@ -58939,7 +58939,7 @@ items: choices: null dynamic: false allowNull: false - - id: 7KU1pkoi3ShJUDs67eevT9 + - id: pM8jbhqbtbNo6mPbnhtAgL sortOrder: 1 fieldKey: customObjectSearchFields label: Custom Object Search Fields @@ -58954,7 +58954,7 @@ items: choices: null dynamic: false allowNull: false - - id: 7KGcGgdNyUd8Wa1sqo4nLS + - id: aYQ2tX2tXDNeqrBNntVSLa sortOrder: 2 fieldKey: objectType label: Object Type @@ -58972,7 +58972,7 @@ items: choices: null dynamic: true allowNull: false - - id: 3otM6PDBzi8vGuwC63hVD4 + - id: fWZFRPJyKAMSxjQYnz8A3V sortOrder: 3 fieldKey: properties label: Properties @@ -58990,7 +58990,7 @@ items: choices: null dynamic: false allowNull: false - - id: 6LN21bLfUnhJcqbba2josy + - id: qrD6YFJPWbU5gedbVnuFqD sortOrder: 4 fieldKey: searchFieldsToAssociateCustomObjects label: Search Fields to Associate custom Object @@ -59006,7 +59006,7 @@ items: choices: null dynamic: false allowNull: false - - id: 4KRhUvLRCVo2r3t6yQNZaa + - id: 8J59sWsKYS7tvrJWf2pbRw sortOrder: 5 fieldKey: toObjectType label: ObjectType to associate @@ -59024,7 +59024,7 @@ items: choices: null dynamic: true allowNull: false - - id: mjeFiejStfJBPPyzs44J1t + - id: e2QUatT9zypFPKrrCKsT7s sortOrder: 6 fieldKey: associationLabel label: Association Label @@ -59044,7 +59044,7 @@ items: hidden: false defaultTrigger: type = "identify" fields: - - id: 7hcWbXeZNJRXk3XPSuu6XJ + - id: 4xS4s1ZaekfVKyXg1PFcsj sortOrder: 0 fieldKey: email label: Email @@ -59062,7 +59062,7 @@ items: choices: null dynamic: false allowNull: false - - id: nJZRkb4bB4xkDdvwZeh73s + - id: kuuzVs16ySb5R3CupTfKSj sortOrder: 1 fieldKey: company label: Company Name @@ -59076,7 +59076,7 @@ items: choices: null dynamic: false allowNull: false - - id: vQpTmXLd1jc6rbVhmB6xrZ + - id: oKRUsWrVTTmnbg7RBZ42YG sortOrder: 2 fieldKey: firstname label: First Name @@ -59096,7 +59096,7 @@ items: choices: null dynamic: false allowNull: false - - id: z3jib5SH5HSusty1ZGSuv + - id: sMjSUHoGQjtJrjxhfPjYwh sortOrder: 3 fieldKey: lastname label: Last Name @@ -59116,7 +59116,7 @@ items: choices: null dynamic: false allowNull: false - - id: esPuSManaRVMNw2iCSAXMT + - id: wHJqNghwgFHhYa9SshiE9i sortOrder: 4 fieldKey: phone label: Phone @@ -59130,7 +59130,7 @@ items: choices: null dynamic: false allowNull: false - - id: sjfg2qJWYykUh9f1oaSTeE + - id: gNTuZ9TextNg4kZEEbTbKA sortOrder: 5 fieldKey: address label: Street Address @@ -59144,7 +59144,7 @@ items: choices: null dynamic: false allowNull: false - - id: gTqMwdiwE9CxmrtwBjhdsZ + - id: 5Qnk2e5Maky94miag5oyxi sortOrder: 6 fieldKey: city label: City @@ -59158,7 +59158,7 @@ items: choices: null dynamic: false allowNull: false - - id: 5wsniTwu2VxNuhy43ZmzB6 + - id: n5PVRhQB4Wq9XBKEDgmUrW sortOrder: 7 fieldKey: state label: State @@ -59172,7 +59172,7 @@ items: choices: null dynamic: false allowNull: false - - id: oMM1cqZqQz4gKeCHrFQhtw + - id: r7EkcA3eyUzquttGpdcw5X sortOrder: 8 fieldKey: country label: Country @@ -59186,7 +59186,7 @@ items: choices: null dynamic: false allowNull: false - - id: bvbRi24XkYy2M7XJYCeC5T + - id: aHkUeYor3AyKefzzpLqjR4 sortOrder: 9 fieldKey: zip label: Postal Code @@ -59206,7 +59206,7 @@ items: choices: null dynamic: false allowNull: false - - id: b7cuaNx4qSDjojLHnNK81W + - id: wsGC8tVstMhmUimBoy26VB sortOrder: 10 fieldKey: website label: Website @@ -59220,7 +59220,7 @@ items: choices: null dynamic: false allowNull: false - - id: xj2zaAgttfhUphy7MpMZVq + - id: hNnymayknYWduHTZBphxNV sortOrder: 11 fieldKey: lifecyclestage label: Lifecycle Stage @@ -59236,7 +59236,7 @@ items: choices: null dynamic: false allowNull: false - - id: cvMNMgjW6WjurEchBv8nZN + - id: g1zbWzhqu2HrtmocqX1Gg2 sortOrder: 12 fieldKey: properties label: Other properties @@ -59254,7 +59254,7 @@ items: choices: null dynamic: false allowNull: false - - id: kVwAVu13b2FxDhpdgnBX55 + - id: mrPoYwJq6B9hmNXGMiDR4t sortOrder: 13 fieldKey: enable_batching label: Send Batch Data to HubSpot @@ -59279,7 +59279,7 @@ items: hidden: false defaultTrigger: type = "group" fields: - - id: vfL2uNSrsAYtgHqP7UFeuL + - id: irDHR1foyihZj5nNw1jmtg sortOrder: 0 fieldKey: groupid label: Unique Company Identifier @@ -59303,7 +59303,7 @@ items: choices: null dynamic: false allowNull: false - - id: rU1rW627jrptLPVpz6DPjw + - id: w2SMDdWrf5w6Q3e6GeqwEQ sortOrder: 1 fieldKey: createNewCompany label: Create Company if Not Found @@ -59320,7 +59320,7 @@ items: choices: null dynamic: false allowNull: false - - id: 3H5YHGG87tHQdsgA1CHH5S + - id: vCEEJbdJjoBc4jQPt721i3 sortOrder: 2 fieldKey: associateContact label: Associate Contact with Company @@ -59339,7 +59339,7 @@ items: choices: null dynamic: false allowNull: false - - id: jWQQWwuhtBqwVGPNES4MiY + - id: mdoJHgfVn9qQcxvVVR8R2k sortOrder: 3 fieldKey: companysearchfields label: Company Search Fields @@ -59356,7 +59356,7 @@ items: choices: null dynamic: false allowNull: false - - id: 36vnAVMv1kVNJGHp3Ff3fW + - id: j4DpFd8mdJdntbAC8XgrcM sortOrder: 4 fieldKey: name label: Company Name @@ -59370,7 +59370,7 @@ items: choices: null dynamic: false allowNull: false - - id: tD7uLeMBXz6moKrHfrFjZc + - id: 21fC53gX22MiAzoLY7qAjq sortOrder: 5 fieldKey: description label: Company Description @@ -59384,7 +59384,7 @@ items: choices: null dynamic: false allowNull: false - - id: n9DpLGnxssLcCv6XmgYDiX + - id: gkRUADqvo5ASRjEkELZ7oA sortOrder: 6 fieldKey: address label: Street Address @@ -59398,7 +59398,7 @@ items: choices: null dynamic: false allowNull: false - - id: 89df6WSQHHC7HtMDZedjyL + - id: jZKXPdStRXXjrcfuY4DVKX sortOrder: 7 fieldKey: city label: City @@ -59412,7 +59412,7 @@ items: choices: null dynamic: false allowNull: false - - id: czww5LkZzK961Wn6dWJPCC + - id: mpcQMYjg8K6Gx9mbpbTPov sortOrder: 8 fieldKey: state label: State @@ -59426,7 +59426,7 @@ items: choices: null dynamic: false allowNull: false - - id: 31atMSbX8Cy7egcnojBfG2 + - id: 6tPQTdEXQcmz3m1FGMmbEr sortOrder: 9 fieldKey: zip label: Postal Code @@ -59446,7 +59446,7 @@ items: choices: null dynamic: false allowNull: false - - id: mkaPuPxtoDKKZDKxZKm5xf + - id: ovG64hZcZWS2rCDZr3uS3K sortOrder: 10 fieldKey: domain label: Domain @@ -59460,7 +59460,7 @@ items: choices: null dynamic: false allowNull: false - - id: aiyuJi8WUHyGWfpf8wGPMf + - id: hpfmnCzaXWCbiS7PGPpyTV sortOrder: 11 fieldKey: phone label: Phone @@ -59474,7 +59474,7 @@ items: choices: null dynamic: false allowNull: false - - id: 99iadF5vDjtHeRa2VMeb6Y + - id: sG5toTkGNAieomtb4jJ77E sortOrder: 12 fieldKey: numberofemployees label: Number of Employees @@ -59488,7 +59488,7 @@ items: choices: null dynamic: false allowNull: false - - id: oW8v9CtBjNqmhE9bN9VBS4 + - id: n2FY9A6yoWZwxXwptAM3TL sortOrder: 13 fieldKey: industry label: Industry @@ -59502,7 +59502,7 @@ items: choices: null dynamic: false allowNull: false - - id: um1mzk7bHqWEX1AndRzYzC + - id: ky9tagcgYk8CYizUYmaRk7 sortOrder: 14 fieldKey: lifecyclestage label: Lifecycle Stage @@ -59518,7 +59518,7 @@ items: choices: null dynamic: false allowNull: false - - id: 9e3Gj8xiUmTJnKad3ntk2h + - id: 4aNzLUdz6ps9h9wrjV56Hj sortOrder: 15 fieldKey: properties label: Other Properties @@ -59548,7 +59548,7 @@ items: hidden: false defaultTrigger: null fields: - - id: 6onNRaNFypRAZYYGLdGcMh + - id: nDwFrSzZwYDBPYWYqahWfo sortOrder: 0 fieldKey: object_details label: Object Details @@ -59560,7 +59560,7 @@ items: choices: null dynamic: false allowNull: false - - id: neit3KHMYRK4barKnqgsGG + - id: gdD7sPg8g3KGeB9YqbdSRf sortOrder: 1 fieldKey: properties label: Properties @@ -59572,7 +59572,7 @@ items: choices: null dynamic: true allowNull: false - - id: fgCoGZ6dJsJtwS9L2zyYKH + - id: t9vyyZnwoCpzyPodu53G9Y sortOrder: 2 fieldKey: sensitive_properties label: Sensitive Properties @@ -59584,7 +59584,7 @@ items: choices: null dynamic: true allowNull: false - - id: 2NzrfV6g9Q3vYitYSd7Euv + - id: 7yV8398AmZzyxhN6s8aH6Y sortOrder: 3 fieldKey: association_sync_mode label: Associated Record Sync Mode @@ -59604,7 +59604,7 @@ items: value: read dynamic: false allowNull: false - - id: 3xw89jjDecGhxRbs5HRoKA + - id: e2YYohQ5LhvaM9U7AXkRZQ sortOrder: 4 fieldKey: associations label: Associations @@ -59624,7 +59624,7 @@ items: hidden: false defaultTrigger: null fields: - - id: 5f3aU3UJaPSCsKebg9rgUX + - id: pn4dYUTCBpZhvdpCcmhCHe sortOrder: 0 fieldKey: event_name label: Event Name @@ -59636,7 +59636,7 @@ items: choices: null dynamic: true allowNull: false - - id: 4T7uF24G7W69fTTnWqHLu + - id: kyRjup9nLmwWP8eS6xcGie sortOrder: 1 fieldKey: record_details label: Associated Record Details @@ -59648,7 +59648,7 @@ items: choices: null dynamic: false allowNull: false - - id: mEdo3jCu1x7CuuztvfTxGQ + - id: cMFBevUq1ojbFGYZ2uMXC7 sortOrder: 2 fieldKey: properties label: Properties @@ -59660,7 +59660,7 @@ items: choices: null dynamic: true allowNull: false - - id: 2YNqwrKaM51n8cWyYUySWz + - id: kScJ6KK99H3MA9UxmBTFwT sortOrder: 3 fieldKey: occurred_at label: Event Timestamp diff --git a/src/_data/catalog/destinations_private.yml b/src/_data/catalog/destinations_private.yml index 75a939cdda..51f55a0b11 100644 --- a/src/_data/catalog/destinations_private.yml +++ b/src/_data/catalog/destinations_private.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# destination data last updated 2024-09-12 +# destination data last updated 2024-09-17 items: - id: 54521fd925e721e32a72eee1 display_name: Pardot diff --git a/src/_data/catalog/regional-supported.yml b/src/_data/catalog/regional-supported.yml index 7d2b87c8b8..71472b6483 100644 --- a/src/_data/catalog/regional-supported.yml +++ b/src/_data/catalog/regional-supported.yml @@ -817,6 +817,15 @@ sources: - us endpoints: - us + - id: WGp9SQFRVu + display_name: Quin AI + hidden: false + slug: quin-ai + url: connections/sources/catalog/cloud-apps/quin-ai + regions: + - us + endpoints: + - us - id: bnpfpwKnhu display_name: Radar hidden: false diff --git a/src/_data/catalog/source_categories.yml b/src/_data/catalog/source_categories.yml index 25a9c80a73..cc3d826632 100644 --- a/src/_data/catalog/source_categories.yml +++ b/src/_data/catalog/source_categories.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# source categories last updated 2024-09-12 +# source categories last updated 2024-09-17 items: - display_name: A/B Testing slug: a-b-testing diff --git a/src/_data/catalog/sources.yml b/src/_data/catalog/sources.yml index 219abafb0a..f0821aaa76 100644 --- a/src/_data/catalog/sources.yml +++ b/src/_data/catalog/sources.yml @@ -1,5 +1,5 @@ # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT -# sources last updated 2024-09-12 +# sources last updated 2024-09-17 items: - id: 8HWbgPTt3k display_name: .NET @@ -1858,6 +1858,26 @@ items: - Personalization status: PUBLIC partnerOwned: true + - id: WGp9SQFRVu + display_name: Quin AI + isCloudEventSource: true + slug: quin-ai + url: connections/sources/catalog/cloud-apps/quin-ai + hidden: false + regions: + - us + endpoints: + - us + source_type: cloud-app + description: Real-time Visitor Behaviour Prediction + logo: + url: >- + https://cdn-devcenter.segment.com/8b8b10a0-5388-4818-85f6-1f81f01493b5.svg + categories: + - Personalization + - Enrichment + status: PUBLIC_BETA + partnerOwned: true - id: bnpfpwKnhu display_name: Radar isCloudEventSource: true