Outbrain
Outbrain is a native advertising platform using targeted advertising to recommend articles, slideshows, blog posts, photos or videos to a reader.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | check | BID_CPC_BY_SECTION_HISTORY, BUDGET_HISTORY, CAMPAIGN_HISTORY, CAMPAIGN_SEGMENT, CONVERSION_TRACKING_HISTORY, MARKETER_HISTORY, PROMOTED_LINK_HISTORY, SEGMENT_HISTORY, SUFFIX_TRACKING_CODE_HISTORY andTARGETING_LOCATION tables. |
| History mode | check | PROMOTED_LINK_HISTORY, SUFFIX_TRACKING_CODE_HISTORY, BID_CPC_BY_SECTION_HISTORY, CAMPAIGN_HISTORY, SEGMENT_HISTORY, BUDGET_HISTORY, MARKETER_HISTORY and CONVERSION_TRACKING_HISTORY tables. |
| Custom data | ||
| Data blocking | check | |
| Column hashing | check | |
| Re-sync | check | |
| API configurable | check | API configuration |
| Priority-first sync | check | |
| Fivetran data models | ||
| Private networking | ||
| Authorization via API | check |
Setup guide
Follow our step-by-step Outbrain setup guide to connect Outbrain with your destination using Fivetran connectors.
Sync overview
The Outbrain connector supports multithreading. We use multiple parallel API requests to sync Ads data from your Outbrain account to your destination. The connector’s sync speed depends on your Outbrain API quota and account metadata.
Schema information
Outbrain's schema follows Fivetran's standard API schema rules.
Schema
To zoom, open the ERD in a new window.Schema notes
The following details can provide some helpful supplementary information about how Fivetran's schema represents Outbrain relationships.
SuffixTrackingCode
Suffix tracking codes defined in Outbrain campaigns are blown out into SUFFIX_TRACKING_CODE_HISTORY; e.g. ?utm_source=facebook will yield key=utm_source, value=facebook.
GeolocationReport
Location-based reporting is on a per-country basis.
CampaignSegment
Both included and excluded segments in Campaigns are recorded in CAMPAIGN_SEGMENT. The value of CAMPAIGN_SEGMENT.status will be either INCLUDED or EXCLUDED to differentiate targeting relationships.
TargetingInterest
Outbrain allows campaigns to target customers users based on interests, and also provides some simple logic for more constrained targeting.
Example #1: Interest A or B
This configuration would add 2 records to TARGETING_INTEREST where match_op=INCLUDED.
Example #2: not Interest A (exclude people who match at least one)
This configuration would add 1 record to TARGETING_INTEREST where match_op=EXCLUDED.
Example #3: Interest (A or B) and (C or D)
This configuration yields the below mapping, where interest=INTEREST.name.
interest match_op
-----------------------------
Justice INCLUDED
Gadgets INCLUDED
Crime ALSO_INCLUDED
Martial arts ALSO_INCLUDED
Example #4: Interest (A or B) and (C or D or not E)
This configuration yields the below mapping, where interest=INTEREST.name.
interest match_op
-----------------------------
Justice INCLUDED
Gadgets INCLUDED
Crime ALSO_INCLUDED
Martial arts ALSO_INCLUDED
Comedy ALSO_EXCLUDED