# Outbrain (v2)
Information note **Outbrain is supported by the Singer community**
This integration is powered by [Singer's](https://www.singer.io/) Outbrain tap. For support, [visit the GitHub repo](https://github.com/singer-io/tap-outbrain) or [join the Singer Slack](https://singer-slackin.herokuapp.com/).
## Outbrain integration summary
Stitch’s Outbrain integration replicates data using the [Outbrain Amplify API v2](http://developer.outbrain.com/docs/amplify-v2/api-reference/). Refer to the [Schema](https://help.qlik.com/en-US/stitch/integrations/saas/outbrain#schema) section for a list of objects available for replication.
## Outbrain feature snapshot
A high-level look at Stitch's Outbrain (v2) 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)** | Released on February 11, 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 Success icon
This version of the integration is available via the API.
Available |
| **Singer GitHub repository** | [singer-io/tap-outbrain](https://github.com/singer-io/tap-outbrain) | | |
| **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 Success icon
This feature is supported for this version of the integration.
Supported | **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 Success icon
Supported
Supported | | |
| **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 Outbrain
### Step 1: Add Outbrain 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 **Outbrain** 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 Outbrain” would create a schema called `stitch_outbrain` in the destination. **Note**: Schema names cannot be changed after you save the integration.
5. In the **Account ID** field, enter your Outbrain Account (or Marketer) ID.
You can find this by looking at the URL when you’re logged into your Outbrain account. The Account ID looks something like this: `0f4b02153ee75f3c9dc4fc128ab041962` and is located between `marketers` and `campaigns`, if you’re looking at the Overview dashboard:
`https://my.outbrain.com/amplify/site/marketers/[account-id-will-be-here]/campaigns/overview`
6. In the **Username** field, enter your Outbrain username.
7. In the **Password** field, enter your Outbrain password.
### Step 2: Define the historical replication start date
The Sync Historical Data setting defines the starting date for your Outbrain 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 Outbrain’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.
Outbrain 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.
### Step 4: Set objects to replicate
Information note **Is an object missing or not replicating?** Verify that the object meets the requirements for [selection](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#selection-requirements) and [replication](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#replication-requirements).
The last step is to select the tables you want to replicate. [Learn about the available tables for this integration.](https://help.qlik.com/en-US/stitch/integrations/saas/outbrain#schema)
**Note**: If a replication job is currently in progress, new selections won’t be used until the next job starts.
* Selection options
* Individual tables
* All tables
For Outbrain integrations, you can select:
1. **Individual tables**
2. **All tables**
Click the tabs to view instructions for each selection method.
1. In the integration’s **Tables to Replicate tab**, locate a table you want to replicate.
2. To track a table, click the **checkbox** next to the table’s name. A blue checkmark means the table is set to replicate.
3. Repeat this process for all the tables you want to replicate.
4. When finished, click the **Finalize Your Selections** button at the bottom of the screen to save your selections.
Information note **Important**: Using the **Select All** feature will overwrite any previous selections. However, selections aren’t final until **Finalize Your Selections** is clicked. Clicking **Cancel** will restore your previous selections. Refer to the [Select All guide](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#set-all-data-to-replicate) for more info about this feature.
1. Click into the integration from the Stitch Dashboard page.
2. Click the **Tables to Replicate** tab.
3. In the list of tables, click the box next to the **Table Names** column.
4. In the menu that displays, click **Track all Tables and Fields**:
The Track all Tables and Fields menu in the Tables to Replicate tabThe Track all Tables and Fields menu in the Tables to Replicate tab
5. Click the **Finalize Your Selections** button at the bottom of the page to save your data selections.
### Initial and historical replication jobs
After you finish setting up Outbrain, 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.
## Outbrain 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 2** of this integration.
This is the latest version of the Outbrain 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 your Outbrain campaigns.
| **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 ** | id |
| **Useful links** | [Outbrain documentation](http://developer.outbrain.com/docs/amplify-v2/api-reference/#campaigns "Opens in new tab: Outbrain documentation")
[campaign schema on GitHub](https://github.com/singer-io/tap-outbrain/blob/master/tap_outbrain/schemas/campaign.json "Opens in new tab: campaign schema on GitHub")
[Outbrain API method](http://developer.outbrain.com/docs/amplify-v2/api-reference/#campaigns "Opens in new tab: Outbrain API method") |
campaign table schema
| **id**
STRING |
| --- |
| **name**
STRING |
| **campaignOnAir**
BOOLEAN |
| **onAirReason**
STRING |
| **enabled**
BOOLEAN |
| **budget**
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 budget
| id STRING |
| name STRING |
| shared BOOLEAN |
| amount NUMBER |
| currency STRING |
| amountRemaining NUMBER |
| amountSpent NUMBER |
| creationTime STRING |
| lastModified STRING |
| startDate STRING |
| endDate STRING |
| runForever BOOLEAN |
| type STRING |
| pacing STRING |
| dailyTarget NUMBER |
| maximumAmount NUMBER |
|
| **cpc**
NUMBER |
### campaign\_performance
The `campaign_performance` table contains performance metrics for your Outbrain campaigns.
| **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 ** | campaignId
fromDate |
| **Replication Key ** | fromDate |
| | The `fromDate` replication key uses timestamp (date-time) format in V2, allowing granular replication tracking. |
| **Useful links** | [Outbrain documentation](http://developer.outbrain.com/docs/amplify-v2/api-reference/#campaign-performance "Opens in new tab: Outbrain documentation")
[campaign_performance schema on GitHub](https://github.com/singer-io/tap-outbrain/blob/master/tap_outbrain/schemas/campaign_performance.json "Opens in new tab: campaign_performance schema on GitHub")
[Outbrain API method](http://developer.outbrain.com/docs/amplify-v2/api-reference/#campaign-performance "Opens in new tab: Outbrain API method") |
campaign\_performance table schema
| **campaignId**
STRING |
| --- |
| **fromDate**
STRING |
| **impressions**
NUMBER |
| **clicks**
NUMBER |
| **ctr**
NUMBER |
| **spend**
NUMBER |
| **ecpc**
NUMBER |
| **conversions**
NUMBER |
| **conversionRate**
NUMBER |
| **cpa**
NUMBER |