# AppFit (Actions) Destination

## Destination Info

* Accepts [Page](/docs/segment/connections/spec/page), [Alias](/docs/segment/connections/spec/alias), [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **App Fit**, **AppFit** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)
* This integration is **partner owned.** Please reach out to the partner's support for any issues.
* This destination is **Beta.**

[AppFit](https://appfit.io/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) integrates with Segment to help teams stay on top of their key business metrics. Successful teams look at their app metrics on a consistent basis and use that data to make decisions about their business.

When you connect AppFit to your Segment account, you get a top level dashboard for your mobile phone and weekly reminders to review your metrics. If you see a metric that doesn't look right, AppFit lets you flag it and add comments so everyone can discuss what's going on right from their phone.

This destination is maintained by AppFit. For any issues with the destination, [contact their Support team](mailto:support@appfit.io).

## Getting started

1. From the Segment web app, click **Catalog**, then click **Destinations**.
2. Find the Destinations Actions item in the left navigation, and click it.
3. Click **Configure AppFit**.
4. Select an existing Source to connect to AppFit (Actions).

To find your API key, go to the AppFit app and click on Connectors in the main menu. If you already have a Segment Destination connector created, you can click on it and find your API key there, otherwise you can create a new connector by clicking on "Create New Connector" and selecting "Segment Destination"

## Destination Settings

| Field   | Description              | Required | Type     |
| ------- | ------------------------ | -------- | -------- |
| API Key | AppFit project API key.  | Yes      | password |

## Available Actions

Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following AppFit-supported actions:

> \[!NOTE]
>
> Individual destination instances have support a maximum of 50 mappings.

* [Track](#track-9)

### Track

Send an event to AppFit.

Track is a **Cloud** action.

| Field                 | Description                         | Required | Type     |
| --------------------- | ----------------------------------- | -------- | -------- |
| External User ID      | The unique user identifier          | No       | STRING   |
| Time                  | When the event occurred.            | Yes      | DATETIME |
| Event Name            | The event name                      | Yes      | STRING   |
| Anonymous ID          | The anonymous ID of the user        | No       | STRING   |
| Event Properties      | Properties of the event             | No       | OBJECT   |
| App Version           | The app version                     | No       | STRING   |
| Device ID             | The device ID of the user           | No       | STRING   |
| Device Type           | The device type                     | No       | STRING   |
| Device Manufacturer   | The device manufacturer             | No       | STRING   |
| Device Model          | The device model                    | No       | STRING   |
| Device Advertising ID | The device advertising ID           | No       | STRING   |
| IP Address            | The IP address of the client        | No       | STRING   |
| OS Name               | The name of the operating system    | No       | STRING   |
| OS Version            | The version of the operating system | No       | STRING   |
| Event ID              | The event ID                        | Yes      | STRING   |

## Engage

You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo).

For user-property destinations, an [identify](/docs/segment/connections/spec/identify/) call is sent to the destination for each user being added and removed. The property name is the snake\_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property `order_completed_last_30days: true`. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to `false`.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

> \[!NOTE]
>
> Real-time audience syncs to AppFit (Actions)  may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.

## Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

| Field   | Description              | Required | Type     |
| ------- | ------------------------ | -------- | -------- |
| API Key | AppFit project API key.  | Yes      | password |