android best practice with ad in SlidingPanel/ViewPager

[Ahmed El-Helw]

hi,

i've integrated the new sdk and everything works great. in an app i am developing, the client wants a PublisherAdView in a sliding panel (so the fragment always exists and is resumed, but only visible when you swipe), and another in a ViewPager (on the third page, for example, which will not be visible unless the user swipes there, but may be created before hand due to ViewPager caching).

currently, my resume/destroy/pause calls live on the respective fragments - is this the best practice, or should i be doing something more involved (ex when the fragment is actually viewed, call resume, etc?)

thanks!

-ahmed

[Eric Leichtenschlag]

Hi Ahmed,

Technically speaking, I like the idea of keeping the AdView in alignment with the fragment lifecycle. If it's good enough for Android to preload a fragment 1 page early for optimization, it should be good enough for ads.

Keep in mind however, that loading the ads before they're actually shown could decrease click through rate since some ads may never technically be shown. For AdMob this would be fine since you get paid for clicks and not impressions. It sounds like the client is using DFP, where impressions are generally the key metric for charging the advertiser. Loading ads early could inflate the impression count. That may be something you'd want to confirm with the client, if they care about that implementation detail.

Thanks,
Eric

[Robert Richardson]

Hi Eric,

I made some changes to my campaigns. When you get a chance please check them out and let me know what you think.

Thanks for your help and support,

Bob Richardson

--

---
You received this message because you are subscribed to the Google Groups "Google AdMob Ads Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ahmed El-Helw]

sounds good, i'll speak with the client.

thanks Eric!

-ahmed

[Eric Leichtenschlag]

Hi Bob,

I just answered your question on from the other thread. Please keep the discussion about a topic on its own thread going forward.

Thanks,

Eric

On Tuesday, April 8, 2014 6:29:40 PM UTC-7, Robert Richardson wrote:

Hi Eric,

I made some changes to my campaigns. When you get a chance please check them out and let me know what you think.

Thanks for your help and support,

Bob Richardson

On Tue, Apr 8, 2014 at 8:25 PM, Eric Leichtenschlag wrote:

Hi Ahmed,

Technically speaking, I like the idea of keeping the AdView in alignment with the fragment lifecycle. If it's good enough for Android to preload a fragment 1 page early for optimization, it should be good enough for ads.

Keep in mind however, that loading the ads before they're actually shown could decrease click through rate since some ads may never technically be shown. For AdMob this would be fine since you get paid for clicks and not impressions. It sounds like the client is using DFP, where impressions are generally the key metric for charging the advertiser. Loading ads early could inflate the impression count. That may be something you'd want to confirm with the client, if they care about that implementation detail.

Thanks,
Eric

On Monday, April 7, 2014 12:08:14 AM UTC-7, Ahmed El-Helw wrote:

hi,

i've integrated the new sdk and everything works great. in an app i am developing, the client wants a PublisherAdView in a sliding panel (so the fragment always exists and is resumed, but only visible when you swipe), and another in a ViewPager (on the third page, for example, which will not be visible unless the user swipes there, but may be created before hand due to ViewPager caching).

currently, my resume/destroy/pause calls live on the respective fragments - is this the best practice, or should i be doing something more involved (ex when the fragment is actually viewed, call resume, etc?)

thanks!

-ahmed

--

---
You received this message because you are subscribed to the Google Groups "Google AdMob Ads Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.