Merge pull request #7298 from segmentio/develop

Release 24.49.1

Author: stayseesong

CODEOWNERS

@@ -47,7 +47,7 @@ CODEOWNERS  @segmentio/segment-doc-team
 /src/unify @pwseg 
 
 # Protocols owners
-/src/protocols @forstisabella @pwseg
+/src/protocols @forstisabella
 
 # Storage owners
-/src/connections/storage @forstisabella @pwseg
+/src/connections/storage @forstisabella

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/_includes/content/destination-dossier.html

@@ -59,6 +59,7 @@ <h6>Destination Info</h6>
       <li>This destination is not compatible with <a href="/docs/connections/functions/insert-functions/">Destination Insert Functions.</a></li>
       {% endunless %}    
     {% endif %}
+  {% if thisDestination == '64c031541451bb784943f809' or thisDestination == '63e42d44b0a59908dc4cacc6' or thisDestination == '642440d46b66b3eeac42b581' %} <li>This destination is <b>not</b> supported in EU workspaces. For more information, see the <a href="/docs/guides/regional-segment/">Regional Segment</a> documentation.</li> {% endif %}
   {% if destinationInfo.status == "PUBLIC_BETA" %}<li>This destination is in <span class="release-pill">Beta</span></li>{% endif %}
   {% if page.engage == true %}<li>This destination is <b>only</b> compatible with <a href="/docs/engage">Twilio Engage</a>.</li>{% endif %}
 </ul>

src/api/public-api/fql.md

@@ -7,10 +7,9 @@ redirect_from:
 
 {% include content/papi-ga.html %}
 
+This reference provides a comprehensive overview of the Segment Destination Filter query language. For information on the Destination Filters API (including information on migrating from the Config API), visit the [Destination Filters API reference](https://docs.segmentapis.com/tag/Destination-Filters){:target="_blank"}.
 
-Destination Filter Reference documentation can be found in the [main Config API reference docs](https://reference.segmentapis.com/#6c12fbe8-9f84-4a6c-848e-76a2325cb3c5).
-
-The Transformations API uses Filter Query Language (FQL) to filter JSON objects and conditionally apply transformations. You can use FQL statements to:
+The [Transformations API](https://docs.segmentapis.com/tag/Transformations/){:target="_blank"} uses Filter Query Language (FQL) to filter JSON objects and conditionally apply transformations. You can use FQL statements to:
 - Apply filters that evaluate to `true` or `false` based on the contents of each Segment event. If the statement evaluates to `true`, the transformation is applied, and if it is `false` the transformation is not applied.
 - [Define new properties based on the result of an FQL statement](/docs/protocols/transform/#use-cases).
 

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

@@ -0,0 +1,26 @@
+--
+title: Drip (Actions) Destination
+id: 673b62169b3342fbe0fc28da
+---
+
+{% include content/plan-grid.md name="actions" %}
+
+[Drip](https://www.getdrip.com){:target="_blank”} is a nurture marketing platform Empowering B2C SMBs to convert long-sales cycle prospects into lifelong buyers with sophisticated and personalized marketing automation.
+
+This destination is maintained by Drip. For any issues with the destination, [contact their Support team](mailto:[email protected]).
+
+## Getting started
+
+1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Drip (Actions)".
+2. Select Drip (Actions) and click **Add Destination**.
+3. Select an existing Source to connect to Drip (Actions).
+4. Go to the [Drip dashboard](https://www.getdrip.com/dashboard){:target="_blank"}
+5. In the Settings tab, select the User Settings, find and copy the **API key** at the bottom of the page.
+6. In a terminal, run `echo <your-api-key>: | base64` to encode the API key.
+7. Enter the encoded **API Key** in the Drip destination settings in Segment.
+8. Your account ID is a seven digit number that can be found in the address bar of your browser when you are logged into Drip. It is the number after `https://www.getdrip.com/`.
+9. Enter the **Account ID** in the Drip destination settings in Segment.
+
+{% include components/actions-fields.html %}
+
+For more information about developing with Drip, check out their [documentation](https://developer.drip.com/){:target="_blank”}.

src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md

@@ -13,7 +13,7 @@ hide_action:
     name: "Call Conversion"
   - id: mFUPoRTLRXhZ3sGbM8H3Qo
     name: "Conversion Adjustment"
-  - id: oWa5UioHjz5caK7t7tc57f
+  - id: h8sh7d7TUJYR1uv6RKZTGQ
     name: 'Upload Enhanced Conversion (Legacy)'
 ---
 

src/connections/destinations/catalog/actions-intercom-web/index.md

@@ -70,5 +70,36 @@ If you are seeing 404 responses in your browser's network tab, you've likely enc
 - You set the wrong App ID on the Intercom Actions (Web) destination settings page.
 - You set the wrong Regional Data Hosting value on the Intercom Actions (Web) destination settings page. Intercom gates regional endpoints by plan level, so you may not have access to EU data hosting.
 
-### Intercom does not support rETL event batching
-The Intercom (Web) Actions destination does not support the bulk contacts endpoint, and therefore is unable to support batching events in rETL.
+### Intercom does not support Reverse ETL event batching
+The Intercom (Web) Actions destination does not support the bulk contacts endpoint, and therefore is unable to support batching events in Reverse ETL.
+
+### Why are my Identify calls not updating or creating Intercom profiles, or not showing users as leads or visitors?
+Intercom requires requests to include user data/traits beyond `email` or `user_hash` to update or create profiles and change user status from leads/visitors. Without additional user data/traits, Intercom assumes no changes were made to a user's data and does not send a "ping" request.
+
+In the following example, which only includes an `email` and `user_hash`, Intercom would not send a "ping" request and update the status of this user:
+
+```
+analytics.identify("123");
+
+analytics.identify("123", { email: "[email protected]" });
+
+analytics.identify("123",{email: "[email protected]"}, {
+   integrations: {
+    Intercom: {
+      user_hash: "81b65b9abea0444437a5d92620f03acc33f04fabbc32da1e047260024f80566a"
+    }
+  }})
+```
+
+However, in the following example that also contains the `name` trait, Intercom sends a "ping" request and updates the status of this user:
+
+```
+analytics.identify("123", {
+   email: "[email protected]",
+   name: "John Doe"
+}, {
+   integrations: { Intercom: { user_hash: "hash" } }
+});
+```
+
+When sending calls to Intercom, always include a trait, like`name`. If you don't have a trait to send with Identify calls, map Segment's `timestamp` field to Intercom's `last_request_at` field.

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