Integration of Tradedoubler with BigQuery

Learn how to connect Tradedoubler to Google BigQuery using WitCloud. Automatically fetch daily statistics and transactions with their commission data for one of your Tradedoubler programs, and analyze your affiliate marketing results.

Updated

Introduction

This integration connects Tradedoubler to Google Cloud BigQuery. For the Tradedoubler program you choose, it collects daily statistics (impressions, clicks, leads, sales and commissions) and individual transactions with their commission data, in the currency you select. You can analyze the results of your affiliate marketing next to the rest of your data in WitCloud.

Configuration guide

Follow the steps below to connect Tradedoubler with BigQuery. Once the setup is complete, your Tradedoubler data will be transferred to your BigQuery project.

You connect with your Tradedoubler API client (a Client ID and a Client secret) and the username and password of your Tradedoubler account. Create the API client in Tradedoubler's own tool, at solutions.tradedoubler.com/tools/api-client. That tool is Tradedoubler's interface, not WitCloud's, and may change.

Module setup

Go to Integrations in the menu and click Add integration.

Integrations list with the Add integration button

Select Tradedoubler from the list of available integrations.

Integration catalog with Tradedoubler selected

Enter the Collect name, e.g., "Tradedoubler PL".

Collect name field filled in with the example name Tradedoubler PL

Authorization

If you have previously authorized the Tradedoubler module and do not require additional permissions, you can skip this step and pick the existing authorization from the Select Tradedoubler authorization drop-down.

Click Authorize.

Authorize button next to the authorization token field

Fill in the Authorize form with the Client ID and Client Secret of your API client, and the Username and Password of your Tradedoubler account, then click Create. WitCloud checks the credentials with Tradedoubler; if they are rejected, the form shows an error and nothing is saved.

Authorize pop-up with the Client ID, Client Secret, Username and Password fields filled with placeholder values

Select the Tradedoubler program from the Select program drop-down list. It lists the active programs available to your account.

Program drop-down open with two example Tradedoubler programs

Choose the Currency in which you want your data to be retrieved.

Currency drop-down open with currency codes

Optionally, click Show advanced settings. Tables to collect lets you filter the tables you want to collect; by default all of them are selected, and at least one table is required.

Advanced settings open with the Tables to collect field

Click Next.

Historical data and scheduling

In Historical Data, enter the number of days for which you want to fetch historical data. You can enter up to 365 days.

Historical Data field filled in with 365 days

A data synchronization schedule will be created automatically. More information on this topic can be found here.

Click Create to complete the configuration.

Data collection settings with the Create button

Done! Your Tradedoubler data will now be synchronized with BigQuery.

Data schema

Expand the tables below to view the full data schema collected from Tradedoubler.

Data schema for td_advertiser_statistics
Field NameModeType
dateNULLABLETIMESTAMP
impressionsNULLABLEINTEGER
impressionsCommissionNULLABLERECORD
impressionsCommission.publisherCommissionNULLABLEFLOAT
impressionsCommission.tdCommissionNULLABLEFLOAT
clicksNULLABLEINTEGER
clicksCommissionNULLABLERECORD
clicksCommission.publisherCommissionNULLABLEFLOAT
clicksCommission.tdCommissionNULLABLEFLOAT
uniqueVisitorsNULLABLEINTEGER
uvCommissionNULLABLERECORD
uvCommission.publisherCommissionNULLABLEFLOAT
uvCommission.tdCommissionNULLABLEFLOAT
leadsNULLABLEINTEGER
leadsCommissionNULLABLERECORD
leadsCommission.publisherCommissionNULLABLEFLOAT
leadsCommission.tdCommissionNULLABLEFLOAT
ileadsNULLABLEINTEGER
ileadsCommissionNULLABLERECORD
ileadsCommission.publisherCommissionNULLABLEFLOAT
ileadsCommission.tdCommissionNULLABLEFLOAT
salesNULLABLEINTEGER
salesCommissionNULLABLERECORD
salesCommission.publisherCommissionNULLABLEFLOAT
salesCommission.tdCommissionNULLABLEFLOAT
isalesNULLABLEINTEGER
isalesCommissionNULLABLERECORD
isalesCommission.publisherCommissionNULLABLEFLOAT
isalesCommission.tdCommissionNULLABLEFLOAT
commissionNULLABLERECORD
commission.publisherCommissionNULLABLEFLOAT
commission.tdCommissionNULLABLEFLOAT
orderValueNULLABLEFLOAT
ctrNULLABLEFLOAT
crNULLABLEFLOAT
lrNULLABLEFLOAT
epcNULLABLEFLOAT
adIdNULLABLESTRING
adNameNULLABLESTRING
adCategoryIdNULLABLESTRING
adCategoryNameNULLABLESTRING
currencyNULLABLESTRING
Data schema for td_advertiser_transactions
Field NameModeType
transactionIdNULLABLESTRING
programIdNULLABLESTRING
programNameNULLABLESTRING
sourceNameNULLABLESTRING
sourceIdNULLABLESTRING
adIdNULLABLESTRING
eventIdNULLABLESTRING
eventNameNULLABLESTRING
eventTypeIdNULLABLESTRING
statusNULLABLESTRING
timeofLastClickNULLABLETIMESTAMP
timeofCreateNULLABLETIMESTAMP
timeofTransactionNULLABLETIMESTAMP
timeofLastModifiedNULLABLETIMESTAMP
leadNumberNULLABLESTRING
orderNumberNULLABLESTRING
orderValueNULLABLEFLOAT
commissionNULLABLEFLOAT
tdCommissionNULLABLEFLOAT
paidNULLABLEBOOLEAN
productInfoREPEATEDRECORD
productInfo.productIDNULLABLESTRING
productInfo.productNameNULLABLESTRING
productInfo.quantityNULLABLEINTEGER
productInfo.productValueNULLABLEFLOAT
productInfo.productGroupNULLABLEINTEGER
voucherCodeNULLABLESTRING
productsApiNULLABLERECORD
productsApi.productIdNULLABLESTRING
productsApi.productNameNULLABLESTRING
crossDeviceNULLABLESTRING
pendingRuleNULLABLESTRING
deviceObjectNULLABLERECORD
deviceObject.deviceTypeNULLABLESTRING
deviceObject.operatingSystemNULLABLESTRING
deviceObject.browserNULLABLESTRING
modifiedNULLABLEBOOLEAN
currencyNULLABLESTRING