Release Status Released Supported By Singer community
Availability Free Status Page Outbrain Status Page
Default Historical Sync 1 year Default Replication Frequency 30 minutes
Whitelisting Unsupported Destination Incompatibilities None

Connecting Outbrain

Step 1: Add Outbrain as a Stitch Data Source

  1. On the Stitch Dashboard page, click the Add Integration button.

  2. Click the Outbrain icon.

  3. Enter a name for the integration. This is the name that will display on the 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.

  4. 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

  5. In the Username field, enter your Outbrain username.
  6. In the Password field, enter your Outbrain password.

Step 2: Define the Historical Sync

The Sync Historical Data setting will define 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 sync data beyond Outbrain’s default setting of 1 year. For a detailed look at historical syncs, check out the Syncing Historical SaaS Data guide.

Step 3: Define Replication Frequency

The Replication Frequency controls how often Stitch will attempt to extract data from your Outbrain integration.

Note: This setting only affects the frequency of data extraction from Outbrain, not the interval at which data is loaded into your data warehouse. For example: a one (1) minute Replication Frequency means Stitch will attempt to extract data every minute, but loading the extracted data may take longer than this.

Use the Default Frequency

To use the default Replication Frequency (30 minutes), leave the Use integration default box checked and click Check and Save to create the integration.

Customize the Frequency

To adjust the Replication Frequency:

  1. Uncheck the Use integration default checkbox. A slider with various frequencies will display.
  2. Click the desired frequency on the slider.
  3. Click Check and Save to create the integration.

To help prevent overages, consider setting the integration to replicate less frequently. See the Understanding & Reducing Your Row Usage guide for tips on reducing your usage.

Outbrain’s Intial Replication Job

After you finish setting up Outbrain, you might see its Sync Status 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.


Outbrain Table Schemas

campaign_performance

Replication Method: Incremental Replication Key : fromDate
Primary Key : campaignId : fromDate API Endpoint: retrieveCampaignsWithPerformanceStatisticsForAMarketer

The campaign_performance table contains performance metrics for your Outbrain campaigns.

campaignId
STRING

The campaign ID plus the start date (day).

fromDate
DATE

The start date.

impressions
NUMBER

The total number of PromotedLinks impressions for the campaign.

clicks
NUMBER

The total number of PromotedLinks clicks for the campaign.

ctr
NUMBER

The average click through rate percentage for the campaign. Calculated as (clicks / impressions)/100

spend
NUMBER

The total amount of money spent for the campaign.

ecpc
NUMBER

The effective (calculated) average CPC (Cost Per Click) for the campaign. Calculated as (spend / clicks)

conversions
NUMBER

The total number of conversions for the campaign.

conversionRate
NUMBER

The average rate of conversions per click percentage for the campaign. Calculated as (conversions / clicks)/100

cpa
NUMBER

The average CPA (Cost Per Acquisition) for the campaign. Calculated as (spend / conversions)


Replication Method: Incremental Replication Key : n/a
Primary Key : id API Endpoint: listAllCampaignsAssociatedWithAMarketer

The campaigns table contains info about your Outbrain campaigns.

id
STRING

The campaign ID.

name
STRING

The name of the campaign.

campaignOnAir
BOOLEAN

Indicates if the campaign is on air.

onAirReason
STRING

The reason for the campaign’s on air status.

enabled
BOOLEAN

Indicates if the campaign is enabled.

budget__id
STRING

The budget ID.

budget__name
STRING

The name of the budget.

budget__shared
BOOLEAN

Indicates if the budget is shared between campaigns.

budget__amount
NUMBER

The monetary amount of the budget.

budget__currency
STRING

The currency denomination applied to the budget.

budget__amountRemaining
NUMBER

The unspent monetary amount remaining on the budget.

budget__amountSpent
NUMBER

The spent monetary amount of the budget.

budget__creationTime
DATE-TIME

The time when the budget was created.

budget__lastModified
DATE-TIME

The time the budget was last updated.

budget__startDate
DATE

The date the budget is scheduled to begin spending.

budget__endDate
DATE

The date the budget is scheduled to stop spending. If the runForever attribute is true, this attribute will not be present for the budget.

budget__runForever
BOOLEAN

Indicates if the budget has an end date. If true, the endDate attribute will not be present for the budget.

budget__type
STRING

Indicates the period on which the budget refreshes. Ex: monthly

budget__pacing
STRING

Indicates how fast the budget will be spent. Ex: automatic

budget__dailyTarget
NUMBER

The maximum amount of spend that is allowed per day.

budget__maximumAmount
NUMBER

The maximum amount allowed, if defined.

cpc
NUMBER

The cost per monetized user action. For example: cost per click.



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.