Our Taboola connector now supports multithreading. We now use multiple parallel API requests to sync ticket data from your Taboola account to your destination, which makes your syncs faster. The connector’s sync speed depends on your Taboola API quota and account metadata.
The Taboola connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it’s quickly ready for you to use. Taboola’s priority-first syncs fetch the most recent thirty days of data from the reporting tables.
To learn more, see our priority-first sync documentation.
We now support table level re-syncs for Taboola connectors.
You can now select how many months of reporting data you’d like to include in your initial sync. Choose from the following options:
- 3 months
- 6 months
- 12 months (default)
- 24 months
- All time
We have added the new column
sub_categories to the
TARGETING_OS table. Check our Taboola ERD for details.
We have improved the Taboola connector’s capacity to support very large data files.
We have designated
_fivetran_id as the only primary key in all
REPORT tables to account for null values in other fields.
We have added the
_fivetran_id field as a primary key in the
TOP_CAMPAIGN_CONTENT_REPORT table. The
item field is no longer a primary key.
Taboola develops and markets a service for online content publishers and advertisers that recommends digital content to website users.