Copy the full src argument of this tag and paste it into the REPLACE_WITH_SCRIPT_SRC above.
(In this case it would be delay.hyperesources/delay_hype_generated_script.js?82237)
Remove or comment out the script tag found in step #2.
This will fully delay the entirety of the ad loading until later.
However, if you’re using an export script, the initial loader and hype runtime will be loaded immediately, and the runtime doesn’t delay in loading external resources. There might need to be changes in the resource loading to support this delay.
Unfortunately those don’t seem to load for me, I assume one needs more access/credentials.
I assume you mean “this does not work?” What issues did you run into? I’m a little surprised, but it does appear that the solution you came up with is basically the same thing, just you are using the flashtalking library.
I was able to get an account (they had some verification issues, but manually were able to get me registered). I tested with your zip and found something odd:
Ah, it looks like that link only works on mobile devices and not desktop browsers. I guess the ad does show up so all is good? I do wonder about the weight difference I’m seeing between yours and mine.
Hi @jonathan, I really like this piece of code. Could we add this with options into the base of Hype for the Banner community? So that with this timeout and politeLoad setting we can bottleneck an initial load to a set value and then after a timeout load the rest fo the banner files/request?
The German Rules of L.E.A.N.:
More Adservers are asking for it and using it. Maybe not Google, but here in Germany there is the OVK (the German IAB, without and https link. Hehe) rule.
I did a visualisation of how I think the options should look like and where to find them inside of Hype.
This is just a suggestion and if the hype community would like to add on this and make it an official feature request, we here would be very happy about it.
I assume you are referring to the code I wrote in the second post of this topic, right?
If this is the only change you need, it could be made today as an Export Script.
To clarify a couple items from your mockup:
Is the Initial-Load field the calculated size of the ad, or is it meant to be the max amount Hype would try to load?
What other options would you expect to see in the Subload popup? DOMContentLoaded and a “normal” option? Or are there other events?
(As a side note, it has been a long standing request to have better loading control over assets, so I am wondering to myself if the document loading could be a part of that effort too to incorporate this type of feature)
This could easily be added with an Export Script to help automate the flow, if you wanted to go that route. The export script examples show how to add code to the start and end of the head and body. If there’s documentation or a spec for your specific requirements I could also help put something together (but it would be unsupported as I can’t make time guarantees to work on it).
Hi @jonathan ,
I also work in Germany and have to consider the initial load/subload of iab for a customer.
Unfortunately, we don't work with flashtalking and the API, "only" with the Google Campaign Manager and the JS framework Greensock.
Can you help us to translate the syntax from above to our workflow?
No no. I already have a DCM redirect clicktag in it. And I upload the ZIP file to the adserver from Google Campaign Manager. It has nothing to do with flashtaking.
I just need help to load images and the JS animation later (subload).