Merge pull request #2052 from segmentio/develop

Release 21.41.2

Author: stayseesong

src/_data/actions/customer-io.yml

@@ -7,6 +7,8 @@ settings:
     - name: Site ID (required)
       description: Your Customer.io site Key. This can be found on the [API Credentials Page](https://fly.customer.io/settings/api_credentials){:target="_blank"}.
       default:
+    - name: Account Region
+      description: For more information, see Customer.io's documentation about [Account Regions](https://customer.io/docs/data-centers/){:target="_blank"}.
 actions:
   - action: Track Event
     blurb: Track an event for a known person.
@@ -82,9 +84,9 @@ config:
       connection_mode:
         - cloud
         - device-web
-      configurable: false
+      configurable: true
       location:
-      notes: Customer.io Data Center is not needed in Customer.io (Actions)
+      notes: Select the Account Region in Connection Settings.
     - name: Site ID
       connection_mode:
         - cloud
@@ -96,7 +98,7 @@ config:
       connection_mode:
         - cloud
         - device-web
-      configurable: false
+      configurable: true
       location:
       notes: Customer.io (Actions) supports cloud-mode.
   - category: Other Settings

src/_data/actions/tiktok.yml

@@ -0,0 +1,43 @@
+settings:
+  - category: Connection Settings
+    settings:
+    - name: Access Token (required)
+      description: TikTok Long Term Access Token. You can generate this from the TikTok Marketing API portal. Please follow TikTok's [Authorization guide](https://ads.tiktok.com/athena/docs/index.html?plat_id=-1&doc_id=100010&id=100681&key=e98b971a296ae45d8e35a22fba032d1c06f5973de9aab73ce07b82f230cf3afd){:target="_blank"} for more info.
+      default:
+    - name: Secret Key (required)
+      description: TikTok App Secret Key. You can find this key in the "Basic Information" tab of your TikTok app.
+      default:
+    - name: App Id (required)
+      description: TikTok App Id. You can find this key in the "Basic Information" tab of your TikTok app.
+      default:
+    - name: Pixel Code (required)
+      description: An ID for your pixel. Required to send events to the TikTok pixel.
+      default:
+actions:
+  - action: Report Web Event
+    blurb: Report events directly to TikTok.
+    fields:
+    - name: Email
+      description: Email address of the user who triggered the conversion event.
+      default: coalesce(properties.email, traits.email)
+    - name: External ID 
+      description: Uniquely identifies the user who triggered the conversion event.
+      default: coalesce(userId, anonymousId)
+    - name: Event Name
+      description: Conversion event name. Please refer to the "Supported Web Events" section on [this](https://ads.tiktok.com/marketing_api/docs?id=1701890979375106){:target="_blank"} page for accepted event names.
+      default: 
+    - name: Event ID
+      description: Any hashed ID that can identify a unique user/session.
+      default: messageId
+    - name: Event Timestamp
+      description: Timestamp that the event took place, in ISO 8601 format.
+      default:
+    - name: Segment Event Type
+      description: The Segment Event type, for example, "page".
+      default: type
+    - name: Properties associated with the event
+      description: Additional properties such as content info, description, and currency.
+      default: 
+    - name: Phone Number
+      description: Phone number of the user who triggered the conversion event, in E.164 standard format, e.g. +14150000000.
+      default: coalesce(properties.phone, traits.phone)

src/connections/destinations/actions.md

@@ -1,6 +1,5 @@
 ---
 title: Destination Actions
-hidden: true
 ---
 
 {% include content/plan-grid.md name="dest-actions" %}
@@ -15,13 +14,26 @@ You can also choose which event types, event names, or event property values tri
 
 Each Actions-framework Destination you see in the Segment catalog represents a feature or capability of the destination which can consume data from your Segment source. The Action clearly lists which data from the events it requires, and which data is optional. For example, Amplitude requires that you always send a  `LogEvent` , or Slack always requires a `PostMessage`.  Each Action also includes a default mapping which you can modify.
 
+## Benefits of Destination Actions
+
+- **Easier setup**: Users see fewer initial settings which can decrease the time spent configuring the destination.
+- **Increased transparency**: Users can see the exact data that is sent to the destination, and when Segment sends it. For example, users can see exactly when Segment sends an IP address to FullStory or an AnonymousId to Amplitude.
+- **Improved customization**: Users can determine how the events their sources trigger and map to actions supported by the destination. For example, define the exact events that are considered purchases by Braze.
+- **Partner ownership**: Partners can own and contribute to any Actions-based destination that use cloud and device mode (web).
+
 ## Available Actions-based Destinations
-- [Amplitude (Actions)](/docs/connections/destinations/catalog/actions-amplitude)
-- [Braze (Actions) Web](/docs/connections/destinations/catalog/actions-braze-web)
-- [Braze (Actions) Cloud](/docs/connections/destinations/catalog/actions-braze-cloud)
-- [Slack (Actions)](/docs/connections/destinations/catalog/actions-slack)
-- [FullStory (Actions)](/docs/connections/destinations/catalog/actions-fullstory)
-- [Customer.io (Actions)](/docs/connections/destinations/catalog/actions-customer-io)
+
+The following destinations are available in public beta status:
+
+| Destination                                                                         | Benefits                                                                                                                |
+| ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
+| [Amplitude (Actions)](/docs/connections/destinations/catalog/actions-amplitude)     | - Supports Amplitude session reporting <br /> - Revenue is a top-level property <br /> - Session tracking in cloud-mode |
+| [Braze (Actions) Cloud](/docs/connections/destinations/catalog/actions-braze-cloud) | E-commerce mappings                                                                                                     |
+| [Braze (Actions) Web](/docs/connections/destinations/catalog/actions-braze-web)     | E-commerce mappings                                                                                                     |
+| [Customer.io (Actions)](/docs/connections/destinations/catalog/actions-customer-io) | Track an anonymous event                                                                                                |
+| [FullStory (Actions)](/docs/connections/destinations/catalog/actions-fullstory)     | Support for FullStory's tracking page variables feature.                                                                |
+| [Slack (Actions)](/docs/connections/destinations/catalog/actions-slack)             | - Consolidated Message Sending <br /> - Configure connection details on a per-message basis                             |
+
 
 ## Destination Actions compatibility
 

src/connections/destinations/catalog/actions-customer-io/index.md

@@ -3,6 +3,8 @@ title: Customer.io (Actions) Destination
 hide-personas-partial: true
 hide-boilerplate: true
 hide-dossier: true
+redirect_from:
+- '/connections/destinations/catalog/customer-io-actions/'
 ---
 {% include content/plan-grid.md name="actions" %}
 

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

@@ -6,7 +6,7 @@ hidden: true
 ---
 
 > info ""
-> This document is about a feature that is in beta. This means that the destination is in active development, and some functionality may change before it becomes generally available
+> This document is about a feature that is in beta. This means that the destination is in active development, and some functionality may change before it becomes generally available.
 
 > success ""
 > **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Google Enhanced Conversions Segment destination. 
@@ -17,7 +17,7 @@ The Google Enhanced Conversions destination enables you to improve the accuracy
 > Enable Enhanced Conversions in your Google Ads account. For each Conversion, specify in the settings to that you will use the enhanced conversions API:
 > 1.  When you log in to Google Ads, make sure you are in [Expert Mode](https://support.google.com/google-ads/answer/9520605?hl=en){:target="_blank"}.
 > 2. Click **Tools & Settings** in the top bar, and select **Conversions** from the dropdown. Select the **Conversion Action** you want Segment to log to.
-> 3. Expand the tab for **Enhanced Conversions**. Enable **Turn on enhanced conversions** and click **Edit code**, then **Use enhanced conversions API**.
+> 3. Expand the tab for **Enhanced conversions**. Enable **Turn on enhanced conversions**. Under "To start, select how you want to set up enhanced conversions", select **API**.
 > 
 > When you authenticate your Segment workspace with your Google Account, use a Google Account that is a member of your Google Ads account.
 

src/connections/destinations/catalog/adobe-target/index.md

@@ -3,6 +3,8 @@ title: Adobe Target Destination
 strat: adobe
 rewrite: true
 beta: true
+hidden: true
+published: false
 ---
 [Adobe Target](https://www.adobe.com/marketing-cloud/target.html) removes the
 coding and set up hassles of A/B testing to help you quickly discover which

src/connections/destinations/catalog/moengage/index.md

@@ -184,7 +184,7 @@ The MoEngage SDK depends on the below Jetpack libraries provided by Google for i
     implementation("androidx.appcompat:appcompat:1.2.0")
     implementation("androidx.lifecycle:lifecycle-process:2.2.0")
 ```
-Refer to the [SDK Configuration](https://docs.moengage.com/docs/android-sdk-configuration) documentation to know more about the build config and other libraries used by the SDK.
+Refer to the [SDK Configuration](https://developers.moengage.com/hc/en-us/articles/4401984733972-Android-SDK-Configuration) documentation to know more about the build config and other libraries used by the SDK.
 
 ### Register MoEngage with Segment SDK
 
@@ -236,7 +236,7 @@ MoEHelper.getInstance(getApplicationContext()).setAppStatus(AppStatus.INSTALL);
 
 ### Configure Push Notifications
 
-Copy the Server Key from the FCM console and add it to the MoEngage Dashboard. For more information about retrieving the Server Key, see [MoEngage - Getting FCM Server Key](https://docs.moengage.com/docs/getting-fcmgcm-server-key). To upload it, go to the Settings Page `Dashboard --> Settings --> Channel --> Push --> Mobile Push --> Android` and add the Server Key and package name.
+Copy the Server Key from the FCM console and add it to the MoEngage Dashboard. To upload it, go to the Settings Page `Dashboard --> Settings --> Channel --> Push --> Mobile Push --> Android` and add the Server Key and package name.
 **Please make sure you add the keys both in Test and Live environment.**
 
 #### Add meta information for push notification
@@ -338,21 +338,19 @@ Add the following snippet and replace `[PARENT_ACTIVITY_NAME]` with the name of
 
 You are now all set up to receive push notifications from MoEngage. For more information on features provided in MoEngage Android SDK refer to the following links:
 
-* [Push Notifications](http://docs.moengage.com/docs/push-configuration)
+* [Push Notifications](https://developers.moengage.com/hc/en-us/sections/360013606771-Push)
 
-* [Geofence](https://docs.moengage.com/docs/android-geofence)
+* [Location Triggered](https://developers.moengage.com/hc/en-us/articles/4403443036564-Location-Triggered)
 
-* [In-App messaging](https://docs.moengage.com/docs/android-in-app-nativ)
+* [In-App messaging](https://developers.moengage.com/hc/en-us/sections/360013831431-In-App-Messages)
 
-* [Notification Center](https://docs.moengage.com/docs/android-notification-center)
-
-* [Advanced Configuration](https://docs.moengage.com/docs/android-advanced-integration)
+* [Notification Center](https://developers.moengage.com/hc/en-us/articles/4403878923284-Notification-Center)
 
 * [API Reference](https://moengage.github.io/android-api-reference/index.html)
 
-* [Compliance](https://docs.moengage.com/docs/android-compliance)
+* [Compliance](https://developers.moengage.com/hc/en-us/sections/4403894212116-Compliance)
 
-* [Release Notes](https://docs.moengage.com/docs/segment-android-releases)
+* [Release Notes](https://developers.moengage.com/hc/en-us/articles/4403896795540-Changelog)
 
 
 ### Identify
@@ -367,7 +365,7 @@ If your app supports the ability for a user to logout and login with a new ident
 
 ### Sample Implementation
 
-Refer to [this](https://github.com/moengage/moengage-segment-integration) github repository for sample implementation
+Refer to [this](https://github.com/moengage/moengage-segment-integration) Github repository for sample implementation
 
 ## Web