# Organization API: Organizations & Members: Acquisition

> The 1 Organization API operations for acquisition.

Source: https://www.coritan.com/docs/api/reference/organizations/organizations-members/acquisition/

Part of [Organizations & Members](/docs/api/reference/organizations/organizations-members/).

## Operations

| Method | Path | Summary |
| --- | --- | --- |
| GET | [`/api/v1/orgs/{org_slug}/acquisition`](#op-get-api-v1-orgs-org-slug-acquisition) | Acquisition report |

### Acquisition report {#op-get-api-v1-orgs-org-slug-acquisition}

`GET /api/v1/orgs/{org_slug}/acquisition`

Where the organization's visits, sign-ups, orders and revenue came from, over a period and against the one before it. Needs the Owner or Admin role.

The period is `from` to `to` in the brand's time zone, the last 30 days when left out, and at most 366 days. Every list holds at most `limit` rows, ranked by orders, then revenue, then visits. The totals always cover every row.

An order is a paid storefront order that is not free, counted in `currency`. Orders and revenue never mix currencies: `currencies` names every currency with an order in the period, and `currency` picks the one the answer is in. Revenue is the invoice total without tax, in that currency's minor units. A sign-up is a customer made through the storefront, so a customer the staff create is not one. A visit is a stored session with bots left out. Sessions are kept for 180 days, so `visits_complete` is false when the period starts earlier and the visit figures are partial.

The answer holds:

* `totals`: `visits`, `signups`, `orders`, `new_customers` (orders from a customer's first paid order), `revenue_minor` and `conversion_rate_bp` (orders over visits). `previous` holds the same figures for the earlier period, or null when `compare` is `none`. Every figure ending in `_bp` is basis points, so 123 is 1.23 percent.
* `channels`: each channel of the last touch with its `visits`, `signups`, `orders`, `new_customers`, `revenue_minor` and `share_bp` (its share of the orders). `first_touch` ranks the channels of the first touch, and `matrix` counts orders by first channel and last channel.
* `sources`, `campaigns`, `landing_pages` and `devices`: the same figures by the last touch's source and medium, its campaign, the page it landed on (the path, with no query and no language prefix) and the device.
* `click_ids`: how many orders carry an ad click ID, and for which ad network.
* `heard_about`: the answers to "How did you first hear about us?" with their share of the answered orders.
* `return`: the ad spend return report for the period in `currency` (`rows`, `totals`, `truncated`), or null when the organization has no ad spend in the period. `truncated` is true when the return report read only its first 50,000 orders.

A `from` after `to`, a period over 366 days, a `compare` other than `previous` or `none`, a `currency` that is not three letters and a `limit` outside 1 to 50 answer 422.

#### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `org_slug` | path | string | yes |  |
| `from` | query | string (date) or null | no | First day of the period, YYYY-MM-DD, in the brand's time zone. Left out, 29 days before the last day, so the period is the last 30 days. A period is at most 366 days. |
| `to` | query | string (date) or null | no | Last day of the period, YYYY-MM-DD, in the brand's time zone. Left out, today. |
| `compare` | query | string or null | no | `previous` (the default) sets every total against the same number of days just before the period, and a calendar month against the month before it. `none` leaves the comparison out. Default: `previous`. |
| `currency` | query | string or null | no | A three letter currency code. Orders and revenue are counted in this one currency and never added across currencies. Left out, the currency with the most revenue in the period, else the brand's own. |
| `limit` | query | integer | no | Rows in each ranked list, 1 to 50. Totals always cover every row. Left out, 10. Default: `10`. |

#### Responses

| Status | Meaning |
| --- | --- |
| `200` | Success. |
| `422` | The request is not valid. `detail` lists each problem. |