The publisher sign-up page  http://dev.liquidadx.com/signup

After they complete the form, they will receive a message saying that their account is awaiting approval:

At this point the publisher has submitted a default website and is in the waiting queue to use your Server to make money selling impressions. The admin will receive an email notifying them that a new publisher signed up and is awaiting approval

After a Publisher is approved, they can begin to set up their website domains and ad zones to get their ad tags.

To Add Ad Zones, the publisher must first create a new website domain.

Domains may be auto-approved or may need approval to continue to the next step of ad zone creation depending on the admin auto-approval settings.

In the Website Domain list in the Publisher Dashboard, click Create Zones.

Now enter the information for a new zone on your website page in which you intend to display a banner advertisement

The floor price, is the lowest CPM price the Publisher will accept for their ad zone banner space. If the highest RTB bid or contract bid minus the both the publisher and demand partner markups is lower than the publisher's floor the Publisher's passback ad tags are shown instead. This insures that the Publisher will never lose money by using your Server, and will keep coming back for repeat business.

Now the publisher will need to get the ad tag code to put in their web pages.

The Publisher will need to copy/paste this ad tag snippet out of the text box and into the web page in the div tag where they want to sell the ad.

Normally the Publisher will simply copy/paste this into their blog or web page, or perhaps they will include it in a site-wide header file.

But note that ad networks often times take ad tag code from ad servers like ____ and copy paste it into another Ad Exchange like AppNexus, Lijit, Zedo, Pubmatic and others as passback ad tag code. Or they will IFRAME it within the ad tags of another ad network's demand dashboard and trigger the impressions from websites that were not approved or that they do not own or control ( in order to make a profit from another ad network's inventory by selling it at a higher CPM through your server ). It's up to the admin to determine whether to let that go or whether to moderate the Publisher.

1. First create a new ad zone and change the Auction type from RTB to Header Bidding using the selection box.

2. Add a new Page Header ID which you can associate to 1 or more ad zones that are loaded in the same page. So if you have 3 ad zones in a single page, the 3 will share this page header ID.

3. Next select the Ad Exchange you want to add for header bidding and click "Add". Note that the bidder for your  exchange server is added automatically and you don't need to add it manually.

4. Next fill out the box that appears for the Ad Exchange you want to add header bidding for with your tag ids from the other Ad Exchange's dashboard. Repeat the process for all the Ad Exchanges you want to compete in the auction in your web page for header bidding. Then save the zone. This will trigger the generation of the header bidding Javascript file associated with the ad zone(s).

5. Now in the ad zone viewer, grab the tags for both the Javascript snippet that goes in the header and the snippet for the ad zone as well that goes in the page HTML. Click the "Header Bidding Invocation Code" Link on the right to get the snippets which you must copy/paste. Remember that no matter how many ad zones share the same page header ID, you must only paste it once in the header of the page. The ad zone snippets themselves should be pasted in the page HTML for each occurrence.

6. At this point you should be all set to run header bidding as a publisher.

7. DEBUGGING NOTES: Now load the page and check the Javascript console to make sure that no errors occur. You may want to open the page header Javascript file that was generated and increase the auction timeout at top as needed. It will be generated in /public/headerbid/userid/. The variable to edit is var PREBID_TIMEOUT = 850; You may want to increase it to 1000 or higher if you are experiencing timeouts. Especially if you are testing locally.