# Taboola (v1) Information note **Taboola is supported by the Singer community** This integration is powered by [Singer's](https://www.singer.io/) Taboola tap. For support, [visit the GitHub repo](https://github.com/singer-io/tap-taboola) or [join the Singer Slack](https://singer-slackin.herokuapp.com/). ## Taboola integration summary Stitch’s Taboola integration replicates data using the [Taboola Backstage API](https://github.com/taboola/Backstage-API). Refer to the [Schema](https://help.qlik.com/en-US/stitch/integrations/saas/taboola/v1#schema) section for a list of objects available for replication. ## Taboola feature snapshot A high-level look at Stitch's Taboola (v1) integration, including release status, useful links, and the features supported in Stitch. | **STITCH** | | | | | --- | --- | --- | --- | | **[Release status](https://help.qlik.com/en-US/stitch/integrations/identify-an-integration-version)** | Deprecated on February 12, 2026 | **Supported by**

the Info icon

Indicates if the integration is supported by Stitch or the Singer community. | [Singer Community](https://www.singer.io/) | | **Stitch plan**

the Info icon

The type of Stitch plan required to use the integration. | Standard | **[API availability](https://help.qlik.com/en-US/stitch/developers/stitch-connect/guides/source-destination-reference)**

the Info icon

Indicates if the integration is available as a source in Stitch Connect. | the Remove icon

This version of the integration isn't available via the API.


Not available | | **Singer GitHub repository** | [singer-io/tap-taboola](https://github.com/singer-io/tap-taboola) | | | | **REPLICATION SETTINGS** | | | | | **[Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling)**

the Info icon

A type of replication scheduling where an integration's Replication Frequency is anchored to a time you select. | the Success icon

This feature is supported for this version of the integration.


Supported | **[Advanced Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/advanced-scheduling)**

the Info icon

A type of replication scheduling that allows you to specify granular start times for data extraction using cron expressions. | the Success icon

This feature is supported for this version of the integration.


Supported | | **Table-level reset**

the Info icon

Indicates if data can be reset at the table level. If unsupported, data can only be reset at the integration level. | the Remove icon

Table-level resets are not supported for this integration. Resets are only supported at the integration level.


Unsupported | **[Configurable Replication Methods](https://help.qlik.com/en-US/stitch/replication/replication-methods)**

the Info icon

Indicates if Replication Methods can be defined by you for tables in the integration. | the Remove icon

Configurable Replication Methods are not supported for this integration. Stitch will use pre-defined replication methods for tables you set to replicate.


Unsupported | | **DATA SELECTION** | | | | | **Table selection**

the Info icon

The ability to select individual tables for replication in the Stitch interface. If table selection is unavailable, all tables and all the columns they contain will be set to replicate by default. | the Remove icon

Table selection is not supported for this integration. All available table and fields will be automatically selected for replication.


Unsupported | **Column selection**

the Info icon

The ability to select individual columns for replication in the Stitch interface. If column selection is unavailable, all columns will be set to replicate by default. | the Remove icon

Column selection is not supported for this integration. All available columns in tables set to replicate will be selected.


Unsupported | | **Select all**

the Info icon

Indicates if the integration supports selecting all available tables and columns. | the Remove icon

As this integration doesn't support table or column selection, all available tables and columns are automatically replicated.


Unsupported | | | | **TRANSPARENCY** | | | | | **[Extraction Logs](https://help.qlik.com/en-US/stitch/replication/extractions/integration-extraction-logs)**

the Info icon

Logs detailing the Extraction phase of the replication process for a given integration. Includes error info, should an error occur. | the Success icon

This feature is supported for this version of the integration.


Supported | **[Loading Reports](https://help.qlik.com/en-US/stitch/replication/integration-loading-reports)**

the Info icon

Reports detailing the Loading phase of the replication process for a given integration. Includes the number of rows loaded for each table and error info, should an error occur. | the Success icon

This feature is supported for this version of the integration.


Supported | ## Connecting Taboola ### Taboola setup requirements To set up Taboola in Stitch, you need: * **Access to the Taboola API**. * **The following API credentials:** * Taboola Account ID * Client ID * Client Secret Reach out to your Taboola Account Manager for assistance. Once you receive this information, you can continue with the setup. ### Step 1: Add Taboola as a Stitch data source 1. [Sign into your Stitch account](https://app.stitchdata.com/). 2. On the Stitch Dashboard page, click the **Add Integration** button. 3. Click the **Taboola** icon. 4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination. For example, the name “Stitch Taboola” would create a schema called `stitch_taboola` in the destination. **Note**: Schema names cannot be changed after you save the integration. 5. In the **Username** field, enter your Taboola username. This user must have access to the Taboola API. 6. In the **Password** field, enter your Taboola password. 7. In the **Account ID** field, enter your Taboola account ID. 8. In the **Client ID** field, enter your Taboola client ID. 9. In the **Client Secret** field, enter your Taboola client secret. ### Step 2: Define the historical replication start date The Sync Historical Data setting defines the starting date for your Taboola integration. This means that data **equal to or newer than this date** will be replicated to your data warehouse. Change this setting if you want to replicate data beyond Taboola’s default setting of **1 year**. For a detailed look at historical replication jobs, check out the [Syncing Historical SaaS Data](https://help.qlik.com/en-US/stitch/replication/syncing-historical-saas-data-resetting-replication-keys) guide. ### Step 3: Create a replication schedule Information note Replication schedules affect the time Extraction begins, not the time to data loaded. Refer to the [Replication Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling) documentation for more information. In the **Replication Frequency** section, you’ll create the integration’s [replication schedule](https://help.qlik.com/en-US/stitch/replication/replication-scheduling). An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins. Taboola integrations support the following replication scheduling methods: * [Replication Frequency](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/replication-frequency) * [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling) * [Advanced Scheduling using Cron](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/advanced-scheduling) (Advanced or Premium plans only) To keep your row usage low, consider setting the integration to replicate less frequently. See the [Understanding and Reducing Your Row Usage guide](https://help.qlik.com/en-US/stitch/getting-started/understanding-stitch-usage) for tips on reducing your usage. ### Initial and historical replication jobs After you finish setting up Taboola, its **Sync Status** may show as **Pending** on either the Stitch Dashboard or in the Integration Details page. For a new integration, a **Pending** status indicates that Stitch is in the process of scheduling the initial replication job for the integration. **This may take some time to complete.** Information note **Initial replication jobs with Anchor Scheduling** If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling#job-scheduling-and-anchor-times) documentation for more information. #### Free historical data loads The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota. Information note **Replication will continue after the seven days are over**. If you’re no longer interested in this source, be sure to **pause** or **delete** the integration to prevent unwanted usage. ## Taboola table reference Information note **Schemas and versioning** Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing. The schema and info displayed below is for **version 1** of this integration. Information note **Table and column names in your destination** Depending on your destination, table and column names may not appear as they are outlined below. For example: Object names are lowercased in Redshift (`CusTomERs` > `customers`), while case is maintained in PostgreSQL destinations (`CusTomERs` > `CusTomERs`). Refer to the [Loading Guide](https://help.qlik.com/en-US/stitch/replication/loading/destination-guides) for your destination for more info. ### campaign The `campaign` table contains info about the campaigns in your Taboola account. #### Replication During every replication job, all campaigns in your Taboola account will be extracted, or “fully replicated.” If you look in the [Extraction Logs](https://help.qlik.com/en-US/stitch/replication/extractions/integration-extraction-logs) in the Stitch app, you’ll see lines like this: ``` 2017-10-25 13:46:52,254Z tap - INFO Synced 100 campaigns. 2017-10-25 13:46:52,255Z tap - INFO Done syncing campaigns. ``` Roughly the same amount of campaigns should be extracted during every job, unless brand new campaigns are added between jobs. When Stitch loads the extracted records into your destination, however, only new and updated campaigns will be loaded. **This means that only new and updated campaign records will count towards your row count**. #### Deleted campaigns Currently, [the Singer tap](https://github.com/singer-io/tap-taboola) powering this integration has no way to account for campaigns that are hard-deleted in Taboola. This means that if a campaign is deleted at the source, the record for that campaign will remain in the destination. #### NULL dates On occasion, Taboola’s API will push `NULL` for `start_date` and `999-12-31` for `end_date`. [The Singer tap](https://github.com/singer-io/tap-taboola#gotchas) behind this integration will convert `NULL` dates to `999-12-31` for consistency. | **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Full Table | | --- | --- | | **Primary Key ![](https://help.qlik.com/en-US/stitch/images/replication/primary-key-icon.svg)** | id | | **Useful links** | [campaign schema on GitHub](https://github.com/singer-io/tap-taboola/blob/master/tap_taboola/schemas.py#L2 "Opens in new tab: campaign schema on GitHub")


[Taboola API method](https://github.com/taboola/Backstage-API/blob/master/Backstage%20API%20-%20Campaigns.pdf "Opens in new tab: Taboola API method") | campaign table foreign keys | Join campaign with | on | | --- | --- | | [campaign_performance](https://help.qlik.com/en-US/stitch/integrations/saas/taboola/v1#campaign-performance) | ```
campaign.id = campaign_performance.campaign_id
``` | campaign table schema | **advertiser\_id**


STRING | | --- | | **approval\_state**


STRING | | **country\_targeting**


OBJECT

This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.

Click to expand country\_targeting

type

STRING

value

ARRAY

type

STRING

| | **cpc**


NUMBER | | **daily\_cap**


NUMBER | | **end\_date**


DATE | | **id**


INTEGER | | **is\_active**


BOOLEAN | | **name**


STRING | | **platform\_targeting**


OBJECT

This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.

Click to expand platform\_targeting

type

STRING

value

ARRAY

type

STRING

| | **publisher\_targeting**


OBJECT

This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.

Click to expand publisher\_targeting

type

STRING

value

ARRAY

type

STRING

| | **spending\_limit**


NUMBER | | **spending\_limit\_model**


STRING | | **spent**


NUMBER | | **start\_date**


DATE | | **status**


STRING | | **tracking\_code**


STRING | ### campaign\_performance The `campaign_performance` table contains performance data for the campaigns in your Taboola account, broken down by day. | **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental | | --- | --- | | **Primary Keys ![](https://help.qlik.com/en-US/stitch/images/replication/primary-key-icon.svg)** | campaign\_id

date | | **Replication Key ![](https://help.qlik.com/en-US/stitch/images/replication/replication-key-icon.svg)** | date | | **Useful links** | [Taboola documentation](https://github.com/taboola/Backstage-API/blob/master/Backstage%20API%20-%20Reports.pdf "Opens in new tab: Taboola documentation")


[campaign_performance schema on GitHub](https://github.com/singer-io/tap-taboola/blob/master/tap_taboola/schemas.py#L117 "Opens in new tab: campaign_performance schema on GitHub") | campaign\_performance table foreign keys | Join campaign\_performance with | on | | --- | --- | | [campaign](https://help.qlik.com/en-US/stitch/integrations/saas/taboola/v1#campaign) | ```
campaign_performance.campaign_id = campaign.id
``` | campaign\_performance table schema | **campaign\_id**


INTEGER | | --- | | **clicks**


INTEGER | | **cpa**


NUMBER | | **cpa\_actions\_num**


INTEGER | | **cpa\_conversion\_rate**


NUMBER | | **cpc**


NUMBER | | **cpm**


NUMBER | | **ctr**


NUMBER | | **currency**


STRING | | **date**


DATE | | **impressions**


INTEGER | | **spent**


NUMBER |