Movatterモバイル変換


[0]ホーム

URL:


DOCS >INTEGRATIONS >SAAS >TABOOLA (V1)

Get started with a free trial today

Already have an account? Sign in

Taboola (v1)

Taboola is supported by the Singer community
This integration is powered bySinger's Taboola tap. For support,visit the GitHub repo orjoin the Singer Slack.

Taboola integration summary

Stitch’s Taboola integration replicates data using theTaboola Backstage API. Refer to theSchema 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

Released on April 25, 2017

Supported by

Singer Community

Stitch plan

Standard

API availability

Available

Singer GitHub repository

singer-io/tap-taboola

REPLICATION SETTINGS
Anchor Scheduling

Supported

Advanced Scheduling

Supported

Table-level reset

Unsupported

Configurable Replication Methods

Unsupported

DATA SELECTION
Table selection

Unsupported

Column selection

Unsupported

Select all

Unsupported

TRANSPARENCY
Extraction Logs

Supported

Loading Reports

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.
  2. On the Stitch Dashboard page, click theAdd Integration button.

  3. Click theTaboola 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 calledstitch_taboola in the destination.Note: Schema names cannot be changed after you save the integration.

  5. In theUsername field, enter your Taboola username. This user must have access to the Taboola API.
  6. In thePassword field, enter your Taboola password.
  7. In theAccount ID field, enter your Taboola account ID.
  8. In theClient ID field, enter your Taboola client ID.
  9. In theClient 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 dataequal 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 of1 year. For a detailed look at historical replication jobs, check out theSyncing Historical SaaS Data guide.

Step 3: Create a replication schedule

Replication schedules affect the time Extraction begins, not the time to data loaded. Refer to theReplication Scheduling documentation for more information.

In theReplication Frequency section, you’ll create the integration’sreplication schedule. 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:

To keep your row usage low, consider setting the integration to replicate less frequently. See theUnderstanding and Reducing Your Row Usage guide for tips on reducing your usage.

Initial and historical replication jobs

After you finish setting up Taboola, itsSync Status may show asPending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, aPending status indicates that Stitch is in the process of scheduling the initial replication job for the integration.This may take some time to complete.

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 theAnchor Scheduling 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.

Replication will continue after the seven days are over. If you’re no longer interested in this source, be sure topause ordelete the integration to prevent unwanted usage.

Taboola table reference

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 forversion 1 of this integration.

This is the latest version of the Taboola integration.

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 theLoading Guide for your destination for more info.

campaign

Thecampaign 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 theExtraction 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 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 pushNULL forstart_date and999-12-31 forend_date.The Singer tap behind this integration will convertNULL dates to999-12-31 for consistency.

Replication Method

Full Table

Primary Key

id

Useful links

campaign schema on GitHub

Taboola API method

Join campaign withon
campaign_performance
campaign.id = campaign_performance.campaign_id

advertiser_id

STRING

approval_state

STRING

country_targeting

OBJECT

cpc

NUMBER

daily_cap

NUMBER

end_date

DATE

id

INTEGER

is_active

BOOLEAN

name

STRING

platform_targeting

OBJECT

publisher_targeting

OBJECT

spending_limit

NUMBER

spending_limit_model

STRING

spent

NUMBER

start_date

DATE

status

STRING

tracking_code

STRING

campaign_performance

Thecampaign_performance table contains performance data for the campaigns in your Taboola account, broken down by day.

Replication Method

Key-based Incremental

Primary Keys

campaign_id

date

Replication Key

date

Useful links

Taboola documentation

campaign_performance schema on GitHub

Join campaign_performance withon
campaign
campaign_performance.campaign_id = campaign.id

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

RelatedTroubleshooting

Questions? Feedback?

Did this article help? If you have questions or feedback, feel free tosubmit a pull request with your suggestions,open an issue on GitHub, orreach out to us.


[8]ページ先頭

©2009-2026 Movatter.jp