Adthena

Any instance where an entry in the below configuration has a leading $ represents a parameter that needs to be replaced with a static value.

Parameters in this document:

• $api_key - The API Key will provide access to the Adthena API. To get an API Key, you will need to request one by emailing support@adthena.com.
  • Note: You will need a different API Key for each Adthena account/location, so be sure to receive and document each key if you have multiple accounts/locations.
• $account_id - The Account ID is a unique identifier for your Adthena account. If you do not know your Account ID value, you can request this by emailing support@adthena.com.
• $resource_name - The Resource Name represents the name of the resource to be appended and used as part of the Destination Table name. The value that should be used here can be found in the API Resources table below.
• $endpoint - The Endpoint represents the data that you would like to ingest into Panoply from the Adthena API. The value that should be used here can be found in the API Resources table below.
• $primary_key - Primary keys are used to ensure the uniqueness of the rows in a table. The Primary Key is comprised of one or more columns that can be used to identify the row in the data warehouse. The process guarantees that no two rows have the same value in their primary key. The value that should be used here can be found in the API Resources table below.
• $period_start - The Start Date of the data that you would like to receive, given in yyyy-mm-DD format. If this date is 30 days in the past, data by week (Sunday-Saturday) will be returned instead of data by day. If this date is more than 13 months in the past, data by month will be returned.
• $period_end - The End Date of the data that you would like to receive, given in yyyy-mm-DD format.
• $attribution_window - The Attribution Window represents the number of days in which an ad publisher can claim credit for a click or impression that leads to a conversion. This can impact some of the metric values in terms of which ad they apply to, and which day they are considered occurring on. This parameter should always be set as a negative number, and at least have a value of -1.
• $incremental_starting_value - The Incremental Starting Value represents the earliest date that data should be collected for, given in yyyy-mm-DD format. For example, if you would like your historical data to go back to the start of 2021, this value would be set to 2021-01-01.

In addition to the above values (periodstart and periodend), additional URL Parameters can be provided as part of the URL Parameters entry to further specify the API call and impact the response that is ultimately ingested into Panoply. For a full list of these additional URL Parameters, see the Query Parameters section under the Resource that you are ingesting, with each Resource page being linked above in the API Resources section.

Destination Table naming convention is ultimately up to you as the data owner. One common structure used for this API is adthena_$resource_name.

When initially collecting historical data, set the periodstart and periodend variables to capture back to the start of data you'd like to ingest. For example, if you would like to collect back to the start of 2021 through the current date, the parameters would be the following:

Upon completion of the backfill of data, you can set the periodstart and periodend parameters to the following values in order to capture incremental data moving forward:

When entering a column value to the incremental key feature, you will need to use the following format: yyyy-dd-MM. For example, if you'd like to start ingesting data from January 1, 2021 forward, set the column value to 2021-01-01 for the initial collection. Upon success, Panoply will automatically update this value to collect only new data, so you will not need to adjust this value moving forward.