# Ascend

## Snapshot

| Features                        | Details                                           |
| ------------------------------- | ------------------------------------------------- |
| Release Status                  | Released                                          |
| Source API Version              | 20120402                                          |
| Table Selection                 | Yes                                               |
| Column Selection                | Yes                                               |
| Edit Integration                | Yes                                               |
| Replication Type Selection      | No                                                |
| Authentication Parameters       | Api Key                                           |
| Replication Type                | <p>Key Based Replication,<br>Full Replication</p> |
| Replication Key                 | Date                                              |
| Suggested Replication Frequency | 1 hour                                            |

## **Tables/APIs Supported**

| CreativePerformance        | PublisherDetails    |
| -------------------------- | ------------------- |
| ItemisedProductTransaction | PaymentsAndFees     |
| PublisherPerformance       | OrderCommissionRule |
| TransactionHistory         |                     |

## Generating Access Token for Ascend

* Login to <https://www.ascendpartner.com/>
* Click on LogIn
* Enter email and password
* Once logged in, go to Resources > API keys
* You can find the **API Key** for your account here
* Use this api key while creating an integration with Daton

## Integrate Ascend with Daton

1. Sign in to Daton
2. Select Ascend from Integrations page
3. Provide Integration Name Replication Frequency and History. Integration name would be used in creating tables for the integration and cannot be changed later
4. In the next step you will be asked to enter ascend api key
5. Post successful authentication you will be prompted to choose required tables from the list
6. Then select all required fields
7. Submit the integration

## Workflow

1. Integrations would be in Pending state initially and will be moved to Active state as soon as the first job loads data successfully on to the configured warehouse
2. Users would be able to edit/pause/re-activate/delete integration anytime
3. Users can view job status and process logs from the integration details page by clicking on the integration name from the active list

## Ascend Data

### CreativePerformance <a href="#billable-items" id="billable-items"></a>

Purpose: This API gives performance metrics of Creatives(like banners, coupons etc..)

Source API Documentation: <https://support.ascendpartner.com/s/advertiser-api-documentation#CreativeDetails>

Replication: Key Based Incremental

Replication Key: startDate, endDate

**Fields**

| Name                 | Data Type |
| -------------------- | --------- |
| creative\_id         | NUMERIC   |
| creative\_type       | STRING    |
| creative\_name       | STRING    |
| publisher\_id        | NUMERIC   |
| publisher            | STRING    |
| date                 | DATE      |
| affiliate\_usage     | NUMERIC   |
| impressions          | NUMERIC   |
| transactions         | NUMERIC   |
| clicks               | NUMERIC   |
| click\_through\_rate | STRING    |
| sales                | STRING    |
| earnings\_per\_click | STRING    |
| commission           | STRING    |

### ItemisedProductTransactions <a href="#billable-items" id="billable-items"></a>

Purpose: This API is used to fetch itemised product transactions

Source API Documentation: <https://support.ascendpartner.com/s/advertiser-api-documentation#ItemizedTransactions>

Replication: Key Based Incremental

Replication Key: startDate, endDate

**Fields**

| Name                 | Data Type |
| -------------------- | --------- |
| order\_id            | STRING    |
| sale\_date           | DATETIME  |
| status               | STRING    |
| publisher\_id        | NUMERIC   |
| link\_type           | STRING    |
| publisher\_type      | STRING    |
| item\_category\_name | STRING    |
| sale\_amount         | STRING    |
| commission           | STRING    |
| item\_name           | STRING    |
| publisher            | STRING    |
| company              | STRING    |
| transaction\_id      | NUMERIC   |
| item\_id             | STRING    |
| quantity             | NUMERIC   |

### PublisherPerformance <a href="#billable-items" id="billable-items"></a>

Purpose: This API is used to fetch metrics of each publisher performance

Source API Documentation: <https://support.ascendpartner.com/s/advertiser-api-documentation#PublisherPerformance>

Replication: Key Based Incremental

Replication Key: startDate, endDate

**Fields**

| Name                  | Data Type |
| --------------------- | --------- |
| publisher\_id         | NUMERIC   |
| date                  | DATE      |
| impressions           | NUMERIC   |
| clicks                | NUMERIC   |
| sales                 | NUMERIC   |
| leads                 | NUMERIC   |
| sale\_lead\_amount    | STRING    |
| earnings\_per\_click  | STRING    |
| bonus\_amount         | STRING    |
| total\_commission     | STRING    |
| site\_bonus           | STRING    |
| site\_commission      | STRING    |
| publisher\_bonus      | STRING    |
| publisher\_commission | STRING    |
| publisher\_type       | STRING    |
| publisher             | STRING    |
| company               | STRING    |
| state                 | STRING    |
| website               | STRING    |

### TransactionHistory <a href="#billable-items" id="billable-items"></a>

Purpose: This API is used to fetch publisher transaction history details

Source API Documentation: <https://support.ascendpartner.com/s/advertiser-api-documentation#TransactionHistory>

Replication: Key Based Incremental

Replication Key: startDate, endDate

**Fields**

| Name                  | Data Type |
| --------------------- | --------- |
| publisher\_id         | NUMERIC   |
| transaction\_id       | NUMERIC   |
| sale\_date            | DATETIME  |
| order\_id             | NUMERIC   |
| status                | STRING    |
| link\_type            | STRING    |
| transaction\_type     | STRING    |
| publisher\_type       | STRING    |
| commission            | STRING    |
| sale\_amount          | STRING    |
| publisher\_commission | STRING    |
| site\_commission      | STRING    |
| process\_date         | DATETIME  |
| revision              | NUMERIC   |
| item\_id              | STRING    |
| publisher             | STRING    |
| company               | STRING    |
| website\_url          | STRING    |

### PublisherDetails <a href="#billable-items" id="billable-items"></a>

Purpose: This API is used to fetch information regarding publisher

Source API Documentation: <https://support.ascendpartner.com/s/advertiser-api-documentation#Publisher>

Replication: Full Replication

Replication Key: N/A

**Fields**

| Name                         | Data Type |
| ---------------------------- | --------- |
| transparency                 | NUMERIC   |
| id                           | NUMERIC   |
| first\_name                  | STRING    |
| last\_name                   | STRING    |
| company                      | STRING    |
| state                        | STRING    |
| country                      | STRING    |
| website                      | STRING    |
| primary\_promotional\_method | STRING    |
| status                       | STRING    |
| request\_date                | STRING    |
| join\_date                   | STRING    |

### PaymentAndFees <a href="#billable-items" id="billable-items"></a>

Purpose: This API is used to fetch all the payments and fees paid in the given timeframe

Source API Documentation: <https://support.ascendpartner.com/s/advertiser-api-documentation#PaymentsAndFees>

Replication: Key Based Incremental

Replication Key: startDate, endDate

**Fields**

| Name        | Data Type |
| ----------- | --------- |
| id          | NUMERIC   |
| date        | DATETIME  |
| type        | STRING    |
| method      | STRING    |
| amount      | STRING    |
| description | STRING    |

### OrderComissionRule <a href="#billable-items" id="billable-items"></a>

Purpose: This API will break down transactions based on how a Dynamic term pays out on the transaction. This is a child table that fetches transaction\_ids from transaction\_details table(Incremental) internally and uses it to fetch orderComissionRules data.

Source API Documentation: <https://support.ascendpartner.com/s/advertiser-api-documentation#OrderCommissionRule>

Replication: Key Based&#x20;

Replication Key: startDate, endDate

**Fields**

| Name                         | Data Type |
| ---------------------------- | --------- |
| id                           | NUMERIC   |
| order\_id                    | NUMERIC   |
| is\_new\_to\_file            | STRING    |
| order\_date                  | DATETIME  |
| sale\_amount                 | STRING    |
| transaction\_payout\_amount  | STRING    |
| transaction\_payout\_level   | NUMERIC   |
| total\_publisher\_commission | NUMERIC   |
| total\_site\_commission      | NUMERIC   |
| custom\_segment\_custom\_id  | STRING    |
| custom\_segment\_name        | STRING    |
| publisher\_referral\_url     | STRING    |
| total\_order\_commission     | STRING    |
| ruleId                       | NUMERIC   |
| action\_type                 | STRING    |
| action\_value                | STRING    |
| level                        | STRING    |
| publisher\_commission        | NUMERIC   |
| site\_commission             | NUMERIC   |
| commission                   | STRING    |
| item\_name                   | STRING    |
| quantity                     | NUMERIC   |
| category\_id                 | STRING    |
| category\_name               | STRING    |
| item\_price                  | STRING    |

<br>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://daton-sarasanalytics.gitbook.io/daton/integrations/data-sources/saas-integrations/ascend.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.