This Data Connector allows you to import Apptopia Data Source objects into Treasure Data.
Basic knowledge of Treasure Data
Basic knowledge of Apptopia
Use TD Console
Create a new connection
In Treasure Data, you must create and configure the data connection prior to running your query. As part of the data connection, you provide authentication to access the integration.
Open TD Console.
Navigate to Integrations Hub > Catalog.
- Click the search icon on the far-right of the Catalog screen, and enter Apptopia.
- Hover over the Apptopia connector and select Create Authentication.
The following dialog opens.
Edit your Apptopia Client ID and Secret Key information. Then click Continue. Give your connection a name, and click Done.
Create a new transfer
When you select Create Connection, you are taken to the Authentications tab. Look for the connection you created and select New Transfer.
The following dialog opens. Edit the details and select Next.
Preview your data. If you wish to change anything, select Advanced Settings or select Next.
In Advanced Settings you can change some options such as rate limits:
Select the database and table where you want to transfer the data, as shown in the following dialog:
Specify the schedule of the data transfer and select Start Transfer:
You will see the new data transfer in progress, listed under the My Input Transfers tab, and a corresponding job will be listed in the Jobs section.
Install ‘td’ command v0.11.9 or later
You can install the newest TD Toolbelt.
Create Configuration File
Prepare configuration file (for eg: load.yml) with your Apptopia account access information, as follows:
This example shows an Apptopia Publisher Performance Data Source:
client: Apptopia client id.
secret: Apptopia secret.
target: Apptopia entity object to be imported.
See Appendix for the list of available target.
store: Mobile market to fetch data
See Appendix for the list of available store.
start_date: From which date (yyyy-MM-dd) product data to be imported. This field is required when fetching product usage (target is product_usage) or product sale (target is product_sales) with in-app-purchase breakdown (breakdown has iap).
end_date: To which date (yyyy-MM-dd) product data to be imported. This field is optional and is automatically adjusted to maximum 60 days since start_date limited by current date.
requests_per_minute_limit: Limit number of API calls per minute
See Appendix for how to use these options
For more details on available out modes, see the Appendix
Preview Data to Import (optional)
You can preview data to be imported using the command
Execute Load Job
Submit the load job. It may take a couple of hours depending on the data size. Users need to specify the database and table where their data are stored.
It is recommended to specify --time-column option, because Treasure Data’s storage is partitioned by time (see also data partitioning) If the option is not given, the Data Connector will choose the first long or timestamp column as the partitioning time. The type of the column specified by --time-column must be either of long and timestamp type.
If your data doesn’t have a time column you can add it by using add_time filter option. For more details, see add_time Filter Plugin for Integrations.
The preceding command assumes that you already created database(td_sample_db) and table(td_sample_table). If the database or the table does not exist in TD, the command will not succeed, so create the database and table Database and Table Management or use --auto-create-table option with td connector:issue command to auto create the database and table:
You can assign Time Format column to the "Partitioning Key" by "--time-column" option.
You can schedule periodic Data Connector execution for periodic Apptopia import. We configure our scheduler carefully to ensure high availability. By using this feature, you no longer need a cron daemon on your local data center.
Create the Schedule
A new schedule can be created using the td connector:create command. The name of the schedule, cron-style schedule, the database and table where their data will be stored, and the Data Connector configuration file are required.
The `cron` parameter also accepts the options: `@hourly`, `@daily` and `@monthly`.
By default, schedule is setup in UTC timezone. You can set the schedule in a timezone using -t or --timezone option. The `--timezone` option supports only extended timezone formats like 'Asia/Tokyo', 'America/Los_Angeles' etc. Timezone abbreviations like PST, CST are *not* supported and may lead to unexpected schedules.
List the Schedules
You can see the list of scheduled entries by td connector:list.
Show the Setting and History of Schedules
td connector:show shows the execution setting of a schedule entry.
td connector:history shows the execution history of a schedule entry. To investigate the results of each individual execution, use td job <jobid>.
Delete the Schedule
td connector:delete removes the schedule.
Modes for Out Plugin
You can specify file import mode in out section of load.yml.
This is the default mode and records are appended to the target table.
replace (In td 0.11.10 and later)
This mode replaces data in the target table. Any manual schema changes made to the target table remains intact with this mode.
Application SDKs metadata
List of categories
Raw ranks top charts for each category
Featured applications for each category
New app releases for each category
Google Play Market
There is requests per minute rate limit in Apptopia. This rate limit is auto refreshed after a certain number of seconds.
If you have multiple transfers under the same Apptopia account, you can control the rate limit usage of each transfer via requests_per_minute_limit in advanced settings as long as the total limit does not exceed your account limit. For example, assume that your account has quotas as 1000 calls/minute, if you create 2 transfers, e.g. app_performance & publisher_performance targets, you could use 600 rpm for app_performance transfer and the rest (400 rpm) for publisher_performance transfer.