Currently Adgine.net supports two methods of content category attachment:
1. Attaching content categories directly to each page through Adgine.net interface
2. Directly at ad site, by inserting tags in page body.
Users may attach content categories to the whole ad site/web-site/web-site directories/pages.
1-st method is suitable for ad sites with distinct page/directory structure. For such kind of ad sites users may set tree-type structure – by choosing “Edit structure” option after ad site is added to the list in the ”Sites” menu. Within the menu users may set site structure taking in account hierarchy of pages and attach content categories. In case advertising site consists of numerous web-sites with complex structure, it is better to use tag insertion mechanism directly at advertising site’s pages.
There are two possible methods of tagging:
1. Tagging the whole page
2. Tagging certain thematic section of the page.
Page tagging is done by means of inserting META-tag named “adgine_categories”. Using attribute “content” network operator specifies categories corresponding to page thematic. Categories need to be separated by commas or any other separating symbol network operator prefers. Here is an example of META-tag for travelling/recreation advertising network:
<meta name=”adgine_categories” content= “France, beachfront vacations”>
In case one page is divided into several thematic sections, or there is no possibility to do content tagging using META-tag, operators may resort to generation of content tag within ad zone code. Currently this operation is performed manually, so after publisher gets ad zone code it needs to be slightly edited. Adgine.net supports unified format of ad zone code in form of JavaScript; automatically generated zone code looks like this:
<script type =”text/javascript”>
adgn_zone= “f2a9def8-6a9a-4ad9-a378-f11d7568ad32”;
</script>
<script type=”text/javascript”
src=”http://invocation.adgine.net/invocationscript.aspx”></script>
First script block contains variable which serves as zone code identifier. In order to insert content tag, publisher needs to insert tag-variable with working name “adgn_categories”. Corresponding content categories are inserted as tag-variable’s value using “,” or another symbol as a separator between categories. Here is an example of zone code with content tagging (highlighted):
<script type=”text/javascript”>
adgn_zone=f2a9def8-6a9a-4ad9-a378-f11d7568ad32”;
adgn_categories=”France, beachfront vacations”;
</script>
<script type =”text/javascript”>
src=”http://invocation.adgine.net/invocationscript.aspx”></script>
Basic rules(applicable to any method of category attachment):
1.If inserted categories are not in English, in order for them to be recognized correctly, META-tag indicating encoding at specific page needs to be placed. Here is an example of such META-tag:<META HTTP-EQUIV=”Content Type”content=”text/html; charset=windows-1251”>
2.Using combined content tags at one page. If content tag is inserted at least in one zone code at the page, it has to be present in other as well.
3.When inserting content tags or linking content categories in “Sites” menu within system interface it is important to take in account content categories’ hierarchy.
Example. Hierarchy of content categories for auto/auto parts advertising network has following tree-type structure:
Vehicles
1. BMV
2. Nissan
3. Ford
Parts
1. Wheels
2. Headlights
If certain page of this networks’ ad site is attached to “Vehicles” category it would mean that advertising zones at the page would rotate profiles’ elements targeted by any vehicle model (in this case BMW, Nissan, Ford)
|