Merge branch 'develop' into PINT-1842

Author: stayseesong

src/_data/catalog/destinations_private.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2023-06-29 
+# destination data last updated 2023-06-30 
 items:
   - id: 54521fd725e721e32a72eec6
     display_name: Intercom
@@ -3350,7 +3350,6 @@ items:
       url: https://cdn.filepicker.io/api/file/2nBnpISbQ9y5HVdRbNzx
     mark:
       url: https://cdn.filepicker.io/api/file/oWfR4FwGRzWqONbYNZ3z
-    methods:
       track: true
       identify: true
       group: true

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

@@ -17,7 +17,7 @@ HubSpot is an all-in-one marketing tool that helps attract new leads and convert
 When you use the HubSpot Cloud Mode (Actions) destination, Segment sends your data to [HubSpot's REST API](https://developers.hubspot.com/docs/api/overview){:target="_blank"}.
 
 > warning ""
-> The **Upsert Company** action is not compatible with the Segment Event Tester. As a result, Segment recommends using other tools to test and troubleshoot the creation and updates of companies in HubSpot.
+> The **Upsert Company** action is not compatible with the Mapping Tester on the mappings page if Associate Contact is set to **Yes**. As a result, Segment recommends using the Event Tester or other tools to test and troubleshoot creating and updating companies in HubSpot. Please note, for the company to contact association to work, you are required to trigger an Upsert Contact action before triggering an Upsert Company action.
 
 
 ## Benefits of HubSpot Cloud Mode (Actions) vs HubSpot Classic

src/connections/destinations/catalog/canny-functions/index.md

@@ -1,5 +1,38 @@
 ---
-title: 'Canny-Functions Destination'
-hidden: true
+title: Canny (Actions) Destination
+id: 6489bbade6fe3eb57c13bd6a
 beta: true
+hidden: true
+private: true
 ---
+
+{% include content/plan-grid.md name="actions" %}
+
+[Canny](https://canny.io?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="\_blank"} is a single place for all customer feedback. It saves you time managing all the feedback while keeping your customers in the loop. Let your customers post and vote on feedback from within your website or mobile app. You'll get an organized list of feedback that you can use to inform your roadmap.
+
+Canny maintains this destination. For any issues with the destination, [contact the Canny Support team](mailto:[email protected]).
+
+> success ""
+> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Canny Segment destination. There's also a page about the [non-Actions Canny destination](/docs/connections/destinations/catalog/canny/). Both of these destinations receive data from Segment.
+
+{% include content/ajs-upgrade.md %}
+
+## Benefits of Canny (Actions) vs Canny Classic
+
+Canny (Actions) provides the following benefit over the classic Canny destination:
+- **Group Events**. Canny (Actions) supports group events and updates or adds properties to companies.
+
+## Getting started
+
+1. Go to your [Canny Admin Segment Settings](https://canny.io/redirect?to=%2Fadmin%2Fsettings%2Fsegment){:target="\_blank"}.
+2. Install the integration to get your API key.
+3. From the Segment web app, navigate to **Connections > Catalog**, then select the **Destinations** tab in the catalog.
+4. Search for **Canny (Actions)** and select it.
+5. Click **Configure Canny (Actions)**.
+6. Select an existing Source to connect to Canny (Actions).
+7. Enter your configuration settings.
+8. Enter the Canny API key in the Canny (Actions) destination settings.
+9. Enable the destination and save changes.
+
+{% include components/actions-fields.html %}
+

src/connections/destinations/destination-filters.md

@@ -30,7 +30,7 @@ Keep the following limitations in mind when you use destination filters:
 - *(For device-mode)* Destination filters don't filter some fields that are collected by the destination SDK outside of Segment such as `page.url` and `page.referrer`.
 - *(For web device-mode)* Destination filters for web device-mode only supports the Analytics.js 2.0 source. You need to enable device mode destination filters for your Analytics.js source. To do this, go to your Javascript source and navigate to **Settings > Analytics.js** and turn the toggle on for **Destination Filters**.
 - *(For web device-mode)* Destination filters for device-mode only supports the Analytics.js 2.0 source.
-- *(For mobile device-mode)* Destination filters for mobile device-mode is currently not supported.
+- *(For mobile device-mode)* Destination filters for mobile device-mode doesn't support iOS and Android libraries.
 - Destination Filters don't apply to events that send through the destination Event Tester.
 
 

src/connections/reverse-etl/reverse-etl-source-setup-guides/redshift-setup.md

@@ -21,13 +21,13 @@ To set up Redshift with Reverse ETL:
     ```
 4. Follow the steps listed in the [Add a source](/docs/connections/reverse-etl#step-1-add-a-source) section to finish adding Redshift as your source.
 
-### Extra Permissions
+## Extra Permissions
 Give the `segment` user read permissions for any resources (databases, schemas, tables) the query needs to access. 
 
 Give the `segment` user write permissions for the Segment managed schema (`__segment_reverse_etl`), which keeps track of changes to the query results.  
 
-### Troubleshooting
-#### Extraction failures: relation does not exist
+## Troubleshooting
+### Extraction failures: relation does not exist
 If you are able to run the query in the Query Builder, but the sync fails with the `relation does not exist` error, please make sure the schema name is included before the database table name, and check that the schema name is correct:
 ```ts
 SELECT id FROM <schema_name>.<table_name>

src/connections/sources/catalog/libraries/mobile/ios/index.md

@@ -580,6 +580,46 @@ Analytics.shared().enable()
 > warning ""
 > If you disable the Segment SDK in response to user opt-out, all Segment method invocations (Track, Screen, Identify, etc) are ignored. However, this does not disable any destination SDKs that you bundled along with Segment. You should consult the vendor documentation for those destinations, and invoke the corresponding `disable` methods for each packaged SDK to ensure that any automatic data collection stops.
 
+## Context
+Context is a dictionary of extra information you can provide about a specific API call. You can add any custom data to the context dictionary that you want to have access to in the raw logs. Some keys in the context dictionary [have semantic meaning and are collected for you automatically](/docs/connections/spec/common/#context), such as information about the user’s device.
+
+The example below shows a track call where campaign data is added to context:
+
+{% codeexample %}
+{% codeexampletab Swift %}
+```swift
+Analytics.shared().track("Product Viewed", properties: nil, options: ["context": ["campaign": ["medium": "email", "name": "testCampaign", "source": "testSource"]]])
+```
+{% endcodeexampletab %}
+{% codeexampletab Objective-C %}
+```objc
+[[SEGAnalytics sharedAnalytics] track:@"Product Viewed"
+                            properties:nil
+                              options:@{ @"context": @{ @"campaign": @{ @"medium": @"email", @"name": @"testCampaign", @"source": @"testSource" }}}];
+```
+{% endcodeexampletab %}
+{% endcodeexample %}
+
+You can also override any context that Segment automatically collects. 
+
+The example below shows a track call where locale is overwritten to a specific value:
+
+{% codeexample %}
+{% codeexampletab Swift %}
+```swift
+Analytics.shared().track("Product Viewed", properties: nil, options: ["context": ["locale": "en"]])
+```
+{% endcodeexampletab %}
+{% codeexampletab Objective-C %}
+```objc
+[[SEGAnalytics sharedAnalytics] track:@"Product Viewed"
+                            properties:nil
+                              options:@{ @"context": @{ @"locale": @"en" }}];
+```
+{% endcodeexampletab %}
+{% endcodeexample %}
+
+
 
 ## Selecting Destinations
 

src/connections/spec/mobile.md

@@ -195,7 +195,9 @@ You can send this event when you receive a crash notification from your app, but
 
 ## Campaign events
 
-As the walls between apps become increasingly lowered, capturing information about the content and campaigns that drive users to engage with your app is critical to building more targeted, relevant, personalized experiences for your users.
+As the walls between apps become increasingly lowered, capturing information about the content and campaigns that drive users to engage with your app is critical to building more targeted, relevant, personalized experiences for your users. 
+
+Segment does not collect any campaign events automatically unless configured to do so. 
 
 ### Install Attributed
 

src/connections/storage/catalog/data-lakes/index.md

@@ -15,7 +15,7 @@ Segment supports two type of data-lakes:
 > note "Lake Formation"
 > You can also set up your Segment Data Lakes using [Lake Formation](/docs/connections/storage/data-lakes/lake-formation/), a fully managed service built on top of the AWS Glue Data Catalog.
 
-## Set up Segment Data Lakes
+## Set up Segment Data Lakes (AWS)
 
 To set up Segment Data Lakes, create your AWS resources, enable the Segment Data Lakes destination in the Segment app, and verify that your Segment data is synced to S3 and Glue.
 

src/connections/storage/data-lakes/index.md

@@ -29,7 +29,7 @@ To learn more about Segment Data Lakes, check out the Segment blog post [Introdu
 
 Segment supports Data Lakes hosted on two cloud providers: Amazon Web Services (AWS) and Microsoft Azure. Each cloud provider has a similar system for managing data, but offer different query engines, post-processing systems, and analytics options.
 
-### How Segment Data Lakes works
+### How Segment Data Lakes (AWS) works
 
 Data Lakes store Segment data in S3 in a read-optimized encoding format (Parquet) which makes the data more accessible and actionable. To help you zero-in on the right data, Data Lakes also creates logical data partitions and event tables, and integrates metadata with existing schema management tools, such as the AWS Glue Data Catalog. The resulting data set is optimized for use with systems like Spark, Athena, EMR, or machine learning vendors like DataBricks or DataRobot.
 
@@ -49,7 +49,7 @@ Data Lakes store Segment data in ADLS in a read-optimized encoding format (Parqu
 
 For detailed Segment Data Lakes (Azure) setup instructions, see the [Data Lakes setup page](/docs/connections/storage/catalog/data-lakes/).
 
-### Set up Segment Data Lakes
+### Set up Segment Data Lakes (AWS)
 
 When setting up your data lake using the [Data Lakes catalog page](/docs/connections/storage/catalog/data-lakes/), be sure to consider the EMR and AWS IAM components listed below.
 
@@ -84,7 +84,7 @@ TODO:
 add schema overview (tables/columns generated)
 -->
 
-### Segment Data Lakes schema
+### Segment Data Lakes (AWS) schema
 
 #### S3 partition structure
 

src/connections/storage/warehouses/schema.md

@@ -7,6 +7,7 @@ A **schema** describes the way that the data in a warehouse is organized. Segmen
 
 > note "Warehouse column creation"
 > **Note:** Segment creates tables for each of your custom events in your warehouse, with columns for each event's custom properties. Segment does not allow unbounded `event` or `property` spaces in your data. Instead of recording events like "Ordered Product 15", use a single property of "Product Number" or similar.
+> Segment creates and populates a column only when it receives a non-null value from the source.
 
 ### How warehouse tables handle nested objects and arrays