How to Set Up Your Winksite Mobile Site & Community with Google AdSense or Admob Mobile Advertising.

Re: Winksite – Monetize Your Mobile Site with Advertising from Google AdSense or Admob.

GOOGLE: Setting Up Your Mobile Site to Display Ads From Google AdSense

Set-up at Google AdSense

  1. Log into Google AdSense ID at http://www.google.com/adsense and create an account if you do not already have one (can take 1-2 days after submitting your application to Google.)
  2. Click the ‘My Account’ tab near the top.
  3. Scroll down to the bottom of the ‘Account Settings’ page to the ‘Property Information’ section.
  4. Your Google AdSense ID is the alphanumeric code next to ‘AdSense for Mobile’ and typically starts with: ca-mb-pub-

Set-up at Winksite

  1. Enter the Google AdSense into your mobile site’s “Advertising Preferences” page accessible from your Account “Dashboard” or “Edit Site” Main Menu (see Monetize Your Site | Advertising Preferences).
  2. Select “Display Google AdSense Ads”
  3. Select ad position and placement on your site templates/pages.
  4. Hit the “Save” button at the bottom of the set-up form.

ADMOB: Setting Up Your Mobile Site to Display Ads From Admob

Set-up at AdMob

  1. Log into AdMob at http://www.admob.com and create an account if you do not already have one.
  2. Click the ‘My Sites’ tab near the top.
  3. If you have not set up a site for use with AdMob, click ‘Add Site’ and use the address of your site which is: http://winksite.com/username/foldername
  4. On the ‘Manage My Sites’ page, the alphanumeric AdMob Site ID is displayed.

Set-up at Winksite

  1. Enter the AdMob Site ID into your mobile site’s “Advertising Preferences” page accessible from your Account “Dashboard” or “Edit Site” Main Menu (see Monetize Your Site | Advertising Preferences).
  2. Select “Display AdMob Ads”
  3. Select ad position and placement on your site templates/pages.
  4. Hit the “Save” button at the bottom of the set-up form.

Note: For either Ad Network option you do not need to insert any code on your Winksite mobile site. You ONLY need your Google AdSense ID or your AdMob Site ID.

Winksite – Monetize Your Mobile Site with Advertising from Google AdSense or Admob.

Winksite drives a lot of mobile pages views. Over the years, most every ad network on the planet has approached Winksite about monetizing our mobile traffic. We always played with the idea of signing up, but we don’t view Winksite’s traffic as “ours” alone. As we see it, publishers who trust their content and communities to Winksite’s care provide Winksite with great value just by showing up. The traffic and impressions are mostly there because of the efforts of our 25 thousand publishers and the audience they attract.

We can’t unilaterally profit from that traffic like the other feed mobilizers and site building tools. They have it wrong and are ripping off the publishers. At best their share of the revenue share is too high — at worst — they take it all.

It took a while for us to figure out the obvious — make it drop dead simple for a publisher to insert either Google Mobile AdSense or AdMobs ads into their mobilized feeds, mobile Websites, and communities at Winksite — and take NO revenue share.

All a publisher needs do is:

  1. Register and create a mobile site.
  2. Enter their Google AdSense ID or AdMob Site ID.
  3. Select ad position and placement on their site templates.

What would you like next?

Tutorials for Creating a Mobile Website at Winksite

Thank you Nik for putting together some great tutorials on how to use Winksite.

Creating a mobile phone website by Nik Peachey

Here’s a movie showing what my site should look like on a mobile phone.
Winksite demo

Here’s another movie showing how to create your own site
Tutorial movie 1

An this movie shows how you edit and change the site
Tutorial movie 2

You can try the live site on your PC
Interact with the live Winksite

Sign Up to build your mobile Website.

Integral by the Pet Shop Boys – QR Codes & Campaigning Against the Erosion of Our Personal Freedom

For all of you who dig QR Codes this is for you.
(Scott forgive me.)

Watch the Pet Shop Boys Video in Wide Format: http://www.petshopboys.co.uk/splash.html

The video sets out to amplify the message of the song. The piece was conceived and created by The Rumpus Room as a multi platform project, having versions of the film for small hand held devices as well as large resolution screens. It is both a traditional piece of film and an interactive portal to online information and campaigns.

The video has over 100 QR Codes that are subliminal when watched in real time, but accessible to interact with if you navigate through the film using time controllers. The QR Code links in the video are a catalogue of online content about issues of civil liberties, as well as links that will give you the opportunity to get involved in campaigning against the erosion of our personal freedom.

I think we found our theme song for MobileCamps.

Yahoo! Are You Listening?

Dear Yahoo!

When will you honor the request for our domain to be placed on the Yahoo! oneSearch service “White List”?

When will Yahoo!’s oneSearch service respect the “Cache-Control” of “no-transform”?

When will Yahoo! provide transparency to the oneSearch implementation of this Novarra transcoding madness so everyone who needs to can OPT OUT?

(Note: We also have rel=”alternate” media=”handheld” implemented as Google suggests.)

If this is news to you…

I refer you to, “The New Walled Garden?

Sorting out an off-portal publishing system to deliver mobile device-specific 100% W3C mobileOK and .mobi standards-compliant templates was apparently not enough. Now it seems I have to take on everyone in the world who is bastardizing us with their freaking Novarra “web transformation” engines and poor customer service (i.e. whitelisting.)

and…

Yahoo!’s oneSearch service clearly distinguishes mobile and web results. They are returning both PC and desktop links to Winksite. Links in the PC section goes to the transcoder, while links in the Mobile Web section goes direct.

So why do I have a problem with this? Let me explain…

When someone visits Winksite or a mobile site published at Winksite we send that visitor to a version appropriate to their device. We asked to be White Listed because a mobile phone should never end up at a transcoded version of our broadband site. If Yahoo! respected that ALL the links in the results would pass to us directly where we could then do the job that people count on us to do.

Instead our routing is intercepted and adapted content NOT our content or the content of our publishers as it was intended to be distributed is sent. This cripples our site and renders our community features unusable.

I question Yahoo!’s (and anyone else’s) right to do that…

…and without permission to create a derivative work that violates our copyright AND hinders our ability to provide a service that took years of hard work to build.

Cheers,
David Harper
Founder, Winksite

The New Walled Garden?

It’s getting even worse for mobile developers and content providers.

Now it’s Yahoo!/Novarra. Who else?

Novarra to Provide Mobile Web Tranformation Services to Yahoo!

Chicago, IL USA – July 24, 2007 – Novarra, the leading provider of next-generation mobile Internet platforms and services, announced today that Yahoo! has selected Novarra’s Vision™ server version 6.5 platform to provide web transformation for Yahoo!’s oneSearch service. When a user clicks on a link to a Web site in a Yahoo! oneSearch result, Novarra’s Vision server platform transforms the Web site for the mobile phone.

We decided to check up on what was happening to Winksite.

This is the result…

Yahoo!’s oneSearch/Novarra is providing mobile device search results that link to transcoded versions of our broadband web site rather then linking to our mobile version.

This is after requesting that our domain be placed on the oneSearch White List MONTHS AGO and submitting three of our sitemaps for indexing – broadband site, WML, & XHTML.

WTF.

I have a responsibility to 25K plus publishers who trust their mobile sites to our care to do everything I can to see to it that their content makes it through to their audience.

Sorting out an off-portal publishing system to deliver mobile device-specific 100% W3C mobileOK and .mobi standards-compliant templates was apparently not enough. Now it seems I have to take on everyone in the world who is bastardizing us with their freaking Novarra “web transformation” engines and poor customer service (i.e. whitelisting.)

Is there a reason why mobile developers and content providers have to jump through so many hoops and fight so many battles in order to reach their viewers in a manner equal to how the broadband Internet operates everyday?

Is anyone listening?

CLARIFICATION:
Yahoo!’s oneSearch service clearly distinguishes mobile and web results. They are returning both PC and desktop links to Winksite. Links in the PC section goes to the transcoder, while links in the Mobile Web section goes direct.

So why do I have a problem with this? Let me explain…

When someone visits Winksite or a mobile site published at Winksite we send that visitor to a version appropriate to their device. We asked to be White Listed because a mobile phone should never end up at a transcoded version of our broadband site. If Yahoo! respected that ALL the links in the results would pass to us directly where we could then do the job that people count on us to do.

Instead our routing is intercepted and adapted content NOT our content or the content of our publishers as it was intended to be distributed is sent. This cripples our site and renders our community features unusable.

I question Yahoo!’s (and anyone else’s) right to do that…

…and without permission to create a derivative work that violates our copyright AND hinders our ability to provide a service that took years of hard work to build.

Save the Moble Web from Vodafone. Actions to Take.

Dennis from Wap Review has pointed out several actions to take if you are against the actions of Vodafone in his post, “Vodafone’s Heavy-Handed Transcoder.”

From Wap Review:

This is a serious issue. Vodafone is clearly wrong. As defined by the W3C, the purpose of the User-Agent header is to identify the originating browser. More importantly Vodafone is breaking a long established de-facto standard in mobile-web development that the User-Agent is the best way to identify a particular handset for the purpose of optimizing content delivery. Vodafone is breaking the mobile web. As the second largest mobile carrier in the world they have enormous power and are setting a dangerous precedent. If you are a mobile developer or user who wants to see quality content please let your voice be heard.

Things you can do:

  • Send an email of support to Luca (passani at eunet dot no).
  • Let Vodafone know what you think by leaving a comment on their message board.
  • If you have a blog, raise this issue and link to Luca’s statement.

We need to create a ruckus and use the publicity to get Vodafone to change their behavior. The proxy should not change the User-Agent and it should not be the default. Voda needs to give their users the real mobile web, unfiltered and un-transformed. The proxy should be an option to be invoked by the user only if and went it’s needed.

Vodafone UK is Clearly Wrong – The User-Agent String Issue

UPDATE:
Nigel Choi has kindly invested his last weekend to provide the community with evidence of how the Novarra/Vodafone transcoding service disrupts the mobile experience:
http://wurfl.sourceforge.net/vodafonerant/vodawsj/nigel.html
————

For several weeks a firestorm has been taking place at Vodafone’s Developer Forum (Betavine, Mobile Internet Content Adaptation forum)

Simply put…

Vodafone UK started striping out essential device identification information that mobile phones send to content providers (i.e. the User-Agent String.)

The User-Agent String is used by developers and content providers to deliver mobile-optimized sites OR device-optimized content/services.

Vodafone’s actions thwart the efforts of companies in the mobile ecosystem who set out to provide a customized mobile presentation of their services, hurt these companies financially, and is counter to the advancements facilitated by groups such as the W3C and dotMobi.

For a distilled explanation of the Vodafone User-Agent string issue and how it affects the mobile Web please visit “Vodafone UK is abusing its position” by Luca Passani.

Mike Butcher over at Techcrunch UK has picked up on the story.

Luca Passani:

I am irritated with Vodafone. More that that. I am furious. I see an abuse and I am not sure what to do about it. But it’s an abuse. A Big one. Perpetrated by a large company in a dominant position against a myriad of small companies and against its own customers. An abuse that is damaging a whole industry in its infancy. I am talking about the industry of the mobile internet. I am talking about the possibilities for existing and new companies to have a new channel for selling content and services to consumers, and about a company which, from one day to the next, decides to pull the plug on the infrastructure that made this possible. The plug is pulled because this decision makes some tiny extra business sense for the big abusive company here and now, but it has no legitimacy whatsever, and the reason why the big abusive company can do it is merely technological: they manage the pipe the brings the data from the service provider to the consumer, and they decided to exploit this possibility to cut everyone else out.

Is this legal? I don’t know. Probably not. The problem is that, being this a relatively new field, there are no specific established regulations which spell out clearly what companies can or cannot do. By exploiting this uncertainty, the big abusive company is applying its dirty tricks and hoping to get away with it.

The abusive company I am talking about is Vodafone UK and the abuse is their decision to strip out essential device identification information that mobile phones send to content providers in order to let them serve customized content for each user’s device.

I want to bring the problem to public attention, make people aware of the issue and get everyone involved to do something about it. Read on…

HP 's The Digital Mindset Blog – So How Important Is Mobile For Social Marketing?

HP asks, “So how important is mobile for social marketing?”

HP then answer’s their own question, “In short, very.”

I have to agree.

HP’s The Digital Mindset Blog::

  • John Hadl, whom Brandweek called “the father of mobile marketing” and a top 10 Next Generation Marketer, predicts that in a couple of years mobile phones will be the “premier consumer connection and medium for insights available for marketers.”
  • Julie Ask of Jupiter Research makes the case that mobile has already become a natural and increasingly important complement to social marketing campaigns. She provides a list of seven best practices for marketers to keep in mind when creating mobile social marketing campaigns.
  • In his keynote at Mplanet 2006, AT&T’s COO Randall Stephenson, said that of the three vehicles AT&T has to reach customers in their new Three Screen Initiative (internet/PC, TV, wireless/mobile phone), wireless is the most important.
  • Wireless Week’s Brad Smith suggests mobile advertising may be poised to explode next year.
  • Tomi Ahonen calculated that in 2006 mobile social networking was already worth $3.45 billion. In Ahonen’s view, “if you are not on mobile, you won’t be relevant soon.”
  • Mmetric recently reported that 12.3 million consumers in the United States and Western Europe accessed a social networking site with their mobile device in June. And this was prior to the launch of the iPhone.

Note: Winksite is mentioned in the post as an example of a mobile web 2.0 mashup, where web content is automatically repurposed for mobile consumption making it “almost trivial to mobilize one’s blog.”

Ashley Tisdale's On The Mobile Web – Or – How What I Do For A Living Finally Impressed My Gradeschooler

Thanks Ashley (& Warner). With the popularity of “High School Musical 1 & 2” and, “The Suite Life of Zack and Cody” in my household a Winksite for Ashley provided me with some extra respect at the dinner table this evening.

…and required that I post this “News” to my blog. 🙂

AshleyMusic.com: Ashley’s on the mobile web!

You can now keep in touch with Ashley and connect directly from your cell phone! Log on with your cell phone web browser to mobile.ashleymusic.com.

Get mobile updates from Ashley such as, diary entries, photos, news, and more! Also, you can chat with other fans and post on the message board. With this new mobile site, you can check in with Ashley no matter where you are!

Bookmark the URL into your phone and keep checking back! Log on to the mobile web at mobile.ashleymusic.com for more.

Related Post(s):
Warner Launches Mobile Portal For The Veronicas – Mash-Up Of Branded Content With Social Media