DoubleClick's documentation is very lacking, but they do support Adobe Edge files for banners. You need to zip all your files (there will probably be 6: your .html, several Edge-generated .js files, your "Images" folder, and nad "Includes" folder) into a single .zip archive, and then upload that to DC Studio. DC Studio will unpack all your files, identify the primary .html file, and create the proper paths for your images.
Thanks for your response. We have zipped all the files into a single .zip archive and uploaded it to DC Studio. This is where we have trouble. DC Studio unpacks the files, but what then? If we select the primary html file, and select preview, it only shows an empty window, nothing ever displays. We don't know what to do to get beyond this point.
Hmmm - not really sure why you're having trouble. I can absolutely confirm that zipping and uploading to DC Studio is the correct procedure. I just finished developing a series of 32 banners which were all uploaded this way, with no problems.
Are you first publishing your banner, and then zipping and uploading the files from the "publish" directory? What does your directory structure look like before you zip everything? When DC Studio unpacks your .zip file, do you get a list of all your files - images, .js files, etc.? You mention selecting the .html - my experience has been that DC Studio automatically recognizes the .html file and labels it as the "primary." The next step should be to set up your Background Exits (essentially the same thing as ClickTags, if you are familiar with those.)
Ah, I just realized - maybe you are not including the DC Enabler code in your .html file? That might explain why things aren't working. In case you didn't do this step, this is what you need to do:
Once you have published your Edge banner, open the .html using any text editor, Dreamweaver, whatever. Somewhere inside the <head></head> tags, include the following code:
You also need to have Background Exits in your banner. Each button/hotspot/clickable area should get this code in it's "click" handler:
You can replace 'Background Exit' with any string, I believe. Each unique destination should get it's own Exit label, I just use Background Exit 1, Background Exit 2, etc.
If you are missing the enabler and the background exits, this should solve your problem. Good luck!
Thanks again for the response!
I am zipping and uploading the files from the "publish" directory. I am also including the enabler code in the html file. When the zipped file is uploaded to DC studio, it is not automatically recognizing the .html file or labeling it as "primary". All of the unzipped files are shown, they are all active. If everything is left active, then they will all display at some point, including boxes of nothing but code. If we deselect everything except the .html file and then post it, we just get an empty box.
As for the background exits, I have not done this. I am not sure about how this is done, and it was not included in my guide for building In-page ads. Would this not being done be the problem?
I don't know if not including the background exits would be the cause of your problem. I don't think so, but on the other hand you will need to include them, so you might as well do it and see if it solves the problem for you.
There may be another way, but the way I have done it is to use invisible "hotspots" (rather than <a href> tags) to hold the background exits. So, for each URL in your banner, you will need a hotspot with a unique identifier - i.e. "Background Exit 1","Background Exit 2", etc. Currently, for each URL or button, you probably have some code that looks like this:
Replace that code with:
Enabler.exit('Background Exit 2');
Beyond that, I'm not really sure where your problem lies. It sounds as though you are doing the right thing, but again in my experience once you upload a .zipped archive, DC Studio automatically recognizes the .html file, and identifies the background exits you have included. If adding the background exits doesn't fix things, then clearly something else is wrong - you may need to reach out to DoubleClick support at that point.
I wonder if your zip files is always above 100kb? because of the js files that edge produces? I tried to upload but got this error. Any help appreciated.