Twitter Ads Advanced Settings
- 13 Jul 2021
- 1 Minute to read
- Print
- DarkLight
- PDF
Twitter Ads Advanced Settings
- Updated on 13 Jul 2021
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Warning:
We do not recommend changing advanced settings unless you are an experienced Panoply user.
For users who have some experience working with their data in Panoply, there are a number of items that can be customized for this data source.
- Destination Schema: This is the name of the target schema to save the data. The default schema for data warehouses built on Google BigQuery is panoply. The default schema for data warehouses built on Amazon Redshift is public. This cannot be changed once a source has been collected.
- Destination: This is the prefix that Panoply will use in the name of the tables included in the collection. The default destination for Twitter Ads is
twitter_ads_{_collection}
, where__collection
is the name of the table from Twitter Ads. - Primary Key: The primary key is an id field that defines the column that contains the table's Primary Key. The default for Twitter Ads is id.
- Exclude: The Exclude option allows you to exclude certain data, such as names, addresses, or other personally identifiable information. Enter the column names of the data to exclude.
- Parse String: If the data to be collected contains JSON, include the JSON text attributes to be parsed.
- Truncate: Truncate deletes all the current data stored in the destination tables, but not the tables themselves. Afterwards Panoply will recollect all the available data for this data source.
- Click Save Changes then click Collect.
- The data source appears grayed out while the collection runs.
- You may add additional data sources while this collection runs.
- You can monitor this collection from the Jobs page or the Data Sources page.
- After a successful collection, navigate to the Tables page to review the data results.
Was this article helpful?