RTB House Integration

RTB House doesn't run generic banner ads — it runs dynamic creative retargeting, where the specific products shown to each visitor are selected individually for them. That selection is only possible if RTB House has an accurate, current picture of your catalog: which products exist, what they cost, whether they're in stock, and how they're categorized. The product feed is what supplies that picture.

Behind each ad, RTB House combines two data sources: a tracking pixel installed on the advertiser's site, which captures what a visitor viewed, added to cart, or bought, and the product feed, which tells the system what those viewed items actually are — price, availability, category, image. Its deep learning models use that combination to predict which products a given visitor is statistically most likely to respond to, then assemble the creative and bid for the impression in real time. Without a well-structured, regularly updated feed, the retargeting engine has nothing to select from, no matter how sophisticated the underlying model is.

RTB House doesn't publish its internal matching logic, since it runs the model itself rather than exposing it, but third-party tag-management documentation for the RTB House retargeting pixel (Tealium's integration reference) shows the shape of the connection: the pixel fires events carrying an Offer ID, a Category ID, a Conversion ID, and a Conversion Value for each product a visitor interacts with. The Offer ID is the join key — it's expected to match the product identifier used in your feed — which is how RTB House resolves "visitor viewed offer #12345" into an actual product name, price and image when it builds a creative.

RTB House's own description of client onboarding (published on its blog) splits integration into three parallel workstreams: tagging (installing the pixel), feed (the client builds the feed, RTB House's team validates it), and creative (RTB House's team designs ad formats around the feed data). That structure fits an enterprise/managed model where feed formatting is finalized in coordination with an RTB House contact rather than against one public schema — though the newer self-service rtb.com platform is built to let advertisers configure tag and feed setup themselves, with creatives generated automatically.

RTB House has not published a public, field-level feed specification comparable to Google Merchant Center's or Meta's — which fits how it goes to market: most advertisers set up feeds in direct coordination with an RTB House account manager (or, on the newer rtb.com self-service platform, configure it themselves) rather than against a standardized public schema. RTB House's own published description of the process is simply that the advertiser "creates the feed and sends it to RTB House experts, who validate it" before it's used for creatives — the exact file format, delivery method and update cadence are confirmed during that setup conversation, not dictated by a fixed public document.

In practice, that generally means a feed delivered as an XML or CSV file hosted at a URL rather than manually uploaded — consistent with how RTB House's own official Shopify connector app works, syncing a store's product catalog automatically. What Feedance can guarantee on our side is a clean, always-current feed URL in a well-formed, standard structure (CSV, XML/RSS, or Google-Merchant-style XML) that you or your RTB House contact can validate against whatever field mapping your specific account requires.

RTB House does not publish a field-by-field attribute list the way some comparison shopping engines do, so we won't present one as if it were official. What is verifiable is narrower: third-party documentation of RTB House's tracking pixel confirms that the retargeting engine relies on an Offer ID and a Category ID to connect on-site browsing behavior back to a specific catalog item, alongside conversion/value data captured at checkout. For that matching to work, the identifier your feed uses for each product needs to match the identifier your RTB House tag sends for that same product.

Beyond that confirmed pair, the attributes RTB House's creative team will need to actually build dynamic ads are the ones any dynamic-creative retargeting platform needs: a stable product ID, product title, price, a usable product image, the landing-page URL, availability/stock status, and a category or product type. We list these because they're structurally necessary for feed-driven dynamic creative in general — not because RTB House has published them as a named, official attribute set — and the exact naming and formatting should be confirmed with your RTB House contact during setup.

1. In Feedance, build a feed from your store or existing catalog data and map your fields to a clean, standard structure (CSV or XML/RSS). Feedance normalizes prices, availability, and images so the feed stays well-formed as your catalog changes.
2. Feedance generates a hosted, always-current feed URL for that channel.
3. Share that feed URL with your RTB House account manager for validation — the enterprise/managed path — or paste it directly into the feed-setup step of the self-service rtb.com platform alongside your RTB House tracking pixel, if you're onboarding that way.
4. RTB House validates the feed against your account setup. On the managed path, its creative team builds ad formats around it; on the self-service path, creatives are generated automatically.
5. Keep the Feedance feed live and let it refresh on a schedule, so price, stock and catalog changes propagate to RTB House without manual re-uploads.

RTB House hasn't published a specific required refresh interval for advertiser feeds, so this is general best practice rather than an RTB House rule: for any real-time-bidding retargeting platform, an out-of-date feed is worse than a briefly slow one, because it can lead to ads showing sold-out products or the wrong price. Retailers with frequently changing stock or pricing — flash sales, limited-inventory drops — should aim to refresh at least daily, ideally several times a day; catalogs that change infrequently can update daily with no meaningful loss. Feedance can schedule automatic refreshes so the feed RTB House reads is never more than a few hours stale, regardless of how often your source catalog changes.

RTB House hasn't published a list of feed error codes specific to its platform, so rather than invent RTB-House-specific errors, here are the general feed-hygiene issues that most commonly break dynamic-creative retargeting on any platform, RTB House included:

• Mismatched or unstable product IDs. If the ID in your feed doesn't match the Offer ID your tracking pixel sends for that same product, the retargeting engine can't connect "this visitor looked at this item" back to a real product, and it won't appear in a personalized ad.
• Dead or low-resolution product images. Broken image URLs or images below basic size/quality thresholds tend to get skipped by dynamic creative templates, silently shrinking your effective catalog.
• Stale availability or price data. Showing an ad for a sold-out product, or at the wrong price, undermines trust and wastes bid spend on an impression that can't convert.
• Missing or inconsistent category data. Category/product-type fields are what let a deep learning model group similar products for cross-sell and lookalike recommendations; blank or inconsistent categories weaken that signal.
• Duplicate or variant-collapsed entries. Feeds that merge size/color variants into a single row lose the granularity retargeting needs to show a shopper the exact variant they viewed.

Feedance's feed validation flags most of these issues automatically, before the feed is shared with RTB House.

These are general best practices for feed-driven retargeting rather than RTB House-specific requirements, since RTB House doesn't publish an optimization playbook publicly:

1. Keep product titles descriptive and specific (brand, model, key attribute) — recommendation models generally perform better with more informative text per item.
2. Make sure every active, purchasable product is actually in the feed; gaps in coverage mean gaps in what the retargeting engine can ever show.
3. Use consistent, granular categories across your whole catalog so the model can reliably group and recommend similar items.
4. Sync price and stock status as close to real time as your platform allows, especially around sales or limited-stock drops.
5. Confirm your product ID scheme with your RTB House contact once, then keep it stable — changing IDs later breaks the pixel-to-feed match for products you've already been retargeting.

Does RTB House require a product feed?
Yes — feed data is what lets RTB House's deep learning models know what a shopper looked at and what to show them in a retargeting ad; a tracking pixel alone only captures behavior, not catalog detail.

Do I need a developer to connect my feed to RTB House?
Not necessarily. RTB House publishes an official Shopify connector app that automates both pixel and feed setup for Shopify stores, and its self-service rtb.com platform is built for advertisers to configure feed and tag themselves. Larger accounts on the managed/enterprise path typically hand the feed to an RTB House account manager instead of configuring it directly.

Is RTB House only available through an account manager?
That was historically the primary path, but as of March 2026 RTB House also offers a self-service platform, rtb.com, aimed at small and mid-sized e-commerce brands and agencies that want deep-learning retargeting without a long-term contract or dedicated account manager.

What exact fields does my feed need for RTB House?
RTB House hasn't published an official, named list of required feed fields. What's confirmed is that your feed's product identifier needs to match the Offer ID your RTB House tracking pixel sends for the same product; beyond that, standard fields — ID, title, price, image, URL, availability, category — cover what any dynamic-creative retargeting engine needs, and your RTB House contact can confirm any account-specific mapping.

Can Feedance host the feed RTB House uses?
Yes. Feedance builds and hosts a standard-format feed URL from your product data, refreshed on a schedule, that you can hand to your RTB House account manager or connect directly through the self-service platform.