Dapper and ClickZ CPA (Cost Per Acquisition) Calculator

Dapper and ClickZ have put in a simple  CPA (Cost Per Acquisition) Calculator tool which we believe should be an important part of a mobile marketer’s everyday life.

The tool is available here.

We would encourage every marketer to review their CPA for every network they choose, go beyond the hype and actually measure the performance and then choose the right ad network that gives them the best bang for their buck.

If you would like to know our average CPC rates and see how much does it cost to acquire a user on ZestADZ – write to us at sales [at] zestadz.com and we will revert back to you.

ZestADZ Team

Advertisements

Updated Site Install Code with Multiple Ads in a Single Request + Multiple XML Ads

This was on a publisher wish list for quite some time – the ability to get multiple ads from ZestADZ in a single request to speed up their page loading times. This feature has now gone live.

To get multiple ads, go to site install code and select multiple ads. Copy the code and follow the comments to paste different ads in different parts of your mobile site.  

1

 

Getting Multiple Ads as XML

xml_ads_multiYou can directly use the ad request URL of ZestADZ and get ad responses as XML. This is useful for integrating with mobile apps or in some cases mobile sites. We previewed this feature earlier in the blog for a single XML Ad.

Now you can make a similar request and get more than 1 ads i.e. up to 5 ads in a single request as XML. Here is the sample Request URL

http://a.zestadz.com/multiple_ad?ua=NokiaN70/%205.0741.4.0.1%20Series60/2.8%20Profile/MIDP-2.0%20Configuration/CLDC-.1&ip=122.165.32.211&cid=14131C047A50414347574B574153415E8C&recs=5

Parameters

  • recs – this could be a maxiumum of 5
  • response_type – could be text or xml
  • cid – your mobile site or app client id
  • url – URL Encoded url from where the request has been made
  • ua – URL Encoded User Agent string of the phone from where the request has been made
  • ip – the client ip from where the request has been made

Parameters
recs – this could be a maxiumum of 5
response_type – could be text or xml
cid – your mobile site or app client id
url – URL Encoded url from where the request has been made
ua – URL Encoded User Agent string of the phone from where the request has been made
ip – the client ip from where the request has been made

Sample Response

multiple_xml_ads

Please note:

The URL in response – must not be URL Encoded again.

 

 

 

 

 

 

 

 

 

 

 

 

 

We hope that this feature will be useful for you. If there are any questions or comments or issues relating to implementation, please contact us at support [at] zestadz.com

ZestADZ Engineering Team

Announcement: Qeep Partners with ZestADZ for mobile advertising, signs an exclusive deal with ZestADZ.

qeep

Qeep – a fast growing mobile community based in Germany and operating globally, especially in key markets like South Africa, US, India etc today signed an exclusive deal with ZestADZ to monetize their mobile inventory.

Qeep was named amongst the top 20 downloaded apps from the getjar app store in July 2009 – http://www.intomobile.com/2009/08/17/top-20-mobile-apps-from-getjar.html

Qeep and ZestADZ have been working together for the past year and our efforts in better results in monetizing their mobile app inventory has lead to this partnership.

Read the press release here – http://www.gomonews.com/qeep-partners-with-zestadz-for-mobile-advertising-signs-an-exclusive-deal-with-zestadz/

List of Available Ads as XML

We just added a nifty little feature that enables publishers to extract the list of ads as an XML feed. Go to http://www.zestadz.com/static/xml_cpc_feed to read more. Here’s a sample of the generated feed.

<cpc>
<entry>


<countrycode>IN</countrycode>
<operator> </operator>
<manufacturer> </manufacturer>
<min>0.034</min>
<max>0.15</max>
<average>0.15</average>
<currencytype></ currencytype>
</entry>
<entry>
<countrycode>TH</countrycode>
<operator> </operator>
<manufacturer> </manufacturer>
<min>0.03</min>
<max>0.12</max>
<average>0.12</average>
<currencytype></ currencytype>
</entry>
</cpc>