Quantcast StorefrontBacktalk » Blog Archive » McDonald’s Mobile Trial Raises Question: Who Owns The Data?
advertisement
advertisement

McDonald’s Mobile Trial Raises Question: Who Owns The Data?

Written by Evan Schuman
April 9th, 2008
Like this story? Share it
To share this story with people in your social network, please click on the network icons below.

A group of 109 McDonald’s restaurants in the Salt Lake City region are doing a mobile commerce trial, with participating consumers getting free iced coffee. Although those 109 stores are barely one coffee bean’s worth, given the $22.8 billion chain’s 31,377-store network, the trial is interesting both for its capabilities and for how much data-control McDonald’s was willing to give up.

The trial started April 7 and is scheduled to run until April 27, with McDonald’s in parts of Colorado, Nevada, Utah, Wyoming, Nebraska and Arizona. But the area is really considered to be Salt Lake City and its surrounding communities, said Paul Barrera, the McDonald’s marketing manager responsible for the Rocky Mountain region.

McDonald’s is working with a mobile coupon and discount firm called Cellfire. The San Jose-based company offers the mobile service free to consumers.

McDonald’s is launching iced coffee as part of some new menu options and "part of our objective was to create additional awareness," Barrera said, especially among the younger consumers that McDonald’s assumes will be receptive to a mobile coupon campaign. "The key thing is for us to say, ‘Let’s see how many young adults will know about this product.’ The goal really was to get them to try the product," he said.

Cellfire told McDonald’s it has 4,000 subscribers in the Salt Lake City region and that would be the extent of the campaign’s reach, Barrera said.

Such campaigns can work both ways, of course, with the McDonald’s publicity giving consumers a reason to subscribe to the cellphone service.

The way the coupon redemption is supposed to work is that a subscriber sees the latest offers—including this one from McDonald’s—and signs up. A text message gives them the coupon. When they go into the restaurant to redeem it, they show the phone’s screen (displaying a barcode and a number) to the cashier, who selects a preprogrammed POS button for the free coffee.

The McDonald’s employee does not write anything down. This makes it easier for employees and places the data-retention burden on Cellfire.

One of the customizable aspects of this kind of program is expiration date and limits. McDonald’s chose, for example, to allow consumers to use the coupon as many as three times. "That means we can tell [our customers, in this case McDonald's] how many [people] redeemed it once or twice or even three times," said Dwight Moore, Cellfire’s vice president of Corporate Marketing.

Moore said that part of the benefit of using a firm like Cellfire is that it knows a lot about the consumer customers, who sign up revealing their phone number, age, gender and the ZIP code they live in. For privacy concern purposes, Moore said, Cellfire keeps that data in aggregate, to maintain a little bit of anonymity. "We know people’s phone numbers but we don’t know their names," he said.

Getting someone’s name when you already know their cellphone number is usually not too tricky, but we won’t go there. Generally, there isn’t much reason to know consumers’ names as long as you know their habits. Retailers want to reach people who tend to buy certain things and attend certain events. Their names are not merely private: They’re usually quite irrelevant and unnecessary.

But the McDonald’s Salt Lake City mobile trial is interesting because of a different data issue: Control. And it’s an issue that retailers will need to figure out as they experiment more with mobile commerce.

On the one hand, there are some major advantages to McDonald’s in letting the data sit with a company like Cellfire. There are the training savings, because McDonald’s employees have to push just one button. And the company instantly knows how many iced coffees are being given away, which is much of what it really wants to know.

And if McDonald’s wants to know more—such as a demographic analysis of who specifically redeemed the mobile coupons (90 percent female, for example, or 87 percent between the ages of 17 and 23 or 56 percent from ZIP codes 84101 and 84158)— the company can simply ask and be told.

Then there’s the downside of control. If a customer, McDonald’s for example, wanted to take some additional action—such as "Next month, send another coupon just to the 856 customers who used the iced coffee coupon two or three times and offer them a free salad and let’s see what happens"—that customer presumably would be locked into using the same service provider.

There’s an even more frightening retail scenario. Companies like Cellfire certainly start with a modest amount of customer-volunteered data (such as phone number, age, gender and ZIP code), but their customer database grows quickly as they do various advertiser trials. Because they own all of that data, they can provide more sophisticated services to clients as time goes by. That’s a good thing.

But what happens when a rival gets interested? Let’s consider this McDonald’s iced coffee trial. One of the companies that McDonald’s is aiming at with this iced coffee testing is clearly Starbucks. What happens if, a week after the trial ends, Starbucks approaches Cellfire and says that now it wants to do a mobile trial?

What if Starbucks asks Cellfire to send an offer of free cappuccinos to any Cellfire customer who has previously responded to any coffee promotions? This starts to get interesting. Cellfire can’t betray the confidence of any customer, but all information is owned by the company and it clearly has a right to use the knowledge of its customers’ habits for its advertisers.

If Cellfire did that, in a sense, McDonald’s would have subsidized marketing research for its arch enemy. (I won’t lie to you. That pun was intended.)

It’s simply one of the downsides of allowing a partner to own marketing—and ultimately CRM—data from your trials. That data, which you paid for, could easily aid your direct rival.


advertisement

2 Comments | Read McDonald’s Mobile Trial Raises Question: Who Owns The Data?

  1. Great Internet Branding Says:

    This is a great article that addresses some key concerns with mobile marketing…I do think however McDonalds is wise to continue down this path in order to build some mobile and internet marketing for the company..

  2. Aiding the Competitive Enemy Says:

    Why on earth would McDonald’s allow their customer data to be owned by a vendor???

    That vendor then, at their discretion, can sell, abuse, re-use for illicit purposes that MacDonald’s customer. Don’t think for a second that the customer won’t belive it wasn’t McDonalds that violated them- not the vendor. Bad move McDonalds.

Leave a Reply

Newsletter

Quickly catch-up on the latest in E-Commerce and Retail Tech with our free weekly newsletter, with urgent bulletins as news merits.
advertisement

Most Recent Comments

What’s The Rush For New PCI Call Center Requirements?

And I have not heard anyone mention the impact on companies who provide quality improvement services. Many merchants hire quality improvement companies to review their audio recordings to provide guidance on how to improve their sales staff’s effectiveness in customer service and sales retention. PCI Council needs to rethink this requirement until there is a widely available commercially viable solution. Read more...
Another ridiculous decision where regulators don't think critically enough about the unintended consequences of their decision. This will be a huge problem for the credit and collections industry. We have to keep all recorded calls for other reasons not related to cc information. We can't purge all of our calls and we don't have the technology to not record part of the conversation. Even if we did, I am not sure we could afford it. Read more...
This "clarification" is causing a lot of panic with large FS clients who now appear to be non-compliant after spending 7 figure sums on their compliance programs. The only alternative to call recording would now appear to be some sort of IVR/push button type interrupt to take card data away from the contact centre. The council is a position to force that sort of process and technology change and this may backfire on them and the vendors that lobbied hard for this clarification. Read more...
PCI council has made a one-sided decision; They should have done a much more in-depth research that could have provided more insight on what regards to the implications of such decision. Read more...

Will Old OS Cause PCI Violation? No, But Marketing Still Says So

This is an interesting issue, because there's more to it than what's apparent on the surface. PA-DSS requires supported and patched operating systems and other software components (e.g., databases, libraries, Java, etc.) per PA-DSS 7.1.b and 8.1, and the option for compensating controls simply isn't there. Merchants can make use of compensating controls for most PCI DSS requirements, but only when legitimate constraints exist and only in ways that meet the intent and rigor of the requirement and go above and beyond the other PCI DSS requirements. Read more...
Why would one automatically upgrade to a "new" OS -- some of the older versions of certain OS-es are more stable and more robust than the crap being peddled today. This is yet another clear example of PCI SSC being out of touch with reality. Rather than requiring a "current" OS, the requirement should be to demonstrate the OS in use is stable and robust, and is adequately hardened against threats. Read more...
There are compensating controls that encrypt the swipe at the driver level as it enter the PC, there are hardware encrypting card swipes so the cardholder data is already encrypted before it comes to the PC -- either of these, especially the second, would remove the OS entirely from a cardholder data risk profile. Read more...
In my opinion, the only thing the vendor did wrong was they didn’t know of that FAQ entry. Even if they did, it changes nothing about the need for merchants to update software that no longer receives updates. Read more...

MasterCard Blinks, Drops Dec. 31 Level 2 PCI Deadline

Reciprocity between MasterCard and Visa was always been a factor in Acquirer merchant level assignments. The brief removal of reciprocity generated a great deal of interest in being able to be classified at a lower level in MasterCard's world. Nevertheless the return of the reciprocity language in the December changes did not effectively create any new Level 2 merchants, but it DID dash the hopes of a lot of them.... :-( Read more...
Let's given them credit??? For being idiotic in the first place? Not on your life! Everyone has just had to scramble and include the costs of the previously announced M/C requirement in their 2010 budgets, and start negotiating with the QSAs for the additional services. All for naught! Read more...
"A bunch of Level 3 and Level 4 merchants just became Level 2s". Is this an accurate statement? MasterCard & Visa have historically included the caveat "or is a Level X in another brand" in their level setting criteria. MasterCard appeared to back way from this in the June pronouncement, and have simply returned to the status quo. Have Acquirers have been tracking and reporting merchants at separate levels by brand? Read more...
I stick by my comment (quoted in the column) about a bunch of L3 and L4 merchants becoming L2s and requiring an onsite. To me, what made MasterCard's original requirement for an onsite assessment for L2s palatable was that they took away their reciprocity provision. That is, they seemed to focus on larger merchants with over a million MasterCard trans/year. With reciprocity in place, a lot of smaller merchants are pulled into the onsite requirement. Rather than causing confusion, I think reciprocity will lead to additional work for processors and acquirers. Read more...

Retailers Sue POS Vendor, Questions Raised Where PCI Duties Stop

I would add a couple more questions: "did the breach involve the use of the default passwords?" (The story doesn't say.) And "were the default passwords used by Computer World to remotely administer the store systems?" "where is the PCI auditor in all this?" Did the restaurant group think they didn't need an audit because Radiant was (mis)representing Aloha as PCI compliant? How is a retailer or even a PCI auditor to know otherwise? A PCI auditor is not necessarily a qualified computer forensic investigator capable of finding the card data on the hard drives. They can only base a decision on information given to them by others. Read more...
There are so many holes in the process it will be difficult to pin blame on just one constituent. It is ridiculous that the technology exists to better secure these transactions (PIN, EMV, etc) yet banks won't use them. Only the banks or government can force this change, and retailers will suffer until then. Read more...
A major issue in this case will be if the restaurants had any support agreements in place with Computer World and if so what those agreements say. In my experience many single unit/small operators choose to skip the support agreements in favor of a "pay as you go" arrangement. In this scenario I can't imagine how the POS VAR can be held responsible for a system they don't own nor exclusively manage. Read more...
There is a big difference in having the POS installation guide say "make sure you set this password because the security of your CHD depends on this" vs. a POS application not storing the CHD in the first place. Traditionally only the merchant was liable for breaches and PCI related fees (fines). Maybe dragging some of the vendors into the liability mud fight will open the eyes of some of these vendors. Read more...

Should Credit Card Transactions Be Free? There May Be A Way

Here in the Netherlands, where the population is notoriously penny-pinching, credit card acceptance is amazingly low. It's both a result of the consumer not wanting to pay interest on everyday purchases as well as merchants not giving up a slice of the action. It is both legal and common to pass the processing fee onto the customer as a surcharge. Now things are moving to leave the credit cards behind: mobile phone payments are becoming more and more common here, and the transaction fees are minimal. Parking and entertainment (movie/concert tickets, nightclubs) have been amongst the first, and it's rapidly gaining momentum because the market has been hungry for the convenience at a price it is willing to pay. Read more...
"Free" is an illusion. Don't charge one person but charge double to someone else. I am very skeptical on anyone who says that advertising will create valid cashflow. Just look at the advertising struggles in a TiVo world. And if you sell your customers data, just be warned that the one group that might have issue with that are you customers (which to me is very important to cashflow. Read more...
Another factor not mentioned here is the impending costs that the processors and issuers are going to incur when someone decides on an end-to-end encryption method, and it then becomes government mandated. I can guarantee that this is a when question and not an if question. The back-end networks are pretty antiquated right now, and it's going to cost billions to replace everything. The cost of tech may be going down, but the cost of replacing millions of servers and hardware, and creating new, proprietary, software is still really expensive. Read more...
Accepting credit cards are not "risk-free" for merchants, contrary to Jim's comments above. Chargebacks are an expense - both in terms of actual transaction reversals and costs associated with managing the process. Chargeback rules and expenses can be everything from a thorny issue to an onerous expense for some merchants, especially for convenience stores that allow customers to pay for gasoline at the pump, or other retailers that allow in-store self-checkout options. Read more...
I've wondered for years why the price of transactions has been so high. Phone companies long ago started offering unlimited calling for flat rates because they understood that in many cases it cost more to report on the transactions (calls) than it did to fulfill them. Read more...
If a home-owner defaults on the mortgage, who is taking the risk? The bank making the loan to the consumer or the person selling the house? It is obviously the bank that takes this risk and is rewarded for that risk through interest rate charges. In my mind, we have mixed together two distinct and unrelated transactions. Read more...
The one big factor not mentioned in this article is who will take over the risk ? Taking credit cards is risk free to merchants and the issuing Banks take the risk if a customer defaults on the payments ! If you had a "interchange free" payment system will the merchants assume the risk ? Also, if there isn't enough profit for the issuing banks they will stop issuing credit cards which will in turn kill our economy. Read more...

The Dangerous Out-Of-Scope PCI Charade

If tokens are ever deemed in-scope, then where does the line stop? I ask this because it would mean that all timestamps, sequential number, random numbers or any other piece of information that may or may not be used to generate a token is within scope -- all data a POS uses and stores, not just payment data. Read more...
Having the ability to do both Tokenization and End to End Encryption (not mere point to point) can have tremendous scope and risk reduction benefits and agility to adapt to change in this fast moving compliance landscape. Being able to have both on tap from a single platform is a solid approach to avoiding the pitfalls. Read more...
But the consumer walks into a particular retail chain, gives their payment card to someone wearing that chain's uniform and the card is swiped. If, six months later, there's a breach and that card was misused, it's the retailer who will in the spotlight. They're the deep pocket and, therefore, the target. If the consumer is angry and wants to cut off business, it will hit the retailer. Therefore, if the retailer is going to end up being blamed no matter what, they have to stay involved. Read more...
True, that someone may be storing a token-to-PAN cross reference. But that would be the bank, not the retailer. If the bank is not sure they can keep their data secure, then there are bigger problems to be addressed than bringing tokens into scope. Read more...
Good general point, Steve, but for the record, not all tokenization is done the same way. Many tokens are associated with lookup lists that allow for them to re-matched to the card data if it's needed, such as for a chargeback. A token doesn't have to be decryptable (is that a word?) for there to be a way to access the original data. Read more...
The out-of-scope argument is very valid but in reference to tokens, the premise of temporarily out-of-scope or abruptly deemed in-scope is flawed. Conway was quoted “anything that could be made unreadable can, in various ways, be made readable again,” this statement is true when talking about encryption technologies (all encryption technologies) but not so with true tokens. True tokens are in no way related to the original data other than as a reference key. Read more...