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.

Step 3: Execute Load Job

Finally, 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.

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 manually 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.

Scheduled execution

You can schedule periodic Data Connector execution for periodic Apptopia import.
We take great care in distributing and operating our scheduler in order to achieve high availability.
By using this feature, you no longer need a cron daemon on your local datacenter.

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`.

Untitled-3

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 currently scheduled entries by td connector:list.

Delete the Schedule

Appendix

A) Modes for out plugin

append (default)

This is the default mode and records are appended to the target table.

in:
...out:
mode: append

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.

in:
...out:
mode: replace

B) Available targets

Target

Description

app_metadata

Application metadata

app_performance

Application performance

app_ranks

Application ranking

app_sdks_metadata

Application SDKs metadata

category

List of categories

category_rank_lists

Raw ranks top charts for each category

category_featured_lists

Featured applications for each category

category_new_releases

New app releases for each category

country

Supported countries

publisher_metadata

Publisher metadata

publisher_performance

Publisher performance

sdk_metadata

SDK metadata

C) Available markets

Store

Description

itunes_connect

Appple Store

google_play

Google Play Market

D) Rate Limits

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.

Last modified: Jan 17 2018 17:45:01 UTC

If this article is incorrect or outdated, or omits critical information, let us know. For all other issues, access our support channels.