--- title: "Good to know about Outbrain DSP (Zemanta)" slug: "good-to-know-about-outbrain-dsp-zemanta" description: "Learn more about request limits, historical range, and things to consider when using the Outbrain DSP (Zemanta) data source in Supermetrics." updated: 2026-11-12T11:59:51Z published: 2026-11-12T11:59:51Z canonical: "docs.supermetrics.com/good-to-know-about-outbrain-dsp-zemanta" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.supermetrics.com/llms.txt > Use this file to discover all available pages before exploring further. # Good to know about Outbrain DSP (Zemanta) This article gives you tips for building queries and reports that return the data you need, including how the API of this data source handles certain fields and metrics. If you’re connecting to Outbrain DSP (Zemanta), follow the instructions in our [connection guide](/v1/docs/outbrain-dsp-zemanta-connection-guide). See [Outbrain DSP (Zemanta) metrics and dimensions](/v1/docs/outbrain-dsp-zemanta-fields) for the fields available in this data source. ## Request limits and recommended refresh window **Request limit**: 20 requests per second **Recommended refresh window**: 2-3 days ## Historical range There are no known limitations to the historical range of data you can pull with the Outbrain DSP (Zemanta) data source connector. ## Accounts in Outbrain DSP (Zemanta) In the Outbrain DSP (Zemanta) connector, each Account is considered a separate account within the connection. Your Supermetrics subscription determines how many [data source accounts](https://docs.supermetrics.com/docs/about-data-source-accounts) you can use simultaneously. ## Things to consider ### Bid dimension The Bid dimension can only be returned if Ad group is included in the query. ### Incompatible breakdown dimensions Some breakdowns return empty if they are incompatible: - **Creative assets**: Compatible only with Creative & Creative ID - **Delivery**: Only one delivery breakdown possible per report (excluding Media Source fields) ### API performance The underlying Teads DSP API is asynchronous and can be rather slow with heavier queries. ## More resources - [Outbrain DSP (Zemanta) connection guide](/v1/docs/outbrain-dsp-zemanta-connection-guide) - [Outbrain DSP (Zemanta) metrics and dimensions](/v1/docs/outbrain-dsp-zemanta-fields)