Ascend

Ascend by partnerise, ETL connector for data replication

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
Key Based Replication, Full Replication
Replication Key
Date
Suggested Replication Frequency
1 hour

Tables/APIs Supported

CreativePerformance
PublisherDetails
ItemisedProductTransaction
PaymentsAndFees
PublisherPerformance
OrderCommissionRule
TransactionHistory

Generating Access Token for Ascend

  • 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. 1.
    Sign in to Daton
  2. 2.
    Select Ascend from Integrations page
  3. 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. 4.
    In the next step you will be asked to enter ascend api key
  5. 5.
    Post successful authentication you will be prompted to choose required tables from the list
  6. 6.
    Then select all required fields
  7. 7.
    Submit the integration

Workflow

  1. 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. 2.
    Users would be able to edit/pause/re-activate/delete integration anytime
  3. 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

Purpose: This API gives performance metrics of Creatives(like banners, coupons etc..)
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

Purpose: This API is used to fetch itemised product transactions
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

Purpose: This API is used to fetch metrics of each publisher performance
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

Purpose: This API is used to fetch publisher transaction history details
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

Purpose: This API is used to fetch information regarding 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

Purpose: This API is used to fetch all the payments and fees paid in the given timeframe
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

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.
Replication: Key Based
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
Last modified 3mo ago