Option to restart blocked providers

[linderboss]

Suggestion:

Property to change the current behaviour of removing permanently ad providers after a failed request.
The control could reactivate them after some time or number of requests.

[SimonDarksideJ]

Hmm, we'll consider this. Although in our experience the majority of cases when the provider doesn't deliver an add on an application run it doesn't deliver an ad for at least that day, if not that week.
We had this in testing with the fail check disabled and left it running for an hour or so on each provider (except AdDuplex of course since they never fail :D)

Only other reason for fail is lack of network, only in that situation would a retry possibly help

Thoughts

[linderboss]

I see your point.
I like the "retry after the network comes back" feature.
Most apps will not benefits from such feature, since their session length is short and multi-page XAML based (especially if you put banner on each page).

Maybe long running Windows Store apps or Unity games (not many XAML page transitions to initialize AdRotator) can find it useful. If PubCenter has a 97% fill rate and gives me the best ECPM, it will be nice to see it active most of the time. Maybe some fill rate real-time analysis to decide resurrecting a dead ad provider or not...

Well, it's a suggestion. If you come with something clever and useful it will be great. If not, just close this issue.

[jkw117]

I have a long running app, and I've seen it where the pubcenter especially will provide an advertisement 25% of the time or less. But it does provide them several times within an hour, just not every 60 seconds. I have adduplex setup, so I've seen it use pubcenter a few times then drop to adduplex which is always there. Which isn't terrible but isn't great either.

[SimonDarksideJ]

First I've heard of "long running" scenarios that are long enough to cause a problem, but I get your point. We do this under the hood, so it should be an easy task to expose it publicly.

[jkw117]

A quick Question is Smaato supported for Windows 8.1 universal/desktop apps yet? I know it is for phones.

I’ve been trying to get it to work for my windows store app, and there’s 2 confusing parts, in the demo/examples it doesn’t contain any Smaato settings except in the defaultadsettings.xml, like below:

<Smaato AppId="130017033" SecondaryId="1100004086" Probability="100" AdOrder="1"/>

I tried adding

Ads300x250.PlatformAdProviderComponents.Add(AdRotator.Model.AdType.Smaato, typeof(SOMAW81.SomaAdViewer));

where I am adding my other providers, but nothing is coming from Smaato, I implemented a 2nd add with just Smaato and it works. So I wasn't sure if it’s supported yet, or not. As some docs are a little obscure about it.
Also should the pubid be the secondaryID? and adspaceid be the appid?
The docs aren’t clear on that either.

Sent from Windows Mail

From: Simon (Darkside) Jackson
Sent: ‎Wednesday‎, ‎May‎ ‎13‎, ‎2015 ‎1‎:‎51‎ ‎PM
To: Adrotator/AdrotatorV2
Cc: jkw117

First I've heard of "long running" scenarios that are long enough to cause a problem, but I get your point. We do this under the hood, so it should be an easy task to expose it publicly.

—
Reply to this email directly or view it on GitHub.