<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Reddit Ads API Blog</title>
        <link>https://ads-api-reddit.netlify.app/blog</link>
        <description>Reddit Ads API Blog</description>
        <lastBuildDate>Tue, 30 Jun 2026 00:00:00 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <item>
            <title><![CDATA[June 2026 Reddit Ads API Updates]]></title>
            <link>https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update</link>
            <guid>https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update</guid>
            <pubDate>Tue, 30 Jun 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Reddit Ads API June 2026 updates: ad URL editing, Structured Posts, asset-level reporting, catalog diagnostics, and feature-access queries.]]></description>
            <content:encoded><![CDATA[<p>Hi Developer,</p>
<p>Please read the Reddit Ads API updates for June 2026.</p>
<ul>
<li class=""><a class="" href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#campaign-management">Campaign Management</a></li>
<li class=""><a class="" href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#creative-management">Creative Management</a></li>
<li class=""><a class="" href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#targeting">Targeting</a></li>
<li class=""><a class="" href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#audience-management">Audience Management</a></li>
<li class=""><a class="" href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#post-management">Post Management</a></li>
<li class=""><a class="" href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#catalog-management">Catalog Management</a></li>
<li class=""><a class="" href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#conversion-signals">Conversion Signals</a></li>
<li class=""><a class="" href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#reporting">Reporting</a></li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="campaign-management">Campaign Management<a href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#campaign-management" class="hash-link" aria-label="Direct link to Campaign Management" title="Direct link to Campaign Management" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="filter-ads-by-configured-and-effective-status">Filter ads by configured and effective status<a href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#filter-ads-by-configured-and-effective-status" class="hash-link" aria-label="Direct link to Filter ads by configured and effective status" title="Direct link to Filter ads by configured and effective status" translate="no">​</a></h3>
<p><a href="https://ads-api.reddit.com/docs/v3/operations/List%20Ads" target="_blank" rel="noopener noreferrer" class=""><code>List Ads</code></a> now supports <code>configured_status</code> and <code>effective_status</code> query parameters for filtering ads. Developers can use these filters to more easily narrow ad results inside their own tools, which makes it faster for advertisers to review delivery state, troubleshoot campaign setup, and take action on the right ads without extra manual sorting.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="creative-management">Creative Management<a href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#creative-management" class="hash-link" aria-label="Direct link to Creative Management" title="Direct link to Creative Management" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="access-creative-assets-via-api">Access creative assets via API<a href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#access-creative-assets-via-api" class="hash-link" aria-label="Direct link to Access creative assets via API" title="Direct link to Access creative assets via API" translate="no">​</a></h3>
<p><a href="https://ads-api.reddit.com/docs/v3/operations/List%20Creative%20Assets" target="_blank" rel="noopener noreferrer" class=""><code>List Creative Assets</code></a> and <a href="https://ads-api.reddit.com/docs/v3/operations/Get%20Creative%20Asset" target="_blank" rel="noopener noreferrer" class=""><code>Get Creative Asset</code></a> are now available. This gives developers direct access to creative asset data, making it easier to build creative libraries, sync asset visibility into partner tools, and support more efficient advertiser workflows around asset review and reuse.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="targeting">Targeting<a href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#targeting" class="hash-link" aria-label="Direct link to Targeting" title="Direct link to Targeting" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="enable-language-targeting-for-ad-groups">Enable language targeting for ad groups<a href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#enable-language-targeting-for-ad-groups" class="hash-link" aria-label="Direct link to Enable language targeting for ad groups" title="Direct link to Enable language targeting for ad groups" translate="no">​</a></h3>
<p>Language targeting is now available for third-party API users, and supported languages can be retrieved with <a href="https://ads-api.reddit.com/docs/v3/operations/List%20Languages" target="_blank" rel="noopener noreferrer" class=""><code>List Languages</code></a>. Developers can now build language targeting directly into campaign setup flows, helping advertisers reach more relevant audiences and manage multilingual campaign strategy more efficiently through partner tools.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="audience-management">Audience Management<a href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#audience-management" class="hash-link" aria-label="Direct link to Audience Management" title="Direct link to Audience Management" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="return-business-ids-on-custom-audiences">Return business IDs on custom audiences<a href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#return-business-ids-on-custom-audiences" class="hash-link" aria-label="Direct link to Return business IDs on custom audiences" title="Direct link to Return business IDs on custom audiences" translate="no">​</a></h3>
<p>Custom audience responses now include the read-only <code>business_id</code> field across <a href="https://ads-api.reddit.com/docs/v3/operations/Get%20Custom%20Audience" target="_blank" rel="noopener noreferrer" class=""><code>Get Custom Audience</code></a>, <a href="https://ads-api.reddit.com/docs/v3/operations/List%20User%20Custom%20Audiences" target="_blank" rel="noopener noreferrer" class=""><code>List User Custom Audiences</code></a>, and <a href="https://ads-api.reddit.com/docs/v3/operations/Create%20Custom%20Audience" target="_blank" rel="noopener noreferrer" class=""><code>Create Custom Audience</code></a>. This gives developers clearer business-level context for audience objects, which can simplify account mapping and audience management workflows for advertisers operating across multiple businesses or teams.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="post-management">Post Management<a href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#post-management" class="hash-link" aria-label="Direct link to Post Management" title="Direct link to Post Management" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="support-user-generated-content-controls-in-structured-posts">Support user-generated content controls in structured posts<a href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#support-user-generated-content-controls-in-structured-posts" class="hash-link" aria-label="Direct link to Support user-generated content controls in structured posts" title="Direct link to Support user-generated content controls in structured posts" translate="no">​</a></h3>
<p>Structured Posts now expose user-generated content enhancement settings on text, image, and video ad creatives in <a href="https://ads-api.reddit.com/docs/v3/operations/Get%20Structured%20Post" target="_blank" rel="noopener noreferrer" class=""><code>Get Structured Post</code></a> responses and <a href="https://ads-api.reddit.com/docs/v3/operations/Create%20Structured%20Post%20Creation%20Job" target="_blank" rel="noopener noreferrer" class=""><code>Create Structured Post Creation Job</code></a> requests. Developers can use <code>enhancements.user_generated_content.enroll_status</code> to indicate whether user-generated content may appear in an ad, making it easier to support newer creative controls in their integrations and helping advertisers adopt richer creative formats with more confidence.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="view-structured-post-creation-timestamps">View structured post creation timestamps<a href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#view-structured-post-creation-timestamps" class="hash-link" aria-label="Direct link to View structured post creation timestamps" title="Direct link to View structured post creation timestamps" translate="no">​</a></h3>
<p>The Structured Post schema now includes a read-only <code>created_at</code> field in <a href="https://ads-api.reddit.com/docs/v3/operations/List%20Structured%20Posts" target="_blank" rel="noopener noreferrer" class=""><code>List Structured Posts</code></a>, <a href="https://ads-api.reddit.com/docs/v3/operations/Get%20Structured%20Post" target="_blank" rel="noopener noreferrer" class=""><code>Get Structured Post</code></a>, and <a href="https://ads-api.reddit.com/docs/v3/operations/Update%20Structured%20Post" target="_blank" rel="noopener noreferrer" class=""><code>Update Structured Post</code></a> responses. This gives developers more visibility into post creation timing, which can improve content management workflows, troubleshooting, and internal auditability for advertisers managing larger creative libraries.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="catalog-management">Catalog Management<a href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#catalog-management" class="hash-link" aria-label="Direct link to Catalog Management" title="Direct link to Catalog Management" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="track-invalid-products-across-catalogs-and-product-sets">Track invalid products across catalogs and product sets<a href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#track-invalid-products-across-catalogs-and-product-sets" class="hash-link" aria-label="Direct link to Track invalid products across catalogs and product sets" title="Direct link to Track invalid products across catalogs and product sets" translate="no">​</a></h3>
<p>Product Catalog and Product Set responses now include the read-only <code>invalid_products_count</code> field in the summary, such as <a href="https://ads-api.reddit.com/docs/v3/operations/List%20Product%20Catalogs" target="_blank" rel="noopener noreferrer" class=""><code>List Product Catalogs</code></a>, showing how many products have critical issues and were not submitted for review. This gives developers a clearer way to surface catalog health in their tools and helps advertisers identify product feed problems faster so they can resolve issues before they affect catalog-based campaigns.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="conversion-signals">Conversion Signals<a href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#conversion-signals" class="hash-link" aria-label="Direct link to Conversion Signals" title="Direct link to Conversion Signals" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="expose-enhanced-signal-collection-configuration-on-pixels">Expose enhanced signal collection configuration on Pixels<a href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#expose-enhanced-signal-collection-configuration-on-pixels" class="hash-link" aria-label="Direct link to Expose enhanced signal collection configuration on Pixels" title="Direct link to Expose enhanced signal collection configuration on Pixels" translate="no">​</a></h3>
<p>The Pixel schema now includes <code>enhanced_signal_collection_config</code> in <a href="https://ads-api.reddit.com/docs/v3/operations/List%20Pixels%20By%20Ad%20Account" target="_blank" rel="noopener noreferrer" class=""><code>List Pixels By Ad Account</code></a> and <a href="https://ads-api.reddit.com/docs/v3/operations/List%20Pixels%20By%20Business" target="_blank" rel="noopener noreferrer" class=""><code>List Pixels By Business</code></a> responses. This gives developers more visibility into pixel configuration details and can help advertisers better understand how signal collection is set up across accounts as they manage measurement and optimization workflows.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="reporting">Reporting<a href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#reporting" class="hash-link" aria-label="Direct link to Reporting" title="Direct link to Reporting" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="expand-custom-conversion-event-reporting">Expand custom conversion event reporting<a href="https://ads-api-reddit.netlify.app/blog/06-2026-monthly-update#expand-custom-conversion-event-reporting" class="hash-link" aria-label="Direct link to Expand custom conversion event reporting" title="Direct link to Expand custom conversion event reporting" translate="no">​</a></h3>
<p>The <a href="https://ads-api.reddit.com/docs/v3/operations/Get%20A%20Report" target="_blank" rel="noopener noreferrer" class="">Reporting API</a> now supports <code>conversion_custom_events</code> in <a href="https://ads-api.reddit.com/docs/v3/operations/Get%20A%20Report" target="_blank" rel="noopener noreferrer" class=""><code>Get A Report</code></a> requests and responses, so developers can request custom conversion events by name with selected metrics and action sources. Reddit also added the <code>LANGUAGE</code> breakdown, giving developers more flexibility in how they structure reporting workflows and helping advertisers get more granular performance insights across markets and multilingual campaigns.</p>
<p>Thank you for your business.</p>
<p>Reddit Ads API</p>]]></content:encoded>
            <category>monthly updates</category>
            <category>creative assets</category>
            <category>targeting</category>
            <category>custom audiences</category>
            <category>structured posts</category>
            <category>reporting</category>
            <category>product catalogs</category>
            <category>conversion signals</category>
        </item>
        <item>
            <title><![CDATA[May 2026 Reddit Ads API Updates]]></title>
            <link>https://ads-api-reddit.netlify.app/blog/05-2026-monthly-update</link>
            <guid>https://ads-api-reddit.netlify.app/blog/05-2026-monthly-update</guid>
            <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Reddit Ads API May 2026 updates: ad URL editing, Structured Posts, asset-level reporting, catalog diagnostics, and feature-access queries.]]></description>
            <content:encoded><![CDATA[<p>Hi Developer,</p>
<p>Please read the Reddit Ads API updates for May 2026.</p>
<ul>
<li class=""><a class="" href="https://ads-api-reddit.netlify.app/blog/05-2026-monthly-update#campaign-management">Campaign Management</a></li>
<li class=""><a class="" href="https://ads-api-reddit.netlify.app/blog/05-2026-monthly-update#post-management">Post Management</a></li>
<li class=""><a class="" href="https://ads-api-reddit.netlify.app/blog/05-2026-monthly-update#reporting">Reporting</a></li>
<li class=""><a class="" href="https://ads-api-reddit.netlify.app/blog/05-2026-monthly-update#catalog-management">Catalog Management</a></li>
<li class=""><a class="" href="https://ads-api-reddit.netlify.app/blog/05-2026-monthly-update#feature-access-management">Feature Access Management</a></li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="campaign-management">Campaign Management<a href="https://ads-api-reddit.netlify.app/blog/05-2026-monthly-update#campaign-management" class="hash-link" aria-label="Direct link to Campaign Management" title="Direct link to Campaign Management" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="update-click-url-query-parameters-on-existing-ads">Update Click URL query parameters on existing ads<a href="https://ads-api-reddit.netlify.app/blog/05-2026-monthly-update#update-click-url-query-parameters-on-existing-ads" class="hash-link" aria-label="Direct link to Update Click URL query parameters on existing ads" title="Direct link to Update Click URL query parameters on existing ads" translate="no">​</a></h3>
<p>The <code>Update Ad</code> endpoint now accepts <code>click_url_query_parameters</code> in the request body, bringing update behavior in line with ad creation. Developers can now modify tracking parameters on existing ads without recreating them, making it easier for advertisers to adjust URL tagging and measurement parameters on live ads to support cleaner attribution and more flexible campaign optimization.</p>
<p>➜ <a class="" href="https://ads-api-reddit.netlify.app/docs/v3/api/update-ad">Update Ad</a></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="post-management">Post Management<a href="https://ads-api-reddit.netlify.app/blog/05-2026-monthly-update#post-management" class="hash-link" aria-label="Direct link to Post Management" title="Direct link to Post Management" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="move-to-structured-posts-for-more-flexible-post-management">Move to Structured Posts for more flexible post management<a href="https://ads-api-reddit.netlify.app/blog/05-2026-monthly-update#move-to-structured-posts-for-more-flexible-post-management" class="hash-link" aria-label="Direct link to Move to Structured Posts for more flexible post management" title="Direct link to Move to Structured Posts for more flexible post management" translate="no">​</a></h3>
<p>We’ve marked the Post API as legacy and recommend moving to the new Structured Posts API for post management going forward. Structured Posts gives developers a more scalable, flexible framework for supporting image, text, video, and carousel creatives through an asynchronous creation flow, making it easier to build richer post workflows and unlock newer capabilities like Disclaimer Text for eligible clients.</p>
<p>➜ <a class="" href="https://ads-api-reddit.netlify.app/docs/v3/api/structured-posts">Structured Posts</a></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="reporting">Reporting<a href="https://ads-api-reddit.netlify.app/blog/05-2026-monthly-update#reporting" class="hash-link" aria-label="Direct link to Reporting" title="Direct link to Reporting" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="break-down-reporting-by-asset-id">Break down reporting by asset ID<a href="https://ads-api-reddit.netlify.app/blog/05-2026-monthly-update#break-down-reporting-by-asset-id" class="hash-link" aria-label="Direct link to Break down reporting by asset ID" title="Direct link to Break down reporting by asset ID" translate="no">​</a></h3>
<p>We’ve added the <code>ASSET_ID</code> breakdown to the Reporting API, giving developers a new way to segment report output alongside existing fields and breakdowns. This makes it easier to build more granular asset-level reporting in their own tools, helping advertisers understand which creative assets are driving results and optimize creative strategy with greater precision.</p>
<p>➜ <a class="" href="https://ads-api-reddit.netlify.app/docs/v3/api/get-a-report">Get A Report</a></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="catalog-management">Catalog Management<a href="https://ads-api-reddit.netlify.app/blog/05-2026-monthly-update#catalog-management" class="hash-link" aria-label="Direct link to Catalog Management" title="Direct link to Catalog Management" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="track-invalid-products-in-catalog-imports">Track invalid products in catalog imports<a href="https://ads-api-reddit.netlify.app/blog/05-2026-monthly-update#track-invalid-products-in-catalog-imports" class="hash-link" aria-label="Direct link to Track invalid products in catalog imports" title="Direct link to Track invalid products in catalog imports" translate="no">​</a></h3>
<p>The <code>List Catalog Imports</code> response now includes a read-only <code>invalid_products_count</code> field in the summary, showing how many products were rejected as invalid and not imported. This gives developers a clearer way to monitor import health and surface feed-quality diagnostics in their catalog workflows, so they can help advertisers identify rejected products faster, troubleshoot import issues more efficiently, and reduce manual investigation.</p>
<p>➜ <a class="" href="https://ads-api-reddit.netlify.app/docs/v3/api/list-catalog-imports">List Catalog Imports</a></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="feature-access-management">Feature Access Management<a href="https://ads-api-reddit.netlify.app/blog/05-2026-monthly-update#feature-access-management" class="hash-link" aria-label="Direct link to Feature Access Management" title="Direct link to Feature Access Management" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="query-feature-access-by-conversion-pixel">Query feature access by conversion pixel<a href="https://ads-api-reddit.netlify.app/blog/05-2026-monthly-update#query-feature-access-by-conversion-pixel" class="hash-link" aria-label="Direct link to Query feature access by conversion pixel" title="Direct link to Query feature access by conversion pixel" translate="no">​</a></h3>
<p>The <code>Get Feature Access</code> endpoint now supports a <code>conversion_pixel_id</code> parameter, allowing developers to query feature access based on a specific conversion pixel ID.&nbsp;</p>
<p>➜ <a class="" href="https://ads-api-reddit.netlify.app/docs/v3/api/get-feature-access">Get Feature Access</a></p>
<p>Please reach out with any questions or concerns.</p>
<p>Reddit Ads API</p>]]></content:encoded>
            <category>monthly updates</category>
            <category>ads</category>
            <category>structured posts</category>
            <category>posts</category>
            <category>reporting</category>
            <category>product catalogs</category>
            <category>feature access</category>
        </item>
        <item>
            <title><![CDATA[Conversion Pixel ID Requirement Notice]]></title>
            <link>https://ads-api-reddit.netlify.app/blog/conversion-pixel-id-requirement-notice</link>
            <guid>https://ads-api-reddit.netlify.app/blog/conversion-pixel-id-requirement-notice</guid>
            <pubDate>Mon, 13 Apr 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Starting July 13th, 2026, all ad groups and campaign budget optimization (CBO) campaigns require a `conversion_pixel_id` to be set.]]></description>
            <content:encoded><![CDATA[<p>Starting July 13th, 2026, all ad groups and campaign budget optimization (CBO) campaigns require a <code>conversion_pixel_id</code> to be set.</p>
<p>Update your campaigns and ad groups to prevent delivery issues. Find your Pixels with <a class="" href="https://ads-api-reddit.netlify.app/docs/v3/api/list-pixels-by-ad-account"><code>List Pixels by Ad Account</code></a>.</p>
<p>Contact <a href="mailto:adsapi-partner-support@reddit.com" target="_blank" rel="noopener noreferrer" class="">adsapi-partner-support@reddit.com</a> for support or questions.</p>]]></content:encoded>
            <category>notice</category>
            <category>campaigns</category>
            <category>ad groups</category>
        </item>
    </channel>
</rss>