This integration is powered by Singer's Outbrain tap. For support, visit the GitHub repo or join the Singer Slack.
Outbrain integration summary
Stitch’s Outbrain integration replicates data using the Outbrain Amplify API. Refer to the Schema section for a list of objects available for replication.
Outbrain feature snapshot
A high-level look at Stitch's Outbrain (v1) integration, including release status, useful links, and the features supported in Stitch.
| STITCH | |||
| Release status |
Released on March 1, 2017 |
Supported by | |
| Stitch plan |
Standard |
API availability |
Available |
| Singer GitHub repository | |||
| 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 Outbrain
Step 1: Add Outbrain as a Stitch data source
- Sign into your Stitch account.
-
On the Stitch Dashboard page, click the Add Integration button.
-
Click the Outbrain icon.
-
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_outbrainin the destination. Note: Schema names cannot be changed after you save the integration. -
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:
0f4b02153ee75f3c9dc4fc128ab041962and is located betweenmarketersandcampaigns, if you’re looking at the Overview dashboard:https://my.outbrain.com/amplify/site/marketers/[account-id-will-be-here]/campaigns/overview - In the Username field, enter your Outbrain username.
- 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 guide.
Step 3: Create a replication schedule
In the Replication Frequency section, you’ll create the integration’s replication schedule. 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:
-
Advanced Scheduling using Cron (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 for tips on reducing your usage.
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.
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 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.
Outbrain 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 for version 1 of this integration.
This is the latest version of the Outbrain 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 the Loading Guide for your destination for more info.
campaign_performance
The campaign_performance table contains performance metrics for your Outbrain campaigns.
|
Key-based Incremental |
|
|
Primary Keys |
campaignId fromDate |
|
Replication Key |
fromDate |
| Useful links |
|
campaignId
STRING |
|
clicks NUMBER |
|
conversionRate NUMBER |
|
conversions NUMBER |
|
cpa NUMBER |
|
ctr NUMBER |
|
ecpc NUMBER |
|
fromDate
DATE |
|
impressions NUMBER |
|
spend NUMBER |
campaigns
The campaigns table contains info about your Outbrain campaigns.
|
Full Table |
|
|
Primary Key |
id |
| Useful links |
|
budget OBJECT
|
||||||||||||||||
|
campaignOnAir BOOLEAN |
||||||||||||||||
|
cpc NUMBER |
||||||||||||||||
|
enabled BOOLEAN |
||||||||||||||||
|
id
STRING |
||||||||||||||||
|
name STRING |
||||||||||||||||
|
onAirReason STRING |
| Related | Troubleshooting |
Questions? Feedback?
Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.