Sorry, we don't support your browser.  Install a modern browser

Amazon DSP: add the total_new_to_brand_* (brand halo) metrics#1942

T

Problem
The amazon_dsp connector exposes the promoted-product new-to-brand metrics
(new_to_brand_product_sales, new_to_brand_purchases, new_to_brand_units_sold,
new_to_brand_roas) but none of the corresponding total_* variants that include
brand halo. Amazon’s DSP campaign report returns both families, and our previous
pipeline delivered them.

Why this looks like an oversight rather than a design decision
For every other conversion metric the connector already ships both variants:
sales and total_sales, units_sold and total_units_sold, purchases and
total_purchases, roas and total_roas. New-to-brand is the only family where the
total_* side is missing.

Impact
Our monthly client reports show the brand halo variant. For one advertiser in
April 2026 the figure is 10,333.62 EUR with halo versus 8,083.39 EUR without, a
difference of 21.8 percent. Without the field we would have to change a number
we have been reporting to clients for months, or keep a second pipeline running
just for this one metric.

Requested fields (dsp_campaign)

  • total_new_to_brand_sales
  • total_new_to_brand_purchases
  • total_new_to_brand_units_sold
  • total_new_to_brand_roas
    Nice to have, same family: total_new_to_brand_purchase_rate,
    total_new_to_brand_detail_page_views

Done when
dsp_campaign returns the total_* new-to-brand metrics, and the values match the
Amazon DSP console for the same advertiser and date range.

3 hours ago