Merge pull request #3545 from segmentio/develop

Release 22.38.2

Author: rchinn1

Gemfile.lock

@@ -31,7 +31,7 @@ GEM
       httpclient (~> 2.8, >= 2.8.3)
       json (>= 1.5.1)
     colorator (1.1.0)
-    commonmarker (0.23.4)
+    commonmarker (0.23.6)
     concurrent-ruby (1.1.9)
     dotenv (2.7.6)
     em-websocket (0.5.2)

package-lock.json

@@ -36,7 +36,7 @@
     "superagent": "^6.1.0",
     "webpack": "^5.53.0",
     "webpack-cli": "^4.8.0",
-    "yaml-lint": "^1.2.4"
+    "yaml-lint": "^1.7.0"
   },
   "dependencies": {
     "@algolia/autocomplete-js": "^1.4.0",
@@ -46,7 +46,7 @@
     "ajv": "^6.10.2",
     "algoliasearch": "^4.10.5",
     "ansi-regex": "^6.0.1",
-    "browser-sync": "^2.27.7",
+    "browser-sync": "^2.27.10",
     "check-links": "^1.1.8",
     "clipboard": "^2.0.8",
     "diff": "^5.0.0",

package.json

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2022-09-20 
+# destination categories last updated 2022-09-22 
 items:
 - display_name: A/B Testing
   slug: a-b-testing

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2022-09-20 
+# destination data last updated 2022-09-22 
 items:
 - id: 60b5d0a01f3726b85dc05aab
   display_name: 2mee
@@ -37569,13 +37569,13 @@ items:
 - id: 61957755c4d820be968457de
   display_name: Salesforce (Actions)
   name: Salesforce (Actions)
-  slug: salesforce-actions
-  hidden: true
+  slug: actions-salesforce
+  hidden: false
   endpoints:
   - us
   regions:
   - us
-  url: connections/destinations/catalog/salesforce-actions
+  url: connections/destinations/catalog/actions-salesforce
   previous_names:
   - Salesforce (Actions)
   website: https://www.salesforce.com/products/sales-cloud/overview/

src/_data/catalog/destinations.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED LIST OF CONNECTIONS THAT SUPPORT REGIONAL
-# Last updated 2022-09-20 
+# Last updated 2022-09-22 
 warehouses:
   - id: WcjBCzUGff
     display_name: Azure SQL Data Warehouse
@@ -3353,8 +3353,8 @@ destinations:
       - us
   - id: 61957755c4d820be968457de
     display_name: Salesforce (Actions)
-    slug: salesforce-actions
-    url: connections/destinations/catalog/salesforce-actions
+    slug: actions-salesforce
+    url: connections/destinations/catalog/actions-salesforce
     regions:
       - us
     endpoints:

src/_data/catalog/regional-supported.yml

@@ -43,4 +43,6 @@
 - original: "mixpanel-actions"
   override: "actions-mixpanel"
 - original: "rokt"
-  override: "rokt-integration"
+  override: "rokt-integration"
+- original: "salesforce-actions"
+  override: "actions-salesforce"

src/_data/catalog/slugs.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source cateogries last updated 2022-09-20 
+# source cateogries last updated 2022-09-22 
 items:
   - display_name: A/B Testing
     slug: a-b-testing

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# sources last updated 2022-09-20 
+# sources last updated 2022-09-22 
 items:
   - id: 8HWbgPTt3k
     display_name: .NET

src/_data/catalog/sources.yml

@@ -16,6 +16,7 @@
 {% assign settings = currentIntegration.settings %}
 {% assign actions = currentIntegration.actions %}
 {% assign presets = currentIntegration.presets %}
+{% assign hiddenActions = page.hide_action | map: "id"%}
 
 
 {% if settings.size > 0 %}
@@ -81,7 +82,6 @@
 
 ## Available Actions
 
-
 Build your own Mappings! Combine supported [triggers](/docs/connections/destinations/actions/#components-of-a-destination-action) with the following {{currentIntegration.display_name | remove: " (Actions)"}}-supported actions:
 
 <div class="premonition info">
@@ -93,10 +93,13 @@
 </div>
 
 {% for action in actions %}
+{% unless hiddenActions contains action.id %}
 - [{{action.name}}](#{{action.name | slugify}})
+{% endunless %}
 {% endfor %}
 
 {% for action in actions %}
+{% unless hiddenActions contains action.id %}
 ### {{action.name}}
 <p>{{action.description | markdownify}}</p>
 <p>{{action.name}} is a <strong>{{action.platform | capitalize}}</strong> action. The default Trigger is:</p> <code>{{action.defaultTrigger}}</code>
@@ -136,6 +139,6 @@
 {% else %}
 This action does not have any fields.
 {% endif %}
-
+{% endunless %}
 {% endfor %}
 

src/_includes/components/actions-fields.html

@@ -11,7 +11,7 @@
 <tbody>
   {% for dest in actionsDests %}
   {% unless dest.hidden == true %}
-  {% if dest.actions.size > 0 || dest.actions.presets.size > 0%}
+  {% if dest.actions.size > 0 %}
   <tr>
     <td><a href="/docs/{{dest.url}}">{{dest.name}}</a></td>
     <td>{% if dest.status == "PUBLIC_BETA" %}Beta {% else %} GA {%endif%}</td>

src/_includes/components/available-actions.html

@@ -37,15 +37,15 @@ Intercom Cloud Mode (Actions) provides the following benefits over the classic I
 3. Click **Configure Intercom Cloud Mode (Actions)**.
 4. Select the source that will send data to Intercom Cloud Mode (Actions) and follow the steps to name your destination.
 5. On the **Settings** tab, authenticate with Intercom using OAuth.
-6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
+6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customize-mappings).
 7. Enable the destination and configured mappings.
 
-{% include components/actions-fields.html settings="true"%}
+{% include components/actions-fields.html %}
 
 ## FAQ & Troubleshooting
 
 ### Why is a company I created missing from my Intercom dashboard?
 If a company is created without an attached user, the company does not appear on Intercom's dashboard. This is expected. Once a user is attached to the company, it should appear in the list of companies.
 
 ### Why isn’t a user getting attached to a company?
-When you use the Identify Company action, Segment creates or updates a company's information. In the same action, Segment also attaches the user in your group call to that company. If the user doesn't exist in Intercom when the action runs, Segment creates or updates the company but not attach the user. Ensure the user is created in Intercom first.
+When you use the Identify Company action, Segment creates or updates a company's information. In the same action, Segment also attaches the user in your group call to that company. If the user doesn't exist in Intercom when the action runs, Segment creates or updates the company but can't attach the user. Ensure the user is created in Intercom first.

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

@@ -5,6 +5,11 @@ hide-dossier: false
 hidden: true
 private: true
 id: 62d9daff84a6bf190da9f592
+hide_action:
+  - id: 5W984Qq59XEQnFYKXKHGeZ
+    name: "Update User"
+  - id: nqdBJoXJwFrzwoL1y45LYt
+    name: "Update Company"
 versions:
   - name: 'Intercom Cloud Mode (Actions)'
     link: '/docs/connections/destinations/catalog/actions-intercom-cloud'

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

@@ -52,7 +52,7 @@ analytics.identify('user1234', {
 ```
 
 > info ""
-> HubSpot's device-mode integration has two conditions for Identify to create or update a contact. Identify calls must include a `traits.email` value and need to go with a Page or Track call. You can read more from HubSpot's documentation [here](https://developers.hubspot.com/docs/methods/tracking_code_api/identify_visitor){:target="_blank"}. If you are using HubSpot's cloud-mode integration, an Identify call will update records without the need for a Page or Track call.
+> HubSpot's device-mode integration has two conditions for Identify to create or update a contact: 1) Identify calls must include a `traits.email` value. 2) A Page or Track call must follow an Identify call. You can read more from [HubSpot's documentation](https://developers.hubspot.com/docs/methods/tracking_code_api/identify_visitor){:target="_blank"}. If you are using HubSpot's cloud-mode integration, an Identify call updates records without the need for a Page or Track call.
 
 HubSpot does not accept any trait keys that contain upper case letters or spaces. Segment converts any custom traits you send to lower case, and replaces spaces with an underscore.
 

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

@@ -158,7 +158,7 @@ If you do move key checkout events to the server side, you will have to manually
 
 *   **UTM parameters**: collecting the UTM params will allow you to tie conversion events to your marketing campaign or activities. This is valuable in that you can immediately measure performance and calculate ROI on your campaigns.
 
-*   **IP address**: the IP address can provide location intelligence for your customers. This means you can personalize your shopping experience or engagement emails with inventor that might be more relevant depending on your customers' locations.
+*   **IP address**: the IP address can provide location intelligence for your customers. This means you can personalize your shopping experience or engagement emails with inventory that might be more relevant depending on your customers' locations.
 
 *   **User Agent**: the User Agent will inform you of your customers' preferred device and shopping experience. Are they converting on a mobile web browser? Native app? Or on their laptop?
 

src/guides/how-to-guides/cross-channel-tracking.md

@@ -69,6 +69,11 @@ Regional Segment in the EU changes the way you [configure the Data Lakes AWS env
 ### Warehouse Public IP Range
 Use Segment's custom CIDR `3.251.148.96/29` while authorizing Segment to write in to your Redshift or Postgres port. [BigQuery](/docs/connections/storage/catalog/bigquery/#getting-started) doesn't require you to allow a custom IP address.
 
+## Known Limitations
+-   Regional Segment is currently limited to the EU. Future expansion of Regional Segment beyond the EU is under evaluation by Segment Product and R&D.
+    
+-   Edge proxies are deprecated. Customers using edge proxies may see US-based IP addresses in event payloads. For EU customers, Segment recommends using a Regionalized EU workspace. For non-EU customers, Segment recommends using the US-based endpoint (`api.segment.io`) to preserve client IP addresses.
+
 ## Destination support and Regional endpoint availability
 
 > info "Don't see a regional endpoint for a tool you're using?"

src/guides/regional-segment.md

@@ -177,7 +177,7 @@ You can read the [full Profile API docs](/docs/personas/profile-api/) to learn m
 
 ## Download your Audience as a CSV file
 
-You can download a copy of your Audience by visiting the the Audience overview page.
+You can download a copy of your Audience by visiting the Audience overview page.
 ![Downloading an Audience as a CSV file](/docs/personas/images/audience_overview.png)
 Before you can download the CSV, you will need to generate it. There are three different options for formatting: