Outbrain is a third-party, content discovery platform that offers native advertising. It is dedicated exclusively to drawing data-driven connections between users’ interests and actions to help you target that very behavior and promote your post on other pieces of content in order to attract readers from other websites.
You can replicate your marketer and ad campaign data from Outbrain to a Destination database or data warehouse using Hevo Pipelines.
Prerequisites
-
An active Outbrain account from which data is to be ingested exists.
-
You are assigned the Team Administrator, Team Collaborator, or Pipeline Administrator role in Hevo to create the Pipeline.
Obtaining Login Credentials
-
Register for the Outbrain Amplify API.
-
Find the credentials for accessing Outbrain APIs in the confirmation e-mail received from Outbrain.
You can use these credentials while configuring your Hevo Pipeline.
Configuring Outbrain as a Source
Perform the following steps to configure Outbrain as the Source in your Pipeline:
-
Click PIPELINES in the Navigation Bar.
-
Click + CREATE PIPELINE in the Pipelines List View.
-
In the Select Source Type page, select Outbrain.
-
In the Configure your Outbrain Source page, specify the following:
-
Pipeline Name: A unique name for the Pipeline, not exceeding 255 characters.
-
Username: The username in the access credentials obtained from Outbrain.
-
Password: The password in the access credentials obtained from Outbrain.
-
Historical Sync Duration: The duration for which you want to ingest the existing data from the Source. Default duration: 1 Year.
Note: If you select All Available Data, Hevo ingests all the data available in your Outbrain account since May 01, 2015.
-
-
Click TEST & CONTINUE.
-
Proceed to configuring the data ingestion and setting up the Destination.
Data Replication
| For Teams Created | Default Ingestion Frequency | Minimum Ingestion Frequency | Maximum Ingestion Frequency | Custom Frequency Range (in Hrs) |
|---|---|---|---|---|
| Before Release 2.21 | 6 Hrs | 3 Hrs | 24 Hrs | 3-24 |
| After Release 2.21 | 6 Hrs | 30 Mins | 24 Hrs | 1-24 |
Note: The custom frequency must be set in hours as an integer value. For example, 1, 2, or 3 but not 1.5 or 1.75.
-
Historical Data: The first run of the Pipeline ingests historical data for the selected objects on the basis of the historical sync duration specified at the time of creating the Pipeline and loads it to the Destination. Default duration: 1 Year.
-
Incremental Data: Once the historical load is complete, data is ingested as per the ingestion frequency in Full Load or Incremental mode, as applicable.
-
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:
Data Model
The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:
| Object | Description |
|---|---|
| Budget | Details and activity statuses for all budgets associated with a marketer. Budget objects represent the amount of money to be spent via the Amplify platform. Usually a budget belongs to a single campaign unless it is a shared budget. |
| Marketer | Data for all marketers associated with the current user. Marketers are representatives of Outbrain customers. A single Marketer object may control campaigns for more than one end-buyer. |
| Conversion | All Conversion Events associated with a marketer. Multiple conversions give the ability to track any action a user takes after clicking through to your content (Requires multiple custom pixels by end user). |
| Campaign | Campaigns contain many promoted links and define budget, targeting, and cpc. Campaign settings apply to the promoted links contained in a specific campaign. Derived tables: - Targeting Location - Targeting Location Parent - Bids by Section |
| Section | Specific content category within the publisher’s site such as sports or business. This object fetches the full list of sections’ metadata, classified by sections’ IDs. |
| Segments | Segments give the ability to segment customers based on their actions, and retarget them with new or existing campaigns. Derived tables: - Campaign Segment |
| Targeting Interest | Information that provides a mapping of interests to each campaign. |
| Campaign Report | Daily campaign-level report covering all the performance metrics, such as, views, clicks, and conversions. |
| Section Report | Daily section-level report covering all performance metrics such as views, clicks, and conversions. |
Limitations
- None.
Revision History
Refer to the following table for the list of key updates made to this page:
| Date | Release | Description of Change |
|---|---|---|
| Mar-05-2024 | 2.21 | Updated the ingestion frequency table in the Data Replication section. |
| Feb-20-2023 | NA | Updated section, Configuring Outbrain as a Source to update the information about historical sync duration. |
| Dec-07-2022 | NA | Updated section, Data Replication to reorganize the content for better understanding and coherence. |
| Jul-26-2021 | NA | Added a note in the Overview section about Hevo providing a fully-managed Google BigQuery Destination for Pipelines created with this Source. |