Merge pull request #7800 from motasem-userpilot/mobile-docs

Userpilot mobile destination

Author: stayseesong

src/connections/destinations/catalog/userpilot-mobile/index.md

@@ -0,0 +1,84 @@
+---
+title: Userpilot Mobile Device Mode Destination
+id: 68207e064c022255721ec2d3
+---
+
+Userpilot helps product teams deliver personalized in-app experiences to increase growth metrics at every stage of the user journey. When you integrate Userpilot with Segment, you can send your Segment events to Userpilot, enabling you to create more personalized experiences for your users across the product lifecycle.
+
+[Userpilot](https://www.userpilot.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} provides in-app guidance, product tours, and contextual onboarding experiences to help teams activate users and drive feature adoption.
+
+Userpilot maintains this destination. For any issues with the destination, [contact the Userpilot Support team](mailto:[email protected]).
+
+## Getting started
+
+1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank"}, search for *Userpilot Mobile (Device Mode)*.
+2. Select **Userpilot Mobile** and click **Add Destination**.
+3. Select an existing Source to connect to Userpilot.
+4. Go to the [Userpilot installation dashboard](https://run.userpilot.io/installation){:target="_blank"}, and copy your **App Token**.
+5. Enter the **App Token** in the Userpilot destination settings in Segment.
+
+## Supported methods
+
+Userpilot supports the following methods, as specified in the [Segment Spec](/docs/connections/spec).
+
+### Identify
+
+Send [Identify](/docs/connections/spec/identify) calls to associate a user with traits. These are used for segmentation, personalization, and lifecycle targeting.
+
+```swift
+analytics.identify(userId: "<USER_ID>", traits: [
+  "email": "[email protected]",
+  "name": "John Doe",
+  "plan": "Pro",
+  "createdAt": "2019-10-17"
+])
+```
+
+Calling Identify from Segment triggers `userpilot.identify`. Segment recommends passing as much data as possible to get the most out of Userpilot.
+
+Data passed in an Identify call can be organized under these different categories:
+* Properties about the user such as `plan` or `userRole` help target a specific 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 lifecycle
+
+These appear within Userpilot's user dashboard and power audience segmentation and targeting.
+
+### Group
+Send [Group](/docs/connections/spec/group) calls to associate users with an account, organization, or project.
+
+```swift
+analytics.group(groupId: "<GROUP_ID>", traits: [
+  "companyName": "Acme Inc.",
+  "subscriptionTier": "Enterprise"
+])
+```
+
+Calling Group from Segment triggers `userpilot.identify` with company-level traits, allowing you to use company metadata in targeting logic.
+
+
+### Screen
+Send [Screen](/docs/connections/spec/screen) calls to track navigation or screen changes in mobile apps.
+
+```swift
+analytics.screen(title: "Home")
+```
+
+Calling Screen from Segment triggers `userpilot.screen` event. This allows Userpilot to:
+* Trigger relevant experiences configured for specific pages/screens.
+* Check for ongoing experiences already running.
+
+
+### Track
+
+Send [Track](/docs/connections/spec/track) calls to log user actions or custom events.
+
+```swift
+analytics.track(name: "Added to Cart", properties: [
+  "itemId" : "sku_456",
+  "price" : 29.99
+])
+```
+
+Calling Track from Segment triggers `userpilot.track`. These custom events can be used to:
+* Trigger specific experiences (for example, a Carousel or Survey)
+* Monitor user behavior for analytics or lifecycle targeting