> For the complete documentation index, see [llms.txt](https://docs.onlymonster.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onlymonster.ai/management-system/team-metrics-for-fansly.md).

# Team Metrics for Fansly

Team Metrics is an analytical dashboard that helps you analyze how members interact with fans and find areas where their performance can be improved.

The dashboard consists of three tabs: **Overview**, **Transactions**, and **Sales Settings**.

{% hint style="info" %}
**Note:** Team Metrics opens on OnlyFans by default. To see Fansly data, switch the **Platform** filter to **Fansly**. Metrics for OnlyFans accounts are described in the [Team Metrics article](https://docs.onlymonster.ai/management-system/team-metrics-for-onlyfans.md).&#x20;
{% endhint %}

### Filters

Filters are located above the table. The values in the table update when you change any of them.

| Filter       | Description                                                                                                                                        | Default       |
| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- |
| Time Range   | Sets the period for the data. Supports exact time selection down to the minute.                                                                    | Last 24 hours |
| Accounts     | Select one or multiple accounts, or select an account group to add all of its accounts at once. Groups are created in the **Accounts** tab.        | All Accounts  |
| Members      | Select one or multiple members to display statistics for those members only.                                                                       | All Members   |
| Roles        | Select a role to filter members by it. The list is built from the roles in your organization. Only one role can be selected at a time.             | All Roles     |
| Earning Type | **Net** — earnings after Fansly commission. **Gross** — earnings including Fansly commission. Switching the type recalculates all revenue metrics. | Net           |
| Platform     | Switches the table between **OnlyFans** and **Fansly**.                                                                                            | OnlyFans      |

#### Time Range

* **Custom range:** select the start and end dates, and set the exact time if needed.
* **Quick ranges:** Last 24 hours, Today, Yesterday, This week, Last week, This month, Last month, This year, Last 7 / 14 / 30 / 60 / 90 / 180 / 365 days.
* **By month:** select any month of the current year.
* **Maximum period:** data can be viewed for up to 365 days.
* **Apply / Reset:** click **Apply** to confirm the selected range, or **Reset** to clear it.
* **Time zone:** choose **UTC+00:00** (default) or your **Organization Time Zone**.

#### Platform

When **Fansly** is selected:

* The table shows only the members' Fansly data. If a member works on both platforms, the values are calculated separately for each platform.
* The columns follow the selected platform. For Fansly, the table shows the metrics listed in the Metrics section below.
* The **Accounts** filter lists only Fansly accounts.

### Metrics

Each row in the table is a member. The columns appear in the table in the order listed below.

| Metric                  | Description                                                                                                                                          |
| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| Member                  | The member's name and ID.                                                                                                                            |
| Accounts                | The accounts the member worked on during the selected time range.                                                                                    |
| Total Revenue           | Total revenue generated by the member. Calculated as Media Revenue + Media Sets Revenue + Tips + Subscription Revenue.                               |
| Media Revenue           | Revenue from media sales.                                                                                                                            |
| Media Sets Revenue      | Revenue from media set sales.                                                                                                                        |
| Tips                    | Revenue from all tip transactions.                                                                                                                   |
| Subscription Revenue    | Revenue from subscriptions assigned to the member, including renewals.                                                                               |
| Media Sold              | Number of media purchased by fans.                                                                                                                   |
| Media Sets Sold         | Number of media sets purchased by fans.                                                                                                              |
| Total Messages Sent     | Number of messages sent by the member, excluding Mass Messages, Priority Messages, Auto Messages, Scheduled Messages, and messages sent by Mimic AI. |
| Manually Typed Messages | Number of messages written and sent manually, excluding AI Replies, Templates, Mass Messages, and copy-pasted messages.                              |
| Copy-Paste Count        | Number of messages sent via copy-paste.                                                                                                              |
| Free Media Sent         | Number of messages with at least one free media outside a media set.                                                                                 |
| Free Media Set Sent     | Number of messages with at least one media set that contains only free media.                                                                        |
| Unsent Messages         | Number of messages unsent by the member.                                                                                                             |
| Words                   | Total number of words written and sent by the member.                                                                                                |
| Avg. Words per Message  | Average word count in manually typed messages. Calculated the same way as for OnlyFans.                                                              |
| Total Chats             | Number of unique chats where the member sent manually typed messages.                                                                                |

### Working with the table

* **Sorting:** click any column header to sort members in ascending or descending order.
* **Search:** use the **Search** field to find a member in the table.
* **Columns:** click the column selector icon next to **Search** to hide, show, or reorder columns by dragging and dropping. All columns are visible by default, and your column settings are saved.
* **Pinned Member column:** the **Member** column stays in place when you scroll the table horizontally.
* **Average and Total rows:** the two rows at the bottom of the table summarize the members currently displayed. Metrics that cannot be summed, such as **Avg. Words per Message**, show a dash in the Total row.
* **Empty values:** if there is no data for a value, the table shows a dash (-). A zero value is shown as 0.

### Custom Metrics

Custom Metrics let you create your own metrics by combining existing ones with simple arithmetic. They work the same way as in Accounts Overview and Traffic Metrics.

{% hint style="info" %}
**Note:** Custom Metrics are shared between OnlyFans and Fansly. If a metric is not available on one of the platforms, this is indicated.&#x20;
{% endhint %}

To create one:

1. Click **Custom Metrics**.
2. Click **+ New Metric**.
3. Enter a **Metric Name** and, optionally, a **Description**.
4. Build a **Formula**: use **Add Metric** to pick any metric available in Team Metrics, and combine metrics with the +, −, ×, ÷ and ( ) operators.
5. Choose an **Aggregation** — Sum, Avg, or None — and toggle **With decimals** if needed.
6. Select the output format: $, %, or #.
7. Click **Save**.

Saved custom metrics appear as additional columns in the table and can be shown, hidden, or reordered like any other column.

### Export

Click **Export** and select **XLSX** or **CSV**. The file contains the data currently displayed in the table: it respects the selected filters and visible columns, and includes the Average and Total rows.

### Member Overview

Each member has an **Overview** button. Click it to open Member Overview — a view focused on a single member. Its tables show the member's metrics broken down by account, across all accounts the member is assigned to.

### Sales Settings

The **Sales Settings** tab defines how sales are automatically attributed to members. You can configure attribution separately for each sale type, so the dashboard reflects the way your team actually works.

Attribution is configured per platform: **OnlyFans** and **Fansly** are separate tabs of the Sales Settings screen. Settings on the **Fansly** tab apply to Fansly accounts only.

#### Sale types and attribution rules

Fansly does not disclose the source of a transaction — a media sale looks the same whether the media was sold in a message or in a post. Because of this, **Message Sender** is available only for Message sales, where OnlyMonster tracks who sent the media. For other sale types, the sender is unknown, so this rule is not offered.

You can configure the following sale types. Each of them can be turned on or off.

* **Message:** media sold in messages.
* **Posts:** media sold in posts.
* **Tips:** tips sent by fans.
* **Subscription:** subscription payments, including renewals.
* **Streams:** sales made during streams.

Available rules for each sale type:

| Sale type    | Message Sender | Last Active Member | Cents Fingerprint | Not Assigned |
| ------------ | :------------: | :----------------: | :---------------: | :----------: |
| Message      |        ✓       |          ✓         |         ✓         |       ✓      |
| Posts        |        —       |          ✓         |         ✓         |       ✓      |
| Tips         |        —       |          ✓         |         —         |       ✓      |
| Subscription |        —       |          ✓         |         —         |       ✓      |
| Streams      |        —       |          ✓         |         —         |       ✓      |

What each rule does:

* **Message Sender:** the sale is assigned to the member who sent the message with the media.
* **Last Active Member:** the sale is assigned to the last member who messaged the fan within the selected time frame before the purchase. Any message counts, not only the purchased one.
* **Cents Fingerprint:** the sale is assigned by the cents value of the transaction amount.
* **Not Assigned:** the sale isn't assigned to anyone.

#### Default settings

Until you change the settings, Fansly uses the following rules:

| Sale type    | Default rule       |
| ------------ | ------------------ |
| Message      | Message Sender     |
| Posts        | Last Active Member |
| Tips         | Last Active Member |
| Subscription | Last Active Member |
| Streams      | Last Active Member |

The default Last Active Member time frame is **60 minutes** before the purchase.

#### Last Active Member time frame

Every rule based on Last Active Member requires a time frame — the period before the purchase during which a member's message still counts for attribution. Set it in hours and minutes directly in the rule description.

* **Minimum:** 1 minute
* **Maximum:** 12 hours

If no member messaged the fan within this period, the transaction stays unassigned.

#### Cents Fingerprint

Cents Fingerprint attributes a sale by the cents value of its amount. On the **Fansly** tab, enter a cents value for each member separately for each sale type: in the **Message cents** field for Message and in the **Posts cents** field for Posts — for example, `.50` for Message and `.40` for Posts.

* If the sale amount ends in a member's cents value for a sale type, the sale is attributed to that member under that sale type.
* If no member matches, the sale stays unassigned.
* Cents are matched against the gross amount — the price set on the platform, before Fansly commission.
* Two members cannot share the same cents value.
* One member can use the same cents value for different sale types, for example, `.50` for both Message and Posts. In this case, the sale is attributed to the member, but the sale type cannot be distinguished by cents.

For example, if a member's **Message cents** is set to `.50` and a fan buys media priced at $12.50, the sale is attributed to this member.

Tips, Subscriptions, and Streams have no cents value and are attributed by Last Active Member or stay unassigned. For tips, the fan chooses the amount, and for subscriptions, the price is set on the profile, not by a member — so cents cannot identify who made the sale.

{% hint style="warning" %}
**Important!** Be careful when using Cents Fingerprint: any sale with a cents value that isn't assigned to a member stays unassigned and does not appear in any member's metrics.&#x20;
{% endhint %}

#### Saving changes

Changes take effect only after you click **Save Changes**. You can also choose the date and time from which the new rules start to apply.

Attribution changes are not retroactive. Sales made before the new rules take effect are attributed under the previous rules and are not redistributed, even if they are synchronized after the new rules start.

Sales Settings keeps the full history of settings changes:

* **Scheduled:** versions that will start to apply at the chosen date and time. Scheduled versions can be deleted.
* **Current:** the settings that are applied now.
* **Past versions:** the settings that were applied earlier.

For each version, you can see when and by whom the settings were changed or scheduled. Changed values are highlighted.

#### Unassigned sales

A sale stays unassigned when it doesn't match the selected rule. This can happen in the following cases:

* The cents value of the sale isn't assigned to any member.
* No member messaged the fan within the Last Active Member time frame.
* The sale type is set to **Not Assigned**.
* The **Message Sender** rule is selected, and the purchase was made more than 180 days after the message was sent.
* The **Message Sender** rule is selected, and the message was sent before September 15, 2026.

Unassigned sales are not included in any member's metrics. They can be assigned manually in the **Transactions** tab. After a sale is assigned manually, it appears in the member's metrics within 15 minutes.

### Permissions

Access to Team Metrics for Fansly is controlled by the same permissions as for OnlyFans.

| Permission        | Access                                                                                                             |
| ----------------- | ------------------------------------------------------------------------------------------------------------------ |
| View Metrics      | Access to the Team Metrics dashboard.                                                                              |
| View Transactions | Access to the Transactions tab without the ability to make changes. Automatically includes View Metrics.           |
| Edit Transactions | Enables assigning transactions to organization members. Automatically includes View Metrics and View Transactions. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.onlymonster.ai/management-system/team-metrics-for-fansly.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
