Did the behavior of enableSingleRequest() change?

[Jim W.]

We used enableSingleRequest() to ensure that every ad on the page uses the same targeting and a single line item can fill every ad slot even if we don't call .display on the ad slot until later. That behavior has changed. Now whenever we use enableSingleRequest(), all defined ads will display immediately. There are some ads that we lazy load. We don't call .display on the ad slot until it's about to come into the user's view.

Is this a bug in enableSingleRequest() or is there a new way to have a single request and not display all ads immediately?

Thanks,

Jim

[Vincent Racaza (DFP API Team)]

Hi Jim,

Your concern seems to be specific on the DFP product level (displaying the ads on the web page), and not DFP API specific. Our team only handles DFP API related issues/concerns. Please post this concern in the DFP product forums as their team can better assist you on this.

Thanks,

Vincent Racaza, DFP API Team

[Jim W.]

Thanks for the heads up. I'll move my question.

Jim