Skip to main content

Introduction

RTB House is a retargeting and programmatic advertising platform. The Adriel connector fetches campaign structure and performance data from the RTB House API (v5), including impressions, clicks, advertiser cost, and conversion metrics reported across multiple count conventions. As a marketing connector, metrics, breakdowns, and currencies are standardized so widgets can aggregate across sources without additional configuration. To connect this data source, see How to connect RTB House to Adriel.

Data refresh strategy

Architecture data

Architecture covers ad accounts, campaigns, ad sets, and ads. It refreshes twice daily, at 4:00 PM UTC and 5:00 AM UTC.

Reports data

Reports include daily performance metrics for ad accounts, campaigns, ad sets, and ads. Real-time. Report data is fetched from RTB House on demand when a dashboard loads, so the latest values are always visible. On top of that, scheduled cache refreshes keep historical data consistent across multiple time windows. Refresh schedule. Reports refresh on three overlapping schedules:
  • 5:00 PM UTC daily — syncs the last 9 days for ad account, campaign, ad set, and ad
  • 11:40 PM and 6:40 AM UTC daily — syncs the last 3 days for ad account, campaign, ad set, and ad
  • 7:30 AM UTC on the 1st and 15th of each month — syncs the last 30 days for ad account, campaign, ad set, and ad

Architecture levels

Ad account → Campaign → Ad set → Ad
RTB House campaigns and ad sets share the same underlying subcampaign endpoint, so ad sets are modeled from subcampaign data. Statuses are normalized to Adriel values: ACTIVE → running, PAUSED → paused, NEW → scheduled, READY → in review.

Date range limits

To keep query sizes manageable, the maximum look-back window depends on the date grouping:

Attribution windows

RTB House reports conversions under four count conventions. After the base performance request, the connector issues one additional request per convention, and each convention produces its own conversion count and conversion value. Each convention generates a separate metric variant — for example, conversions are exposed as conversions:rtbHouse:ATTRIBUTED, conversions:rtbHouse:POST_VIEW, and so on, with a matching conversionValue:rtbHouse:{convention} for value.

Metrics

How to read the columns Data type uses this vocabulary: Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean. API Key in code style like impsCount is the literal RTB House API field name. Italic text describes how a value is produced when it doesn’t map cleanly to a single API field.

Delivery & clicks

Cost & spend

Currency values are reported in the ad account’s configured RTB House currency. If that differs from the workspace currency, costs are converted using the current day’s exchange rate.

Conversions & value

Conversion metrics are reported per count convention (see Attribution windows). Each named conversion event also generates its own set of derived metrics.
Per-conversion metrics. For each named conversion, the following dynamic columns are generated (where {convention} is one of the four count conventions):

Campaign structure metadata

Breakdowns

Campaign structure

Date breakdowns

Overview

Adriel-provided grouping options that do not map to an RTB House field.

Creative

Adriel post-processes ad creatives to group visually similar images together.

Limitations

  • 365-day report window — a single report query is capped at 365 days. Wider ranges are split into multiple requests.
  • Archived entities — archived campaigns and ad sets are included in architecture, while archived ad accounts (advertisers) are excluded. Reports may therefore contain entities that are no longer actively managed.
  • Active creatives only at the ad level — ad-level architecture is fetched with activeOnly=true, so paused or archived creatives may not appear as ads.
  • Ad-to-campaign resolution via cache — at the ad level, each row’s parent campaign is resolved from a 10-minute architecture cache. A creative not yet present in the cache may temporarily lack a campaign association.

API references

The connector calls the RTB House API (v5) using HTTP Basic authentication. The endpoints used are:
  • GET /advertisers — ad accounts
  • GET /advertisers/{hash}/campaigns — campaigns and ad sets (subcampaigns)
  • GET /advertisers/{hash}/rtb-creatives — ads (creatives)
  • GET /advertisers/{advertiserId}/rtb-stats — report statistics at all levels

See also