Add ID to Userpilot Docs

Author: pwseg

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

@@ -1,7 +1,8 @@
 
 ---
 title: Userpilot Cloud (Actions) Destination
-id: <integration_id>
+id: 647f30a35eedd03afde0a1c3
+beta: true
 ---
 
 {% include content/plan-grid.md name="actions" %}
@@ -23,14 +24,13 @@ This destination is maintained by Userpilot. For any issues with the destination
 
 ### Overview
 
-The Userpilot cloud mode destination utilizes [Userpilot’s REST APIs](https://docs.userpilot.com/article/195-identify-users-and-track-api){:target="_blank"} to transmit user data and associated events directly to Userpilot. This enables you to leverage Userpilot’s capabilities based on the real-time data received from your application.
+The Userpilot cloud-mode destination uses [Userpilot’s REST APIs](https://docs.userpilot.com/article/195-identify-users-and-track-api){:target="_blank"} to transmit user data and associated events directly to Userpilot. This lets you use Userpilot’s capabilities based on the real-time data received from your application.
 
 - **User Identification** Send [Identify](/docs/connections/spec/identify/) calls from Segment to Userpilot for identifying or updating user and company properties. This data is dispatched directly from your backend servers and can be used for segmenting users and triggering personalized content in real-time
 
 - **Event Tracking:** Segment [Track](/docs/connections/spec/track/) calls are converted into Userpilot events. This feature captures user actions on your web application, allowing you to build a comprehensive understanding of your user's overall experience. You can trigger live, targeted content based on certain user actions like clicking a button or completing a transaction.
 
-
-It's important to remember that each Identify and Track call is sent to Userpilot’s server directly without being affected by the user’s browser settings. This direct server-to-server communication enables a more reliable and secure data transfer.
+Each Identify and Track call is sent to Userpilot’s server directly without being affected by the user’s browser settings. This direct server-to-server communication enables a more reliable and secure data transfer.
 
 Remember to follow Segment’s API rate limits to ensure your data is being sent at an acceptable rate. Always check Userpilot’s API documentation for the most recent information on how to set up Userpilot as a Cloud Mode Destination in Segment.
 
@@ -43,5 +43,4 @@ If you experience any issues while setting up Userpilot as a destination, follow
 
 - Check your Userpilot API Key. Make sure it's correctly entered in Segment.
 - Verify that you've enabled Userpilot as a destination in Segment.
-- If you're still having trouble, contact Segment's support team for further assistance.
-
+- If you're still having trouble, contact Segment's support team for further assistance.

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

@@ -1,7 +1,8 @@
 
 ---
 title: Userpilot Web (Actions) Destination
-id: <integration_id>
+id: 6480b4eeab29eca5415089d4
+beta: true
 ---
 
 {% include content/plan-grid.md name="actions" %}
@@ -44,10 +45,10 @@ analytics.identify('userId123', {
 
 Calling `identify` from `analytics.js` will trigger the `userpilot.identify`. We recommend passing as much data as possible to get the most out of Userpilot.
 
-Data passed in the `identify` can be organized under different categories.
-* Properties about the user such as `plan` or `userRole` to help targetting a specifc segment.
-* Properties to personalize the content of the Userpilot experiences such as `name` or `company`.
-* Properties to target users based on their lifecycle such as `createdAt`. This will allow you to target newly created accounts or accounts that have yet to achieve a certain feature in the user lifecyle.
+Data passed in an Identify call can be organized under different categories.
+* Properties about the user such as `plan` or `userRole` to help targeting a specifc segment
+* Properties to personalize the content of the Userpilot experiences, such as `name` or `company`
+* Properties to target users based on their lifecycle, such as `createdAt`, which allows you to target newly created accounts or accounts that have yet to achieve a certain feature in the user lifecyle
 
 
 ## Track