Merge pull request #3487 from segmentio/develop

Release 22.37.1

Author: pwseg

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

@@ -116,4 +116,6 @@ waitlist
 WebKit
 Wootric
 Xcode
-Zendesk
+Zendesk
+Leanplum
+Aircall

src/_includes/components/available-actions.html

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

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

@@ -54,7 +54,7 @@ The Client Deduplication ID allows for a 48-hour deduplication window. The Trans
 > Segment does not have client-side destinations for the Snap Pixel or Snap App Ads Kit (SDK). If you choose to integrate client-side, these must be implemented natively. See Snapchat’s [Install Snap Pixel](https://businesshelp.snapchat.com/s/article/pixel-website-install?language=en_US){:target="_blank"} and [App Ads Kit](https://businesshelp.snapchat.com/s/article/app-ads-kit?language=en_US){:target="_blank"} for implementation details.
 
 ### Latency
-It may take up to 1-hour for events to appear in the Snap [Events Manager](https://businesshelp.snapchat.com/s/article/events-manager?language=en_US){:target="_blank"}.
+It may take up to 1-hour for events to appear in the Snapchat [Events Manager](https://businesshelp.snapchat.com/s/article/events-manager?language=en_US){:target="_blank"}.
 
 ### Other events
 If you want to send a Snap Event Type that Segment doesn’t have a prebuilt mapping for, you can use the Report Conversion Event action to send the event. For example, if you want to send a `START_TRIAL` event:
@@ -82,3 +82,10 @@ In addition, Segment creates a SHA-256 hash of the following fields before sendi
 
 > warning ""
 > If you hash identifiers upstream before sending to Segment, Segment still hashes that data before sending to Snap. This results in a double hash that won't be able to be matched on. Please ensure your fields are not hashed prior to sending through the Snapchat Conversions API destination.
+
+## Support
+
+The Snap team owns and maintains the Snapchat Conversions API destination.
+
+- For general Segment questions, including issues with event data not being sent to the Snapchat Events Manager, please contact [Segment support](https://segment.com/help/){:target="_blank"}.
+- For questions regarding campaign setup and performance, audience targeting, or additional API functionality, please contact your Snap representative.

src/connections/destinations/category-compare.md

@@ -25,7 +25,12 @@ This page collates information about each destination, organized by category for
 </tr>
 {% for destination in site.data.catalog.destinations.items %}
 {% if destination.categories contains category.display_name %}
-{% unless destination.connection_modes.cloud.web == false and destination.connection_modes.cloud.mobile == false and destination.connection_modes.cloud.server == false and destination.connection_modes.device.web == false and destination.connection_modes.device.mobile == false  %}
+{% if destination.actions[0] %}
+<tr>
+  <td>**[{{ destination.display_name }}](/docs/{{ destination.url }})**</td>
+<td colspan=5 style="border-left: 1px solid gray;">This destination uses the <a href="/docs/connections/destinations/actions">Actions</a> framework.</td>
+</tr>
+{%else%}
 <tr>
   <td>**[{{ destination.display_name }}](/docs/{{ destination.url }})**</td>
   {% if overridesList contains destination.slug %}{% assign thisDestname = destination.slug %}{% assign thisDest = site.data.catalog.overrides.items | where: "slug", thisDestname | first%}
@@ -43,7 +48,7 @@ This page collates information about each destination, organized by category for
   <td style="border-left: 1px solid gray;">{% if destination.connection_modes.device.web %}✅{% else %}⬜️{% endif %} </td>
   <td>{% if destination.connection_modes.device.mobile %}✅{% else %}⬜️{% endif %} </td>
   {%endif%}</tr>
-{% endunless %}
+{%endif%}
 {% endif %}
 {% endfor %}
 </table>

src/connections/schema-unique-limits.md

@@ -4,7 +4,7 @@ title: Segment Schema Limits
 
 **How many unique events can be logged in my Segment Schema table?**
 
-While you can technically track unlimited events with Segment, only the first 2,000 events will be visible on the Schema page for a given Source. After you hit the 2,000 event limit, all future events will still be tracked and sent to your Destinations. They will not, however, be logged in the Segment Schema table.
+While you can technically track unlimited events with Segment, only the first 4,000 events will be visible on the Schema page for a given Source. After you hit the 4,000 event limit, all future events will still be tracked and sent to your Destinations. They will not, however, be logged in the Segment Schema table.
 
 **How many unique event properties can be logged on the event details page?**
 

src/connections/sources/catalog/libraries/mobile/react-native/index.md

@@ -510,6 +510,8 @@ To collect the Android Advertising ID provided by Play Services, Segment provide
 No, only the plugins listed above are supported in device-mode for Analytics React Native 2.0.
 ### Will I still see device-mode integrations listed as `false` in the integrations object?
 When you successfully package a plugin in device-mode, you won't see the integration listed as `false` in the integrations object for a Segment event. This logic is packaged in the event metadata, and isn't surfaced in the Segment debugger.
+### Why are my IDs not set in UUID format?
+Due to [limitations](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/uuid.ts#L5){:target="_blank"} with the React Native bridge, Segment doesn't use UUID format for `anonymousId`s and `messageId`s in local development. These IDs will be set in UUID format for your live app.  
 
 ## Changelog
 [View the Analytics React Native 2.0 changelog on GitHub](https://github.com/segmentio/analytics-react-native/releases){:target="_blank"}.

src/connections/sources/catalog/libraries/mobile/react-native/migration.md

@@ -6,7 +6,7 @@ strat: react-native
 If you're using `analytics-react-native 1.5.1` or older, follow these steps to upgrade to `analytics-react-native 2.0`. You can continue to use your React Native source write key for the upgrade to view historical events. Additionally, with React Native 2.0, you don't need to leverage bundled SDK packages, but can use [this list of supported destinations](/docs/connections/sources/catalog/libraries/mobile/react-native#supported-destinations).
 
 > info ""
-> Analytics React Native 2.0 implements a new storage framework, [@segment/sovran-react-native](https://github.com/segmentio/sovran-react-native){:target="_blank"}, which makes it impossible to determine if your app has been previously installed. Migrating to Analytics React Native 2.0 results in new `Application Installed` events for your existing users. To filter these events out you can either create an Enrichment Plugin to drop events or filter them using your Segment workspace.
+> Analytics React Native 2.0 implements a new storage framework, [@segment/sovran-react-native](https://github.com/segmentio/sovran-react-native){:target="_blank"}, which makes it impossible to determine if your app has been previously installed. Migrating to Analytics React Native 2.0 results in new `Application Installed` events for your existing users. To filter these events out you can either create an Enrichment Plugin to drop events or filter them using your Segment workspace. Furthermore, previously set `userId` values do not persist. Trigger an Identify event to reassign the `userId`. 
 
 To upgrade to React Native 2.0: