Skip to main content
All CollectionsIntentwise Explore (AMC)Instructional Queries
Instructional Query: DSP Reach and Impression Frequency
Instructional Query: DSP Reach and Impression Frequency

Gain insights into the DSP Reach and Impression Frequency query and its applications on Intentwise Explore (AMC).

Ankita Goyal avatar
Written by Ankita Goyal
Updated over a week ago

What are instructional queries?

Amazon Marketing Cloud's (AMC) instructional queries provide pre-written SQL code that AMC users can use as is or modify for common measurement and analytics tasks.

DSP Reach and Impression Frequency

The DSP Reach and Impression Frequency query helps you understand how often your DSP ads are shown to the same users. By analyzing the frequency distribution of ad impressions, you can gain insights into the effectiveness of your ad targeting and frequency capping strategies. This information is essential for optimizing your campaigns and ensuring efficient use of your ad impressions.

To use this query, you'll need to have campaigns delivered with Amazon DSP. The query provides two options: one for analyzing reach and frequency for your Amazon DSP campaigns exclusively and another for analyzing reach and frequency across multiple Amazon advertising channels (DSP, Sponsored Products, Sponsored Brands, and Sponsored Display). Choose the option that best suits your campaign setup and objectives.

The query results include detailed metrics such as frequency buckets (indicating how many times an ad was shown to users), the number of distinct users in each frequency bucket, and the total impressions in each frequency bucket. These metrics allow you to analyze the distribution of ad impressions across different frequency levels, helping you understand how your ad exposure strategy impacts user reach and engagement.

You can also calculate the percentage of users exposed to different frequency buckets and the average impression frequency per user, enabling you to refine your campaign strategies based on reach and frequency considerations.

For more information, refer to our data model.

Did this answer your question?