SET UP YOUR MARBIL ADVERTISING ENVIRONMENT

The JS tag integration is mostly copy/paste into your HTML but does contain some configurable items. Example tag (note the serviceKey used below is a testbroadcaster that can be used temporarily if you have not received a specific key yet):

For example: to get this advert:

Add this to your page Details:
1. The marbilAds.js script can be included anywhere on the page. It should only be included once in the case of multiple adverts.
2. Include the getBroadcasterAdvert function call in your HTML wherever you want an advert to appear. This can be called multiple times per page where required.
3. getBroadcasterAdvert parameters (serviceKey,width,height,clientRef)

1. serviceKey: This is a GUID key that is linked to your broadcaster/publisher. Adverts are loaded onto specific broadcasters, so you will likely have several different serviceKeys to use throughout the site.
2. This is the width reserved on the page for the advert. This would be agreed upon in advance and broadcasters configured to only support the relevant width.
3. Height: This is the width reserved on the page for the advert. This would be agreed upon in advance and broadcasters configured to only support the relevant height.
4. clientRef: This is a unique reference to the user.

The broadcaster can integrate with Marbil by a simple HTTP GET request call. The URL required is: http://service.marbil24.co.za/services/marbil_advert.aspx

The URL will respond by returning the entire HTML content of an image advert. All the broadcaster would be required to do is call the URL and print out the response where the advert is required to display. At this time this integration method only returns the advert in one format (ideal for a banner ad). In future releases some further flexibility will be added to cater for other commonly used advert formats, which will be accessible by sending an additional parameter.

Most basic request format:

This request URL should be appended with the same parameters as used in the web service call. If the parameter is marked as optional, it does not need to be sent.

Key	Required. The serviceKey defines your broadcaster/publisher to the backend. Adverts and types of adverts are configured directly to this key. The key replaces the old username/password type.
ClientRef	Suggested. A unique reference to the user of your site. Preferably the MSISDN of logged in user if available.
ClientContext	Suggested. A reference to the page or site requesting the advert. Currently used for statistical analysis only.
ClientUserAgent	Suggested. Broadcaster should send the client User-Agent header to support device specific profiling.
ClientIPAddress	Suggested. The IP address of the user.
SpecialResponse	Optional. The SpecialResponse parameter can be used when custom ad formats are required. This would be created in an offline process where specific HTML templates can be agreed on for the project. This could come hand in hand with extra parameters, but this would be handled on a requirement to requirement basis.