Skip to main content

ID-Precise Segments: Low Delivery

C
Written by Cindy Hwang

Situations

“My Id-precise segment is not delivering as expected.”

"My Id-precise segment shows a lower number of MAIDs in the DSP than Adsquare”

“My Id-precise segment is working and I have a high number of MAU, but the delivery is very low.”

Campaign Set Up Recommendations

Please note that if there is delivery on the segment, there are usually no issues in terms of data transfer but rather settings applied on the campaign that conflict and block the delivery.

While it is possible to observe a difference in the number of users between Adsquare and the DSP, this depends on the rules by the DSP when they ingest MAIDs - however the difference should be marginal, ie. around 10%.


Please find below some best practices to follow through the campaign set-up on the DSP:

Device Targeting Type

Smartphones & Tablets should be selected for the In-App traffic.

Ad Environment

Only In-App targeting should be selected.

The Mobile Advertising ID (IDFA/ GAID) is necessary for the bid-request.

Day-Part Filter

There is no need to add Day-Part filter to the DSP if it was already applied via AMP. Double filtering can lead to a potential reach reduction.

Tip: to reach households while using Place Visits → adjust the store opening hours during evenings and early mornings.

Geographical Filter

  • Do not add a country geographical location in the DSP as the country level is already defined by Adsquare

  • Adding additional geographical filters will reduce reach through double filtering

Frequency & Pacing

  • Low impressions frequency cap can drastically reduce the number of bid opportunities;

  • A lifetime frequency cap might deplete the audience pool over time.

Creatives

  • It is important to have a variety of mobile-friendly ad sizes that can be served across a wide range of apps;

  • The majority of the inventory is spread among the following sizes: 300x250, 320x50, 728x90 and 300x50.

Brand Safety

Check if the Brand Safety is compatible with In-App inventory.

Several Brand Safety categories are not enabled for In-App inventory and may block delivery.

Data Targeting

The recommendation is to use Adsquare as sole data provider for a specific segment. If you use another data provider for the same segment, the chances of incompatibility increase and it may also reduce the potential reach & delivery.

In addition:

  • If you are using a Custom Place Visits dataset in your segment, ie. a dataset built by Adsquare based on your own locations, bear in mind that this dataset needs to be updated if it is older than 3 or 6 months, depending on the agreement during the creation process.
    If that is the case, please contact your Adsquare Account Manager to check the status and proceed with the update.

DSP Specifications

DV360

Google offers a bid troubleshooter that allows you easily analyze problems with private auctions, guaranteed deals, non-guaranteed fixed deals, and open auction line items. You can find more details here on how to use the Troubleshooter: Troubleshoot your deals and line items - Display & Video 360 Help

Hawk

  • You can ensure that Mobile-Application traffic is enabled under the 'Content' line item

Information to provide

In case the information above does not resolve your issue, please raise a request answering the following questions:

  • When was the campaign activated?

  • Is the campaign targeting In-App?

  • Is the campaign running in OMP (Open Marketplace) or PMP (Private Marketplace)?

  • Is there any whitelist or blacklist applied?

  • Does the whitelist include In-App inventory and excludes web inventory?

  • Are the following settings selected to the campaign?

    • Brand Safety (e.g. IAS)

    • Viewability

    • Geographical Filter

  • Does the campaign runs through enough mobile friendly creatives?

  • Is there an overlay between Adsquare data and any other data?

  • Is there a combination of Id-precise and Geo-contextual targeting?

Did this answer your question?