Movatterモバイル変換


[0]ホーム

URL:


DOCS >INTEGRATIONS >SAAS >OUTBRAIN (V1)

Get started with a free trial today

Already have an account? Sign in

Outbrain (v1)

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

Outbrain integration summary

Stitch’s Outbrain integration replicates data using theOutbrain Amplify API. Refer to theSchema 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

Singer Community

Stitch plan

Standard

API availability

Available

Singer GitHub repository

singer-io/tap-outbrain

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

  1. Sign into your Stitch account.
  2. On the Stitch Dashboard page, click theAdd Integration button.

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

  5. In theAccount 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 betweenmarketers andcampaigns, if you’re looking at the Overview dashboard:

    https://my.outbrain.com/amplify/site/marketers/[account-id-will-be-here]/campaigns/overview

  6. In theUsername field, enter your Outbrain username.
  7. In thePassword 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 dataequal 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 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.

Outbrain 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 Outbrain, 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.

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

campaign_performance

Thecampaign_performance table contains performance metrics for your Outbrain campaigns.

Replication Method

Key-based Incremental

Primary Keys

campaignId

fromDate

Replication Key

fromDate

Useful links

Outbrain documentation

campaign_performance schema on GitHub

Outbrain API method

campaignId

STRING

clicks

NUMBER

conversionRate

NUMBER

conversions

NUMBER

cpa

NUMBER

ctr

NUMBER

ecpc

NUMBER

fromDate

DATE

impressions

NUMBER

spend

NUMBER

campaigns

Thecampaigns table contains info about your Outbrain campaigns.

Replication Method

Full Table

Primary Key

id

Useful links

Outbrain documentation

campaigns schema on GitHub

Outbrain API method

budget

OBJECT

amount

NUMBER

amountRemaining

NUMBER

amountSpent

NUMBER

creationTime

DATE-TIME

currency

STRING

dailyTarget

NUMBER

endDate

DATE

id

STRING

lastModified

DATE-TIME

maximumAmount

NUMBER

name

STRING

pacing

STRING

runForever

BOOLEAN

shared

BOOLEAN

startDate

DATE

type

STRING

campaignOnAir

BOOLEAN

cpc

NUMBER

enabled

BOOLEAN

id

STRING

name

STRING

onAirReason

STRING

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