Merge pull request #6334 from segmentio/develop

Release 24.14.1

Author: cmastr

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2024-03-26 
+# destination categories last updated 2024-04-02 
 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-03-26 
+# destination data last updated 2024-04-02 
 items:
 - id: 637e8d185e2dec264895ea89
   display_name: 1Flow
@@ -704,18 +704,18 @@ items:
 - id: 64f703d1f6e9aa0a283ae3e2
   display_name: ABsmartly (Actions)
   name: ABsmartly (Actions)
-  slug: absmartly-actions
+  slug: actions-absmartly
   hidden: false
   endpoints:
   - US
   regions:
   - us-west-2
   - eu-west-1
-  url: connections/destinations/catalog/absmartly-actions
+  url: connections/destinations/catalog/actions-absmartly
   previous_names:
   - ABsmartly (Actions)
   website: https://absmartly.com/
-  status: PUBLIC_BETA
+  status: PUBLIC
   categories:
   - A/B Testing
   - Feature Flagging
@@ -24513,7 +24513,7 @@ items:
     hidden: false
     defaultTrigger: event = "Audience Exited"
     fields:
-    - id: hcFsZUAz4PnJiafinMjGBq
+    - id: decntd8LrKcv9ie1So3RCL
       sortOrder: 0
       fieldKey: enable_batching
       label: Enable Batching
@@ -24526,7 +24526,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: q1mGgjhDxDWL9rFZcqmz78
+    - id: vy8596qAAowDPaUDcQXRyg
       sortOrder: 1
       fieldKey: external_audience_id
       label: External Audience ID
@@ -24540,7 +24540,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: gjU4G9uWSiVUQ16g3dkGCW
+    - id: fXFR2b5pNgUVFsXD8qmwvQ
       sortOrder: 2
       fieldKey: mobile_advertising_id
       label: Mobile Advertising ID
@@ -24554,7 +24554,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: fGS6WjJVg5WD2HgHpp6PRf
+    - id: d5kfNzrJmdCpmtD4YM1eZG
       sortOrder: 3
       fieldKey: google_gid
       label: Google GID
@@ -24570,7 +24570,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: 7NzUcnNFHKFKaBGvEEDsWs
+    - id: b5JqEKs2cLtRxL7pGZYZL
       sortOrder: 4
       fieldKey: partner_provided_id
       label: Partner Provided ID
@@ -24594,7 +24594,7 @@ items:
     hidden: false
     defaultTrigger: event = "Audience Entered"
     fields:
-    - id: tzrvbbHAcJUeH66ZUMe3qF
+    - id: pvnvQKPBXnodz1iNBg3pHf
       sortOrder: 0
       fieldKey: enable_batching
       label: Enable Batching
@@ -24607,7 +24607,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: qr6XD3sUCTL3eHxa9vT7Z4
+    - id: 4NKT2zS5rKAtpBjakkpJvn
       sortOrder: 1
       fieldKey: external_audience_id
       label: External Audience ID
@@ -24621,7 +24621,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: 5bXAa1PGccofiWvhjhAg1N
+    - id: wUMaDo7XGxk7t6ccibC5RT
       sortOrder: 2
       fieldKey: mobile_advertising_id
       label: Mobile Advertising ID
@@ -24635,7 +24635,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: qJoZoGGW23rpqxrreQRn2i
+    - id: r2njfNxsmfoWrLsdHM5GzK
       sortOrder: 3
       fieldKey: google_gid
       label: Google GID
@@ -24651,7 +24651,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: gsX4MWbMmCwQ6Wcms7psFf
+    - id: kBVti6k7B8cSehgdZcVjv3
       sortOrder: 4
       fieldKey: partner_provided_id
       label: Partner Provided ID

src/_data/catalog/destinations_private.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2024-03-26 
+# destination data last updated 2024-04-02 
 items:
   - id: 54521fd925e721e32a72eee1
     display_name: Pardot

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source categories last updated 2024-03-26 
+# source categories last updated 2024-04-02 
 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-03-26 
+# sources last updated 2024-04-02 
 items:
   - id: 8HWbgPTt3k
     display_name: .NET

src/_data/sidenav/strat.yml

@@ -199,6 +199,8 @@ sections:
     title: Typewriter for Kotlin
   - path: /connections/sources/catalog/libraries/mobile/kotlin-android/kotlin-android-destination-filters
     title: Destination Filters for Kotlin
+  - path: /connections/sources/catalog/libraries/mobile/kotlin-android/kotlin-android-faq
+    title: FAQs
 
 - slug: swift
   section_title: Analytics-Swift Documentation

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

@@ -1,7 +1,6 @@
 ---
 title: ABsmartly (Actions) Destination
 id: 64f703d1f6e9aa0a283ae3e2
-beta: true
 ---
 
 {% include content/plan-grid.md name="actions" %}

src/connections/destinations/catalog/actions-hubspot-cloud/index.md

@@ -98,3 +98,9 @@ Follow the steps mentioned [here](https://knowledge.hubspot.com/integrations/con
 ### How does disconnecting and uninstalling affect a user's data and HubSpot account?
 Segment immediately stops sending data to HubSpot after you disconnect and uninstall a HubSpot account.
 
+### Understanding HubSpot's `date` and dateTime` custom property types
+If you plan on sending a _date_ value that includes time data to your mapped HubSpot custom properties, select HubSpot's `dateTime` property type in HubSpot. If you plan to send a _date_ value that does not contain time data, select the `date` property value in HubSpot. For more information about custom property types, see HubSpot's [Custom objects](https://developers.hubspot.com/docs/api/crm/crm-custom-objects#properties){:target="_blank”} documentation.
+
+If you send a _date_ value that contains time data to a custom property in HubSpot with a `date` property type,  the event might fail due to an "**Invalid Date Error**."
+
+Both of HubSpot's _date_ property types each accept ISO 8601 formatted values, but only the `dateTime` property type accepts values that include time data.

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

@@ -0,0 +1,104 @@
+---
+title: Kafka Destination
+beta: true
+hidden: true
+id: 65dde5755698cb0dab09b489
+---
+
+{% include content/plan-grid.md name="actions" %}
+
+[Kafka](https://kafka.apache.org/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} provides a highly scalable and fault-tolerant messaging system that enables real-time data processing and stream processing at scale. When integrated with Segment, Kafka serves as a powerful backbone for managing and processing event data collected by Segment, allowing businesses to efficiently ingest, route, and analyze data across various applications and systems in real time.
+
+This destination is maintained by Segment. For any issues with the destination, [contact the Segment Support team](mailto:[email protected]).
+
+## Getting started
+
+### Create the Kafka Destination
+
+1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Kafka".
+2. Select the "Kafka" tile and click **Add Destination**.
+3. Select an existing Source to connect to Kafka.
+4. Enter a name for your Kafka destination.
+
+### Configure the Kafka Destination
+
+The way you've configured your Kafka Cluster informs the authentication and encryption settings you'll need to apply to the Segment Kafka Destination. You may need the assistance of someone technical to provide values for the following Settings:
+
+<ol style="counter-reset: none">
+  <li value="5" markdown="1">
+  On the Settings tab, enter values into the **Client ID**, **Brokers** and **Authentication Mechanism** setting fields.
+  </li>
+  <li value="6">
+  Populate fields based on the value you selected from the <b>Authentication Mechanism</b> field:
+    <ul>
+      <li>
+        <b>Plain</b> or <b>SCRAM-SHA-256 / 512</b> authentication: provide values for <b>Username</b> and <b>Password</b> fields.
+      </li>
+      <li> 
+        <b>AWS</b> authentication: provide values for <b>AWS Access Key ID</b> and <b>AWS Secret Key</b> fields, and optionally for the <b>AWS Authorization Identity</b> field. 
+      </li>
+      <li>
+        <b>Client Certificate</b> authentication: provide values for the <b>SSL Client Key</b> and <b>SSL Client Certificate</b> fields. 
+      </li>
+    </ul>
+  </li>  
+  <li value="7" markdown="1">
+  Populate the **SSL Certificate Authority** field, if necessary. 
+  </li>
+  <li value="8" markdown="1"> 
+  Save your changes and proceed to [Configure the Send Action](#configure-the-send-action). 
+  </li>
+</ol>
+
+### Configure the "Send" Action
+
+<ol style="counter-reset: none;">
+  <li value="9" markdown=1>
+  Select the Mappings tab and add a new **Send** mapping. 
+  </li>
+  <li value="10" markdown=1>
+  Select a Topic to send data to. This field should auto-populate based on the credentials you provided in the Settings tab. 
+  </li>
+  <li value="11" markdown=1>
+  Map your payload using the **Payload** field. <br> _(Optional)_: Specify partitioning preferences, Headers and Message Key values.
+  </li>
+  <li value="12" markdown=1>
+  Save and enable the Action, then navigate back to the Kafka destination's Settings tab to enable and save the Destination. 
+  </li>
+</ol>
+
+{% include components/actions-fields.html %}
+
+## FAQ
+
+### Which Kafka Platforms are supported?
+
+The Kafka Destination can send data to Topics on self-hosted Kafka Clusters, or to Clusters hosted on Managed Service platforms like **Confluent Cloud** and **Aiven**.
+
+### Which data formats are supported?
+
+Segment sends data to Kafka in JSON format only. Segment does not yet support other formats, like Avro or Protobuf. 
+
+### Which authentication mechanisms are supported?
+
+The Authentication Mechanism is controlled with the **Authentication Mechanism** Setting field. 
+
+Segment supports the following SASL-based authentication methods: 
+- Plain 
+- SCRAM-SHA-256
+- SCRAM-SHA-512
+- AWS 
+
+Segment also supports **Client Certificate** authentication. 
+
+### How is partitioning controlled?
+
+The **Send** Action provides multiple ways to specify which Partition an event should be sent to. 
+
+- **Partition**: Use this field to specify the name of the Partition Segment should send events to. 
+- **Default Partition**: Use this field to specify a default Partition. Segment uses this when you don't provide a value in the **Partition** field.
+- **Message Key**: Segment uses a hash of this field's value to determine which Partition should receive an event. If you don't provide a Message Key, Segment uses a round robin algorithm to select the partition to send the event to. 
+
+### What is the "SSL - Reject Unauthorized Certificate Authority" field for?
+
+This field specifies if Segment should reject server connections when a certificate is notsigned by a trusted Certificate Authority (CA). This can be useful for testing purposes or when using a self-signed certificate. 

src/connections/destinations/catalog/actions-linkedin-conversions/index.md

@@ -0,0 +1,49 @@
+---
+title: LinkedIn Conversions API Destination
+id: 652e765dbea0a2319209d193
+beta: true
+---
+
+The LinkedIn Conversions API (CAPI) is a conversion tracking tool that creates a direct connection between marketing data from an advertiser’s server and LinkedIn. This integration enables advertisers to measure the performance of their LinkedIn marketing campaigns no matter where the conversion happens and use this data to power campaign optimization. The Conversions API can help strengthen performance and decrease cost per action with more complete attribution, improved reliability, and optimized delivery.
+
+This destination is maintained by Segment. For any issues with the destination, [contact the Segment Support team](mailto:[email protected]).
+
+## Getting started
+
+1. From the Segment web app, click **Catalog**, then click **Destinations**.
+2. Search for “LinkedIn Conversions API” in the Destinations Catalog, and select the destination.
+3. On the LinkedIn Conversions API overview page, click **Add destination**.
+4. Select the source that you want to connect to the LinkedIn Conversions API and click **Next**.
+5. Enter a name for your destination and click **Create destination**. 
+6. On the Settings tab, click Connect to `[destination-name]` and follow the prompts to authenticate with LinkedIn using OAuth. 
+7. Enable the destination and click **Save Changes**.
+
+### Set up a mapping to Stream Conversion Events
+
+Follow the steps in the Destination Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customize-mappings). You must create 1 mapping for every conversion rule. After you create a conversion rule, you cannot update the connected LinkedIn Ad account.  
+
+1. On the Mappings tab, click on **+ New Mapping** and Select **Stream Conversion Event**. 
+2. Select the events you'd like to map and send to your LinkedIn Conversions API destination.
+3. Create a conversion rule or enter the link to an existing rule. _If you chose to create a new conversion rule, Segment creates the conversion rule as soon as you click **Save**._  
+4. Configure the mappings to map event fields and user attributes from your source to the Conversion API. 
+5. Click **Save**. 
+
+After you've created a Stream Conversion Event mapping, Segment displays the connected rule for each mapping on the Mappings tab. To update the conversion rule you created, select the menu icon for the mapping you'd like to update and click **Edit Mapping**. Scroll to section 3, Create a Conversion Rule, and select **Edit your configuration**. After making changes to your conversion rule, click **Save** to save your changes. You can make changes to all fields except for the Ad account field. After you save your changes, Segment updates the conversion rule in LinkedIn. 
+
+{% include components/actions-fields.html %}
+
+## FAQ and troubleshooting
+
+### Why are my inputs failing?
+
+Your inputs must meet the following criteria: 
+- Contains a valid URN with the following format: <br> `urn:lla:llaPartnerConversion:id`
+- The authenticated user must have write access to the ad account used to create conversion rules
+- Contains a userInfo combination that requires firstName and lastName **OR** a userId mapped to at least one of the following idTypes: 
+  - `SHA256_EMAIL`
+  - `LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID`
+  - `ACXIOM_ID`
+  - `ORACLE_MOAT_ID`
+- `conversionHappenedAt` must be a valid timestamp (milliseconds since epoch) and must have happened in the past 90 days
+
+Any deviations from this specification might lead to failed inputs.