Merge branch 'segmentio:develop' into reddit-capi-docs

Author: akhsueh

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2024-11-26 
+# destination categories last updated 2024-12-05 
 items:
 - display_name: A/B Testing
   slug: a-b-testing

src/_data/catalog/destinations.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2024-11-26 
+# destination data last updated 2024-12-05 
 items:
 - id: 637e8d185e2dec264895ea89
   display_name: 1Flow
@@ -108163,6 +108163,131 @@ items:
   actions: []
   presets: []
   partnerOwned: false
+- id: 6720ddceaa24532723b39d63
+  display_name: Singlestore
+  name: Singlestore
+  slug: singlestore
+  hidden: false
+  endpoints:
+  - US
+  regions:
+  - us-west-2
+  - eu-west-1
+  url: connections/destinations/catalog/singlestore
+  previous_names:
+  - Singlestore
+  website: https://www.singlestore.com
+  status: PUBLIC_BETA
+  categories:
+  - Raw Data
+  - Analytics
+  logo:
+    url: https://cdn-devcenter.segment.com/c4bfae1b-e5a6-43ff-8277-d0cf02b54114.svg
+  mark:
+    url: https://cdn-devcenter.segment.com/04b8886a-5fe7-4c05-aab8-4436cd43fbce.svg
+  methods:
+    track: true
+    identify: true
+    group: true
+    alias: true
+    screen: false
+    page: true
+  platforms:
+    browser: true
+    mobile: false
+    server: true
+    warehouse: false
+    cloudAppObject: false
+    linkedAudiences: true
+  components: []
+  browserUnbundlingSupported: false
+  browserUnbundlingPublic: false
+  replay: false
+  connection_modes:
+    device:
+      web: false
+      mobile: false
+      server: false
+    cloud:
+      web: true
+      mobile: false
+      server: true
+  settings:
+  - name: dbName
+    type: string
+    defaultValue: ''
+    description: The name of the database.
+    required: true
+    label: Database Name
+  - name: environment
+    type: select
+    defaultValue: Prod
+    description: The environment of the Singlestore database.
+    required: true
+    label: Environment
+  - name: host
+    type: string
+    defaultValue: ''
+    description: The host of the Singlestore database.
+    required: true
+    label: Host
+  - name: password
+    type: password
+    defaultValue: ''
+    description: The password of the Singlestore database.
+    required: true
+    label: Password
+  - name: port
+    type: number
+    defaultValue: 3306
+    description: The port of the Singlestore database.
+    required: true
+    label: Port
+  - name: username
+    type: string
+    defaultValue: ''
+    description: The username of the Singlestore database.
+    required: true
+    label: Username
+  actions:
+  - id: xxgUnx4BHqGLDYCJ4TiWPW
+    name: Send Data
+    slug: send
+    description: Send data to Singlestore.
+    platform: CLOUD
+    hidden: false
+    defaultTrigger: >-
+      type = "track" or type = "screen" or type = "identify" or type = "page" or
+      type = "group" or type = "alias"
+    fields:
+    - id: o4FSHmgGNDZjGayk4VpDqK
+      sortOrder: 0
+      fieldKey: database
+      label: Database
+      type: STRING
+      description: The name of the SingleStore database to send data to.
+      placeholder: ''
+      required: true
+      multiple: false
+      choices: null
+      dynamic: true
+      allowNull: false
+    - id: pV6xn9yXzxddMKs6EU2Ps2
+      sortOrder: 1
+      fieldKey: message
+      label: Message
+      type: OBJECT
+      description: The complete event payload.
+      placeholder: ''
+      defaultValue:
+        '@path': $.
+      required: true
+      multiple: false
+      choices: null
+      dynamic: false
+      allowNull: false
+  presets: []
+  partnerOwned: true
 - id: 5c768ec31413290001ebdd2e
   display_name: Singular
   name: Singular
@@ -113797,6 +113922,12 @@ items:
       mobile: false
       server: true
   settings:
+  - name: audience_identifier
+    type: select
+    defaultValue: computation_key
+    description: The audience identifier from your Taboola account.
+    required: false
+    label: Audience Identifier
   - name: client_id
     type: string
     defaultValue: ''
@@ -113818,7 +113949,7 @@ items:
     hidden: false
     defaultTrigger: type = "track"
     fields:
-    - id: 5LsQp4x4a2mc1wS4x3DyGK
+    - id: hYPMUogwA6UXaPijimwgGy
       sortOrder: 3
       fieldKey: user_email
       label: Email address
@@ -113839,7 +113970,7 @@ items:
       dynamic: false
       allowNull: false
       hidden: false
-    - id: idcYjf4xSRKXSH3vaBhuxv
+    - id: mrsc76C98Fes6horASeqQU
       sortOrder: 5
       fieldKey: enable_batching
       label: Batch events
@@ -113854,7 +113985,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: kGx5FWvwYVYNB7jgs8Jx4W
+    - id: 5gysPJ3QfJvkihzwjJsW1x
       sortOrder: 6
       fieldKey: device_id
       label: Mobile Device ID

src/_data/catalog/destinations_private.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2024-11-26 
+# destination data last updated 2024-12-05 
 items:
   - id: 54521fd925e721e32a72eee1
     display_name: Pardot
@@ -670,14 +670,24 @@ items:
     browserUnbundlingPublic: false
     replay: false
     settings:
-      - name: apiKey
+      - name: accountid
+        type: string
+        defaultValue: ''
+        description: Rokt ID assigned to your particular account.
+        required: true
+        label: Rokt Account ID
+      - name: rpub
+        type: string
+        defaultValue: ''
+        description: Rokt public key, starts with `rpub-`
+        required: true
+        label: Rokt public key
+      - name: rsec
         type: password
         defaultValue: ''
-        description: >-
-          APIKey used for Rokt API authorization before sending custom audiences
-          data
+        description: Rokt secret key, starts with `rsec-`
         required: true
-        label: API Key provided by Rokt integration
+        label: Rokt secret key
     actions:
       - id: oNpU37CaJbuxq7PqBGEYz4
         name: Sync Engage Audience to Rokt
@@ -689,7 +699,7 @@ items:
         hidden: false
         defaultTrigger: type = "track" or type = "identify"
         fields:
-          - id: hkunPAdr3JHSMDGCW8Hr7P
+          - id: aCdquof3Bd6c3wug29BeEY
             sortOrder: 0
             fieldKey: custom_audience_name
             label: Custom Audience Name
@@ -704,7 +714,7 @@ items:
             dynamic: false
             allowNull: false
             hidden: false
-          - id: k8zCN8YH12e6N9EqeTbK3m
+          - id: 4qkzJunzrb3ZTtn5VEXgHo
             sortOrder: 1
             fieldKey: segment_computation_action
             label: Segment Computation Action
@@ -721,7 +731,7 @@ items:
             dynamic: false
             allowNull: false
             hidden: false
-          - id: 4rPpCohUqos6N47caU35ct
+          - id: fq5EwYtoVfnBh5wRJ6YMhH
             sortOrder: 2
             fieldKey: email
             label: Email
@@ -742,7 +752,7 @@ items:
             dynamic: false
             allowNull: false
             hidden: false
-          - id: ab4jivj6fXuTQ4TM68JERi
+          - id: ae6rFSFRB9dSGZNVAxPxjb
             sortOrder: 3
             fieldKey: traits_or_props
             label: traits or properties object
@@ -765,7 +775,7 @@ items:
             dynamic: false
             allowNull: false
             hidden: false
-          - id: vH5iWCWZpV15WjgDFTnCXd
+          - id: btfk8jdv6uDRh7KT6dmcwC
             sortOrder: 4
             fieldKey: enable_batching
             label: enable batching to rokt api

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source categories last updated 2024-11-26 
+# source categories last updated 2024-12-05 
 items:
   - display_name: A/B Testing
     slug: a-b-testing

src/_data/catalog/sources.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# sources last updated 2024-11-26 
+# sources last updated 2024-12-05 
 items:
   - id: 8HWbgPTt3k
     display_name: .NET

src/connections/destinations/catalog/actions-liveramp-audiences/index.md

@@ -41,6 +41,9 @@ The LiveRamp Audiences destination can be connected to **Twilio Engage sources o
 7. In the settings that appear in the side panel, toggle the Send Track option on and do not change the Audience Entered/Audience Exited event names. Click Save Settings
 8. File a [support case](https://docs.liveramp.com/connect/en/considerations-when-uploading-the-first-file-to-an-audience.html#creating-a-support-case){:target="_blank"} with the LiveRamp team to configure and enable ingestion.
 
+> info "Mapping tester availability"
+> The Mapping Tester isn't available for this destination. Since this destination requires batched events for activation, testing can only be performed end-to-end with a connected source.
+
 {% include components/actions-fields.html settings="false"%}
 
 ## Limitations 

src/connections/destinations/catalog/actions-s3/index.md

@@ -0,0 +1,100 @@
+---
+title: AWS S3 (Actions) Destination
+hide-boilerplate: true
+hide-dossier: false
+id: 66eaa166f650644f04389e2c
+private: true
+beta: true
+# versions:
+#   - name: AWS S3 (Classic)
+#     link: /docs/connections/destinations/catalog/aws-s3/
+---
+{% include content/plan-grid.md name="actions" %}
+
+The AWS S3 (Actions) destination allows you to store event data as objects in a secure, scalable cloud storage solution. Each event is written to your S3 bucket, organized into a customizable folder structure such as by event type or timestamp. This makes it easy to manage, archive, and analyze data using downstream tools or AWS services.
+
+
+## Benefits of AWS S3 (Actions) vs AWS S3 Classic
+The traditional AWS S3 Classic destination enabled the storage of raw logs containing data Segment received, directly into your S3 bucket. While this provided a straightforward data storage solution, users often needed to implement additional processing to standardize or transform these logs (in JSON format) for downstream analytics or integrations.
+
+The AWS S3 (Actions) destination enhances this capability by introducing configurable options to format and structure event data prior to storage. This new approach offers several key benefits:
+
+* **Standardized Data Formatting**. AWS S3 (Actions) lets you define consistent output formats for your data, either CSV or TXT file formats, in a folder definition that you choose. The previous AWS S3 Classic Destination only allowed raw JSON payloads stored within a specific folder called `"segment-logs"`. 
+
+* **Configurable Data Translation**.  AWS S3 (Actions) supports translation rules that can map raw event attributes to more meaningful or actionable representations. You can configure these rules to meet specific data schema requirements by either adding in custom columns or using the default ones.
+
+* **Enhanced Delivery Controls**. The destination provides advanced options for batch size controls and file naming conventions. These controls can help optimize efficiency and simplify data retrieval workflows.
+
+## Getting started
+Setting up the AWS S3 (Actions) destination is a straightforward process designed to help you configure and deploy standardized event data to your Amazon S3 bucket. Follow these steps to get started:
+
+### Prerequisites
+Ensure you have the following in place before configuring the AWS S3 (Actions) destination:
+
+- Amazon S3 Bucket: Create a bucket in your AWS account or use an existing one where you want to store the event data.
+- AWS IAM Permissions: Verify that you have appropriate IAM roles with write access to the S3 bucket and permissions for the Segment connection.
+- IAM Access IDs: Prepare your AWS IAM ARN ID and IAM External ID. These will be needed to authenticate and authorize Segment with your S3 bucket.
+
+
+### Step 1: Create an IAM role in the AWS console
+To set up the IAM role to properly authorize Segment with the AWS S3 (Actions) destination:
+
+1. Log in to your AWS account. 
+2. Create a new or use an existing bucket with `PutObject`, `GetObject`, `ListObject` access to the S3 bucket.
+3. Navigate to **IAM > Roles > Create Role**.
+4. Provide the following policy permissions for the IAM that was just created: 
+```json
+{
+    "Version": "2012-10-17",
+    "Statement": [
+        {
+            "Sid": "PutObjectsInBucket",
+            "Effect": "Allow",
+            "Action": [
+                "s3:PutObject",
+                "s3:PutObjectAcl"
+            ],
+            "Resource": "arn:aws:s3:::<YOUR_BUCKET_NAME>/*"
+        }
+    ]
+}
+```
+5. Click on the Trust Relationships tab and edit the trust policy to allow the IAM user to assume the role. If a user is not already created, refer to the AWS documentation to create a user.
+```json
+{
+   "Version": "2012-10-17",
+   "Statement": [
+     {
+       "Sid": "",
+       "Effect": "Allow",
+       "Principal": {
+         "AWS":                      
+         	"arn:aws:iam::595280932656:role/customer-s3-prod-action-destination-access"
+       },
+       "Action": "sts:AssumeRole",
+       "Condition": {
+         "StringEquals": {
+           "sts:ExternalId": "<YOUR_EXTERNAL_ID>"
+         }
+       }
+     }
+   ]
+ }
+```
+## Step 2: Add the AWS S3 (Actions) Destination in Segment
+To finish the configuration, enable the AWS S3 (Actions) Destination in your workspace. 
+
+1. Add the **AWS S3 (Actions)** destination from the Destinations tab of the catalog.
+2. Select the data source you want to connect to the destination.
+3. Provide a unique name for the destination.
+4. Complete the destination settings:
+   * Enter the name of the region in which the bucket you created above resides.
+   * Enter the name of the bucket you created above. Be sure to enter the bucket's **name** and not URI.
+   * Enter the ARN of the IAM role you created above. The ARN should follow the format `arn:aws:iam::ACCOUNT_ID:role/ROLE_NAME.`
+   * Enter the IAM External ID, which is a value set in the Trust Relationship under your AWS IAM Role.
+5. Enable the destination.
+6. Verify the Segment data is stored in the S3 bucket by navigating to the `<your_S3_bucket>/` in the AWS console. 
+
+{% include components/actions-fields.html settings="true"%}
+
+