Taboola

Taboola helps you create targeted advertising campaigns to market your products and services to the most receptive and relevant audiences and drives up clicks, traffic and conversions.

You can replicate the data associated with your Taboola account and the campaigns to a Destination of your choice using Hevo Pipelines.

For creating Pipelines using this Source, Hevo provides you a fully managed BigQuery data warehouse as a possible Destination. This option remains available till the time you set up your first BigQuery Destination irrespective of any other Destinations that you may have. With the managed warehouse, you are only charged the cost that Hevo incurs for your project in Google BigQuery. The invoice is generated at the end of each month and payment is recovered as per the payment instrument you have set up. You can now create your Pipeline and directly start analyzing your Source data. Read Hevo Managed Google BigQuery.


Prerequisites

  • An active Taboola account.
  • The Client ID and Client Secret for the account. The Client Secret is shared by the Taboola team via email during account onboarding.

Configuring Taboola as a Source

Perform the following steps to configure Taboola as the Source in your Pipeline:

  1. Click PIPELINES in the Asset Palette.

  2. Click + CREATE in the Pipelines List View.

  3. In the Select Source Type page, select Taboola.

  4. In the Configure your Taboola Source page, specify the following:

    Taboola Source settings

    • Pipeline Name: A unique name for the Pipeline, not exceeding 255 characters.

    • Client ID: The Client ID of your Taboola advertiser account

    • Client Secret: The Client Secret of your Taboola advertiser account

      NOTE: The Client ID and Client Secret are shared by your Taboola Account Manager in the onboarding email communication. You can request these again from the Taboola team if required.

    • Advertiser Accounts: This field is displayed once you enter the correct Client ID and Secret. Select the advertiser accounts whose data you want to ingest.

    • Historical Sync Duration: The duration for which historical data must be synced to the Destination. Default value: 1 Year.

  5. Click TEST & CONTINUE.

  6. Proceed to configuring the data ingestion and setting up the Destination.


Data Replication

Default Pipeline Frequency Minimum Pipeline Frequency Maximum Pipeline Frequency Custom Frequency Range (Hrs)
3 Hrs 1 Hr 24 Hrs 1-24

Note: The custom frequency must be set in hours, as an integer value. For example, 1, 2, 3 but not 1.5 or 1.75.

  • Historical Data: Hevo ingests the historical data on the basis of the offset selected at the time of creating the Pipeline. By default, it starts fetching data from the time your Taboola account was created.

  • Incremental Data: Once the historical load is completed, each run of the Pipeline fetches the next available new and modified data.

  • Data Refresh: Data for the last 30 days is refreshed on a rolling basis for all report objects.


Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination database.

To determine the primary keys for replicating the data:

  • If the primary key list count in the Source object is > 3, the __hevo_id is used as the single primary key

  • For fewer than three primary keys in the Source object, the individual fields are retained as primary keys.


Data Model

Report Name Primary Key Description
Account - id Contains details of the prime advertiser under which you perform campaigning operations. The advertiser account is provided to you by Taboola when your account credentials are first created. If you manage multiple accounts, this is also called your Network Account. This object is empty if no advertiser accounts exist.
Campaign - account_id
- id
Contains the list of all campaigns for all the accounts that the data Pipeline is created for. Data for deleted campaigns is also included in this object with status as TERMINATED. Targeting information associated with each campaign can be seen in the _targeting columns.
Campaign Breakdown Report - account_id
- campaign
- __hevo_report_date
Contains reporting data grouped by campaign.
Campaign Day Breakdown Report - account_id
- campaign
- __hevo_report_date
Contains reporting data grouped by campaign and day.
Campaign Item - account_id
- id
Contains items such as images, approval states, statuses, and link URLs for each campaign’s creative strategy.
Campaign Site Daily Report - account_id
- campaign
- campaign_name
- date
- site
- site_name
Contains reporting data grouped by date, campaign level, and site.
Content Provider Report - account_id
-content_provider
- content_provider_name
- __hevo_report_date
Contains reporting data grouped by content provider.
Country Breakdown Report - account_id
- country
- country_name,
- __hevo_report_date
Contains reporting data grouped by content provider and country.
Note: This object is available only for the Network Account and not for any linked accounts of other advertisers.
DMA Country Report - account_id
- country
- dma
- __hevo_report_date
Contains reporting data grouped by DMA and country.
Hour of Day Report - account_id
- __hevo_report_date
- hour_of_day
Contains reporting data grouped by date and campaign.
Platform Report - account_id
- __hevo_report_date
- platform
- platform_name
Contains reporting data grouped by platform name.
Region Country Report - account_id
- country
- __hevo_report_date
- region
Contains reporting data grouped by region and country.
Site Breakdown Report - account_id
- __hevo_report_date
- site_id
Contains reporting data grouped by site.
Top Campaign Content Report - account_id
- __hevo_report_date
- item
Enables you to view the performance of the top 500 campaigns items by URL and Creative for one or all campaigns.
User Segment Report - account_id
- audience_name
- data_partner_audience_id
- __hevo_report_date
- partner_name
Contains reporting data grouped by marketplace audience.

Source Considerations

  • The Content Provider Report is available only for the network account whose credentials are used at the time of configuring the Source.

Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Oct-25-2021 NA Added the Pipeline frequency information in the Data Replication section.
Jul-22-2021 NA - Updated the Data Model with additional reports.
- Added a note in the Overview section about Hevo providing a fully-managed Google BigQuery Destination for Pipelines created with this Source.
Jul-12-2021 1.67 New document.
Last updated on 22 Oct 2021