Stripe Advanced Settings
- 19 Sep 2022
- 1 Minute to read
- Print
- DarkLight
- PDF
Stripe Advanced Settings
- Updated on 19 Sep 2022
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
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.
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 Prefix: This is the prefix that Panoply will use in the name of the tables included in the collection.
- The default prefix for Stripe is
stripe
. - The naming convention is
stripe_{__resource}
, where{__resource}
is a dynamic field for the name of the resource collected. For example, for the resource namedcustomers
, the default destination table will bestripe_customers
. - To change the default, enter your desired prefix in the Destination Prefix field with the same syntax. For example, if you enter
myfile_{__resource}
, the resulting table in Panoply for the customers resource will be namedmyfile_customers
.
- The default prefix for Stripe is
- Collect Events Incrementally: When selecting the Events resource, users can enable the
Collect Events incrementally
option in the advanced options. Once enabled, the incremental load options will become available for configuration. - 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?