Yes. The views that were generated from a report UI will always include “campaigns_mapped_table*” in the title.
For example, if the report name is Test_01 the Postgres table will be called “public.campaigns_mapped_table_test_01”
These tables are being pulled directly from the platforms’ API and are independent from reports within UI.
Such Postgres tables will always include the name of the dimension and provider in the the title, like so: “public.ads_raw_table_facebook”
We can create a Google spreadsheet which will contain all rows from all of your tables within Postgres Db. It will update every time you will open the gsheet.
The “SQL Access Tables” tab shows you all tables that exist within your Postgres database. Learn more.
Yes, column names always stay unchanged in Postgres.
The Binding name is being automatically pulled from APi based on the campaign name.
This is hardcoded and we will double check with our dev team on this point. Maybe, one day in future…
It’s an internal improvado name for providers.
Yes, in fact there can be only one data_source_key with the same name.
Product name is being generated automatically from the and represents a data source (i.e. Facebook)
Changes made within “Define metrics” are not be reflected in Postgres views at all.
By default, data is being updated daily:
You can check last update time at the Edit Datasets menu in your report.
The loading starts at the same time, but every provider has different time for returning request back with data. General time for full update +-4hours
No. But we do not download rows with NULL values anyway.