Release fix (#3810)

* Add docs for new Aampe destination (#3803)

* Add docs for new Aampe destination

* Add 'Aampe' to accept list

Co-authored-by: markzegarelli <[email protected]>

* Re-adding these (#3808)

Co-authored-by: Segment Docs Robot <[email protected]>
Co-authored-by: Thomas Gilbert <[email protected]>

Author: 3 people

.github/styles/Vocab/Docs/accept.txt

@@ -17,6 +17,7 @@
 (?:U|u)nmaps?\b
 (?:U|u)ploader
 (?:U|u)rls?\b
+Aampe
 adset
 Adwords
 Aircall
@@ -102,6 +103,7 @@ NSDate
 NSNull
 NSNumber
 NSString
+OAuth
 Okta
 Omnichannel
 onboarding

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

@@ -0,0 +1,35 @@
+---
+title: Aampe Destination
+id: 6188d844be5cf0e3b59189d2
+---
+
+[Aampe](https://aampe.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) uses automated, rapid learning to personalize notifications, and continuously learns what messages bring value to your customer.
+
+This destination is maintained by Aampe. For any issues with the destination, [contact the Aampe Support team](mailto:[email protected]).
+
+## Getting Started
+
+{% include content/connection-modes.md %}
+
+1. From the Destinations catalog page in the Segment App, click **Add Destination**.
+2. Search for "Aampe" in the Destinations Catalog, and select the "Aampe" destination.
+3. Choose which Source should send data to the "Aampe" destination.
+4. Go to the [Data Integrations page](https://compose.aampe.com/configure/integrations) on Aampe Composer, click on "Add Integration", select "Segment" and click "Next".
+5. Copy the Segment API Key from the resulting page.
+6. Enter this key in "API Key" in the "Aampe" destination settings in Segment.
+
+## Supported methods
+
+Aampe supports the following methods, as specified in the [Segment Spec](/docs/connections/spec).
+
+### Track
+
+Segment sends [Track](/docs/connections/spec/track) calls to Aampe as a `track` event. These are used by Aampe to display engagement activity and reports in the [Aampe Composer](https://compose.aampe.com). You can use these to configure goals that are used for monitoring and creating campaigns. It may take up to 24 hours for events to show up in the Aampe Composer.
+
+```js
+analytics.track("Login Button Clicked");
+```
+
+Segment sends Track calls to Aampe as a `track` event.
+
+Other methods like Page, Screen, and Identify are accepted by the Aampe destination but are not stored or used in any way.

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

@@ -2,8 +2,6 @@
 title: HubSpot Cloud Mode (Actions) Destination
 hide-boilerplate: true
 hide-dossier: false
-hidden: true
-private: true
 id: 632b1116e0cb83902f3fd717
 versions:
   - name: 'HubSpot Web (Actions)'
@@ -55,4 +53,8 @@ HubSpot Cloud Mode (Actions) provides the following benefits over the classic Hu
 Segment provides prebuilt mappings for contacts and companies. If there are other standard objects you would like to create records in, please use the **Create Custom Object Record** action. For example, to create a deal in HubSpot, add a mapping for Create Custom Object Record, set up your Event Trigger criteria, and input a literal string of "deals" as the Object Type. You can use the Properties object to add fields that are in the [deals object](https://developers.hubspot.com/docs/api/crm/deals){:target="_blank"}, such as `dealname` and `dealstage`. The same can be done with other object types (for example, tickets, quotes, etc). Please note, Segment only supports creating new records in these cases; updates to existing records are only supported for contacts and companies.
 
 ### Why aren't my custom behavioral events appearing in HubSpot?
-HubSpot has several limits for custom behavioral events, including a limit on the number of event properties per event. Each event can contain data for up to 50 properties. If this limit is exceeded, the request will fail. See [HubSpot documentation](https://knowledge.hubspot.com/analytics-tools/create-custom-behavioral-events#define-the-api-call){:target="_blank"} for other limits.
+HubSpot has several limits for custom behavioral events, including a limit on the number of event properties per event. Each event can contain data for up to 50 properties. If this limit is exceeded, the request will fail. See [HubSpot documentation](https://knowledge.hubspot.com/analytics-tools/create-custom-behavioral-events#define-the-api-call){:target="_blank"} for other limits.
+
+### Does the HubSpot Cloud Mode (Actions) destination support EU data residency?
+Yes. HubSpot will automatically redirect API requests directly to an EU data center if your HubSpot instance is on an EU data center. See more in HubSpot's [Routing API Traffic](https://product.hubspot.com/blog/routing-api-traffic){:target="_blank"} article.
+

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

@@ -2,8 +2,6 @@
 title: HubSpot Web (Actions) Destination
 hide-boilerplate: true
 hide-dossier: false
-hidden: true
-private: true
 id: 631a1c2bfdce36a23f0a14ec
 versions:
   - name: 'HubSpot Cloud Mode (Actions)'

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

@@ -0,0 +1,65 @@
+---
+title: LinkedIn Audiences Destination
+hide-personas-partial: true
+hide-boilerplate: true
+hide-dossier: false
+id: 62f435d1d311567bd5bf0e8d
+---
+
+
+LinkedIn Audiences enables advertisers to send Segment Engage Audiences to LinkedIn as Matched Audiences using [LinkedIn's API](https://learn.microsoft.com/en-us/linkedin/marketing/integrations/matched-audiences/matched-audiences){:target="_blank"}.
+
+By using Segment's Engage Audiences with LinkedIn, you can increase traffic and drive conversions with hyper-relevant ads that promote product discovery.
+
+> info ""
+> The LinkedIn Audiences destination is in beta and is in active development. Some functionality may change before it becomes generally available.
+
+## Getting Started
+
+Before connecting to the LinkedIn Audiences destination, you must have a [LinkedIn Campaign Manager](https://www.linkedin.com/campaignmanager){:target="_blank"} account and an Ad Account ID. In addition, the user authenticating with LinkedIn must have one of the following LinkedIn ad account roles: `ACCOUNT_BILLING_ADMIN`, `ACCOUNT_MANAGER`, `CAMPAIGN_MANAGER`, or `CREATIVE_MANAGER`.
+
+To add the LinkedIn Audiences destination:
+
+1. From the Segment web app, navigate to **Engage > Audiences**. Ensure you are in the Engage space you plan to use with LinkedIn Audiences. Either choose an existing Engage Audience or create a new one. This is the Audience you plan to send to LinkedIn.
+
+2. Within the Audience, click **Settings** and copy the Audience Key. You'll need this key later.
+
+3. Navigate to **Engage > Engage Settings** and click **Destinations**. Please ensure you are still in the correct Engage space.
+
+4. Search for “LinkedIn Audiences” and select the destination.
+
+5. Click **Configure LinkedIn Audiences**.
+
+6. On the Select Source screen, your Engage space should already be selected as the source. Click **Confirm Source**.
+
+7. On the Destination **Settings** tab, name your destination and authenticate with LinkedIn using OAuth.
+
+8. Once authenticated, input your LinkedIn Ad Account ID from your [LinkedIn Campaign Manager](https://www.linkedin.com/campaignmanager){:target="_blank"} account. Toggle “Enable Destination” on and click  **Save Changes**.
+
+9. Navigate to the **Mappings** tab, click **New Mapping**, and select **Sync To LinkedIn DMP Segment**.
+
+10. Under Select mappings, input the Audience Key you copied in Step 2 as the “Segment Engage Audience Key.” Do not change any other defaults. Click **Save** and toggle to enable the mapping.
+     * **Note:** The Audience Key must be manually entered to ensure users in the Engage Audience are sent to the correct DMP Segment in LinkedIn. For every Engage Audience you want to send to your LinkedIn Ads Account, a separate **Sync To LinkedIn DMP Segment** mapping must be created. You can create up to 50 mappings within an instance of the LinkedIn Audiences destination.
+
+11. Navigate back to **Engage > Audiences** and click on the Audience from Step 1. 
+
+12. Click **Add Destinations** and select the LinkedIn Audiences destination you just created. In the settings that appear in the side panel, toggle the **Send Track** option on and disable **Send Identify**. Click **Save Settings**.
+
+![engage audience destination settings](images/image1.png)
+
+The setup is complete and the Audience will start syncing to LinkedIn. Segment automatically creates a new DMP Segment in LinkedIn and will add or remove users accordingly. The Audience appears in your [LinkedIn Campaign Manager](https://www.linkedin.com/campaignmanager){:target="_blank"}, account under **Plan > Audiences > Matched**.
+
+To sync additional Audiences from your Engage space, create a separate mapping in the LinkedIn Audiences destination. Navigate to **Connections > Destinations**, search and select the LinkedIn Audiences destination, and follow Steps 9-11 above.
+
+{% include components/actions-fields.html settings="true"%}
+
+## Troubleshooting
+
+### Access & Refresh Tokens
+LinkedIn's OAuth access tokens have a time to live (TTL) of 60 days; refresh tokens have a TTL of one year. Segment automatically updates your access token as long as your refresh token is valid. You won't see any errors or interruptions in data delivery if your access token expires while your refresh token is valid.
+
+Upon expiry or revocation of a refresh token, you'll see `Refresh Token Expired` errors in the Delivery Issues section of your LinkedIn Audiences destination **Event Delivery** tab.
+
+Unknown errors from LinkedIn related to OAuth appear as `Oauth Refresh Failed`.
+
+To remedy either error, please navigate to the **Settings** tab of your LinkedIn Audiences destination and select **Reauthorize** under the Connection heading and complete the OAuth flow.