motowebmaster Posted September 6, 2016 Report Share Posted September 6, 2016 Hello, It doesn't appear see that Single Page Call hasn't progressed to the point of utilizing it with the async tag, but am willing to fatten-up my javascript a bit in order to improve response time. My single-page call code is simple. I set my variable names with the zone numbers, and then redefine a couple variables if the width is wider than two particular points. Then run the Revive Adserver SPC script, and display my variables within OA_SHOW in three places. The benefit is that I'm doing only one media query per page, and displaying all of proper the ad zones for that page. I'd like to think that sticking with one media query per page is a best practice, and the users could handle a bit more character download in return for a potentially faster experience using the Revive Adserver async tag. Any thoughts? Quote Link to comment Share on other sites More sharing options...
Erik Geurts Posted September 7, 2016 Report Share Posted September 7, 2016 The new asynchronous tags in Revive Adserver have been designed so that when you put 2 or more of them on a single page, they will execute a single bundled request to the ad server. That means you have the advantage of single page call without the disadvantage of a potentially blocking javascript in the head of the page. So in short, async tags already do what you proposed. andrewatfornax 1 Quote Link to comment Share on other sites More sharing options...
motowebmaster Posted September 8, 2016 Author Report Share Posted September 8, 2016 Good to know. So I just do my media query and display the respective async tags? Quote Link to comment Share on other sites More sharing options...
Erik Geurts Posted September 8, 2016 Report Share Posted September 8, 2016 The new async tags completely replace single page call, so both the code in the head (which is gone in its entirety) and the snippets in the body. I don't understand exactly what you mean by media query. Quote Link to comment Share on other sites More sharing options...
motowebmaster Posted September 9, 2016 Author Report Share Posted September 9, 2016 Instead of using: OA_Show(zoneid) I currently use: OA_Show(variable) I assign a variable to each of my five zone ids, then define a couple OA_Show variables, and do a window/width media query. Initially the default is ad sizes accommodate mobile phones. If the width is larger than either 500px or 800px I change a couple of the OA_Show variables to switch to larger ad formats. It is essentially a simplistic way to support my site's responsive layout design. The data-revive-zoneid appears to be the only unique value in any async tag. I guess that is what needs to change dynamically. Quote Link to comment Share on other sites More sharing options...
Erik Geurts Posted September 9, 2016 Report Share Posted September 9, 2016 4 hours ago, motowebmaster said: The data-revive-zoneid appears to be the only unique value in any async tag. I guess that is what needs to change dynamically. Exactly, spot on. Quote Link to comment Share on other sites More sharing options...
motowebmaster Posted September 11, 2016 Author Report Share Posted September 11, 2016 This is more challenging than I realized. My forum script, Xenforo, is responsive but there doesn't seem to be a way to write a template conditional that is linked to a media query. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.