Whatsnexx Community

Google Analytics & Customer State Marketing Automation

A Winning Combination That Allows Etailer To Optimize Banner Ad and Landing Page Effectiveness.

Recently, a new client approached us to help them optimize their online marketing spend. What they want to know is what banner ads are the most effective at generating profitable leads, what landing pages are best at converting those leads into customers, and what is the best messaging strategy to stimulate repeat purchases. We are talking to a sophisticated etailer who is looking to improve the effectiveness of their marketing effort. To date they have been limited by their ability to track this complex combination of variables: banner ad, landing page, and messaging. This project was amazing because it allowed me to provide the Lead and Sales reporting they are looking for through a simple orchestration of the flow of events and actions between an ecommerce site, Google Analytics and Cakemail. (See Dip into the data pool)

This particular customer state marketing ecosystem coordinates the sending of 28 different email communications. There are four customer segments: Prospects; New Customers; Repeat Customers; VIP Customers. Depending on where the contact is in the marketing process they will receive one of these 28 personalized emails according to their ongoing behavior (whether they buy or stop buying for a period of time). One interesting feature is that we are using eight versions of the Reminder email that is sent out when a customer stops buying after a period of time. As soon as they purchase again a Thank You email is sent and the stops buying timer is reset. The Reminder emails start up again according to the contact’s segment and state; however the sequence of emails picks up where it left off, therefore the contact does not receive the same email twice unless they have gone through all eight different Reminder emails. The opportunities for testing are immense!

One of the goals of this ecosystem is to attribute the sale to the last email sent in order to determine the most effective messages for getting contacts to buy. Over time, this information will allow the etailer to improve email content leading to higher sales.

The attribution of the sale to the last email sent is done by the customer state marketing ecosystem and is reported in near-real time using Google Analytics. The client can view the effectiveness of the marketing program in terms of the number of sales, total sales and average sales for specific time periods. This gives them great flexibility to try different email content strategies without the need to rebuild the ecosystem.

The etailer is also testing out various banner ads and landing pages. They wish to know which combination provides the best results in terms of number of sales, average value of sales, and lifetime customer value. The results are easily reported using a simple Excel Power Pivot table, and the etailer can add new banners and landing pages without having to modify the ecosystem (i.e. Involve IT).

Best of all, the entire ecosystem took me a total of three days to design, build and test! Once the client had set up all of their email templates in Cakemail it was a simple process for me to connect them. Ran one final test and put the ecosystem into production.

The real measure of a marketing automation system to me is how fast the marketer’s solution can be built, how flexible the solution is so that it is easily modifiable, and how agile the solution is in terms of integrated marketing in multi-channel environments.

 

 

 

Related articles

Super States: Making the simple even simpler!

Super States: Making the simple even simpler!

Readers of my blog will know that I am always going on about how easy marketing automation is using Customer State Marketing. Hard to believe that it could get even easier, but it is true! The addition of Super States (i.e. a master state) means that it is no longer necessary to include “housekeeping” events in root automation processes. Using email as an example, it was necessary to track if the contact was optin for email when considering how to respond to a customer event (e.g. contact does not open email). Now there is no longer a need to include an Unsubscribe event in all the scenarios where you want to interrupt the process whenever a contact unsubscribes – Instead you now just need to specify a “Subscriber” Super State that encompasses child scenarios. As long as the contact in in the Subscriber Super State the child level processes (i.e. processes that are dependents of the Super State) will execute. As soon as the contact moves out of the Subscriber Super State then all child level processes stop.
As a result the scenarios are a lot less crowded as there is no longer a need to include the “housekeeping” events.

Another benefit of this approach is that it makes reading and understanding the hierarchy of scenarios (remember that a contact can be in a different state in different scenarios) even easier because the housekeeping noise has been removed. It also streamlines the construction and modification of scenarios. Now the longest part of creating Customer State Marketing automation solutions is the documentation of the scenarios (excluding waiting for the customer’s creatives, of course – i.e. It is no longer the bottleneck). This documentation issue will be solved in an upcoming release of the software. I can’t wait for that one because I estimate it will further reduce my workload by half!

Blasting an email four times a year is not a Relationship Marketing Program

Relational marketing (or relationship marketing) is a term many marketers use today to indicate that they send email blasts to their customers. It seems that whenever I meet a new prospect or client and ask them if they do relational marketing they nod their heads, smile and say emphatically “Yes, we group our customers into four segments and send each one of them a personalized message.” If I am foolish enough to follow that question up with “And how do you measure the effectiveness of your program?” I usually get a response such as “We check the open rates” or “Our bounce rate is very low”. Very rarely do I get an answer such as “Our sales rise about 10% in the week that follows each mailing”.

This is the business environment that is being actively targeted by “Marketing Automation” vendors (see my blog Eloqua, Marketo, and Aprimo are not Marketing Automation for my rant on this subject http://whatsnexx.com/2011/02/eloqua-marketo-and-aprimo-are-not-marketing-automation/)

It should not be surprising then that many “Marketing Automation” solutions do not live up to the hype, as many are being used as glorified, and expensive, email marketing systems. It is really hard to generate a very compelling business case with a high ROI when the cost of the software, implementation, training and on-going support accumulate into a significant amount, and the returns or profits derived from the solution are a long way downstream.

The key to a high and rapid ROI: Low investment and fast implementation. A rapid implementation cycle, such as seen when using an Agile Marketing approach, means that costs are relatively low (as long as you can avoid that high priced marketing automation consultant fee) making it easier to generate a high ROI.

So where to start if you fall into the “I blast four times a year category”? The best place is to start with what you are already doing today; however why not turn those punctual campaigns into ongoing programs? For example, if you are currently pulling a list twice a year to blast a reactivation offer to all customers who have not purchased in the last six months, instead automate it so that a reactivation offer is sent whenever someone has not placed an order for six months (i.e. ongoing reactivation program). If you currently blast a “Back to school” offer to all your customers and then wait to see the results at the cash register at the end of the month, instead blast the offer and then automatically send reminders to those contacts who did not open it within three days (note: you should be doing this for all your emailings), and follow that up with an automated survey to anyone who did not open the email at all.

These are simple first steps you can take to graduate from “Batch and blast” automation to “marketing operations” automation.

Good luck.

B2B vs. B2C vs. Customer State Marketing

The B2B sales cycle focuses on the sales funnel: How to nurture and qualify prospects in order to turn them over to Sales at the opportune moment. The rationale for this is that sales reps are an expensive commodity with limited availability. The objective is to have these expensive resources talking to the prospects that are most likely to close. A lot of time and money are spent on achieving this goal. Big dollars are invested in purchasing and implementing marketing automation software, centralizing data, training personnel, creating business rules in the marketing automation platform, and in paying for consultants to implement the more complex and obscure portions of that marketing automation platform.

The B2C sales cycle focuses on the buyer’s journey: detecting what the buyer is doing and determining the context (e.g. is the first purchase, the third complaint this month, the second request for information…) of the buyer’s activity in order to respond in the most appropriate manner . The focus of B2C is on ensuring that the right offer is sent to the right person at the right time using the right channel. This is in contrast to nurturing and turning a qualified lead over to a direct sales representative. B2B marketing automation tools are very poor at B2C implementations because the customer’s journey is non-linear. B2B is designed for a linear sales funnel path from general inquiry to  properly qualified prospect. B2C requires flexibility in order to deal with buyers who move back and forth in what may appear as a random path from awareness to purchase. B2C must continually integrate new sources of information, new channels and new media. This continual integration challenge is why B2B marketing automation platforms have a problem with B2C – it would take too much of their development budget to continually integrate, test and ensure a consistent platform experience to its users. It is also the reason that there are so few affordable B2C marketing automation solutions available.

Customer State Marketing focuses on the context of the customer event/action dynamic. Customer State Marketing allows the marketer to follow each individual customer along their own unique journey. Whether it is a B2B or a B2C journey is immaterial. What counts is the customer’s state at the time of the event. For example, what is the proper response to:

1)      a white paper download event

2)      an abandoned shopping cart event

3)      one week of contact inactivity

The correct answer is “It depends on the context”! If this is the first time the contact downloads the white paper then the response is different than if it is the third time they download a white paper. If the contact abandons a shopping cart the response is different if this is the first cart they have ever abandoned vs. someone who always abandons a cart. If the contact is inactive for one week the response is different if you are sending them a confirmation email vs. a newsletter.

As you can see, the context of the event (i.e. what State the customer is in) determines the correct response. Only Customer State Marketing provides an easy and effective way to build marketing automation scenarios that take the customer’s state into account at the time of the event, whether it be B2B or B2C.

Customer State vs. Decision Trees in marketing automation

Marketing automation solutions allow the marketer to build scenarios that can be simple or complex. For the marketer, the true test of a marketing automation solution is the ease of use when building complex scenarios: how sophisticated can the scenario be before it gets too complicated to understand, to manage and to modify on an on-going basis.

A principle factor contributing to the complexity of marketing automation solutions is the decision tree. Marketing automation solutions offer various graphical and script based workflow tools that are just dressed up decision trees that automate complex multistage decision problems. Below I will be comparing decision trees vs. a customer state approach.

Decision trees

Decision trees such as figure 1 are a useful to for predicting outcome and are often used to map workflows.

Decision trees are also used to do dynamic segmentation. For example all subscribers who are female and click on the Fashion1206 link in the last email sent to them. Decisions are used to determine the proper response according to a particular customer’s micro-segment in respond to an event (e.g. a contact that signed up then click on the confirmation link and then did not open the next three emails that were sent.)

Decisions trees quickly become complex. The human brain is best when tracking 7 or fewer items. Figure 1 shows a multi-level decision tree for a simple process. Imagine trying to build a sophisticated email programs, let alone a cross channel marketing program. Building a complex marketing automation programs often requires dedicated resources in order to ensure consistent rules setting at every level of the decision tree. Unfortunately dedicated resources are something that is in short-supply in most marketing departments.

Customer State

Customer state is a means to map workflow processes according to a customer’s state at the time of a customer event (e.g. signs up for a newsletter). A customer state diagram (figure 2) maps an event / action scenario similar to the decision tree above yet is much simpler to understand. Reading from left to right the scenario is as follows:

1)      Contact

1. When a contact subscribes then send them a confirmation email and move then to an Unconfirmed state

2)      Unconfirmed

1. When the contact clicks on an email ling then if they are a female then send them the Welcome email and refer and friend email else send the Welcome email only. Move the contact to a Subscriber state
2. If the contact does nothing for 3 days then if they are a female then send the Welcome email and refer and friend reminder
3. If they bounce then flag them in the CRM

3)      Subscriber

1. When the contact clicks on the link then send them a targeted promotion.
2. If they refer a friend then send them the Confirmation email promotion
3. If they bounce then flag them in the C

Figure 2

Only events that are relevant (i.e. possible or interesting) to the customer’s state need be considered when describing a scenario.  For example, the only events that need to be considered when the subject is in an Unconfirmed state in Figure 2 are whether they click on a link, do nothing for three days or bounce. Customer state uses a simple event / action paradigm such as “When a customer signs up (event) then Send a confirmation email (action)”.

Since each action/reaction set is according to the contact’s state there are a finite number of events to consider for any given customer state. Rather than building large decision trees that must describe all possible outcomes and are hard to understand, customer state permits the design simple marketing scenario, such as acquisition, conversion, retention. Contacts can be in different states within each scenario. The various simple scenarios can be combined to create a rich marketing ecosystem.

The benefit of this approach is that scenario design is simple and manageable whereas decision tree modeling is constrained by its complexity. Customer state marketing significantly streamlines cross channel marketing program design and implementation. It enables an agile marketing and removes the need for dedicated marketing resources to build the marketing automation workflow.

Conclusion

As I said in the opening of this article, the true test of a marketing automation solution is the ease of use when building complex scenarios. Customer state has the distinct advantage of being easy to understand, is simple to implement, and is significantly faster to market that decision tree-based solutions.

 

One application to rule them all – AKA: Streamlining marketing operations

The small shop

Every Monday morning Frank logs into the CRM system, defines a list of criteria and pulls a series of lists of contacts to send their weekly promotions to. Frank then loads the lists into his email management system (EMS), creates the email templates and then launches each promotion blast. Frank repeats the process for his mobile message blasts. On a monthly basis he does the same thing for customers with birthdays in the coming month. They will receive a special Birthday offer. Four times a year, Frank pulls a list of all customers who have not purchased in the last six months. They will receive a special Reactivation promotion.

The big shop

David is responsible for marketing operations in a mid-sized company. His team manages a variety of applications including a CRM, an EMS, an e-commerce application and a BI application. David spends much of his time creating rules and ensuring that all the rules are consistent from application to application.

Last year David learned the hard way what happens when you forget to synchronize the rules. Suddenly customers were receiving the wrong promotional message because someone forgot to update the CRM rules after they had updated the e-commerce rules. David is worried about what will happen this year when he goes on vacation.

Problem

Frank’s company cannot afford to implement a marketing automation solution. The money is just not available.

David, for years, has been asking his boss to invest in a marketing automation solution to simplify marketing operations. David argues that an integrated solution would be so much easier to use and would avoid costly mistakes and reduce head count (although he will not commit to it until he can assess the impact of the new solution). David’s boss consistently responds that there is no ROI to support the cost and effort involved to implement a marketing automation solution.

The Solution

Both Frank and David need a way to streamline what they do. Frank spends far too much time doing non value-added work such as pulling and loading lists. David’s team spends far too much time replicating rules between various applications.

The answer to their problem is simple: install one application to manage the rules and automate the communications – rules such as pull this list and send this message if the contact is in this state (i.e. meets the selection criteria); or whenever a customer is flagged as a churn candidate by the BI application then send them this mobile message.

What Frank and David need is a customer state marketing application like Whatsnexx. It would allow them to build scenarios that govern the flow of communications to customers and prospects on a one-to-one basis in near real-time. Each scenario contains the business rules that direct the various applications (e.g. CRM, EMS, BI…) to execute the required function when appropriate.

For Frank this means no more pulling lists from one application and loading them into another. For David it means that he only needs to manage one rule set rather than crossing his fingers in the hope that he did not miss a rule in one of the applications.

The solution is simple and elegant: Put all the rules in one application and use it to govern the activities of the other applications. In essence, one application to rule them all!

Marketing Technologists: No programming needed, just Creatives!

In his post Rise of the Marketing Technologist (http://www.chiefmartec.com/2010/04/rise-of-the-marketing-technologist.html), Scott Brinker makes a number of great points that speak directly to my current occupation (all quotes are attributed to Scott’s article).

“...in the big picture of marketing, the real challenge isn't the individual components — it's how these different pieces fit together in your unique enterprise.”

Exactly so! All business activity can be broken down into discrete activities. The challenge is how to orchestrate these activities into a marketing symphony. Some might argue that a great marketer is an individual who can envision marketing strategy, devise programs to attain marketing objectives, execute campaigns that engage the audience and achieve a set number of goals in a measureable fashion. It is the rare marketer who also possesses technology skills.

Scott states that technology choices “open (or close) the door to synergies with your other technology choices.”

Argument for a Marketing Technologist is that a good knowledge of technology is important to a CMO. This is because technological choices have a long tail. They will be in effect a long time and will eventually become a legacy system or a candidate for replacement. As I.T. is responsible for system maintenance and integration issues, both present and future, they are rightly concerned and therefore somewhat rigid in their adoption of new technology. Bad technological choices can create geometric increases in maintenance costs. For this reason new technology must be vetted by I.T. before it can be adopted. This can create significant delays for marketers, marketers who need flexibility and speed to market in order to capitalize on market opportunities.

Marketing and I.T. can often seem at odds with each other. This is primarily due, in my opinion, to a lack of understanding of the requirements of the two disciplines (reliability and costs vs. speed and agility). When there is some understanding, there is often an insufficient depth to properly assess the business impact of current choices vs. speed to market.

“Marketing must take ownership of the technology in its domain.”

Scott refers to the need for a “marketing-technology czar” because “technology becomes one of the vertical pillars of the marketing function”. Whereas I agree with the last of these points, the need to understand the technology is no longer a major issue. I say this because of my own workday reality. I work with a tool that removes to a large extent my concern with technology integration and maintenance issues. My focus is on implementing marketing programs quickly and inexpensively by leveraging whatever marketing technology is readily available to the marketer.

“A CMO doesn't need to have been a Chief Creative Officer, but he or she must know how to manage and lead such resources.”

As Scott points out so succinctly, you just need to connect the dots. I spend my time with marketers asking them what they want to do, how they want to do it, and where is the information coming from. The tool I use allows me to easily connect all the dots, that is to say deal with any customer events and actions. All I do is receive data from a web form, a database, a spreadsheet, an XML ticket or whatever. I don’t really care because all I need to know is that when my marketing scenario receives this data we agree on the name of the event and the fields that will be received.

Once I receive the data all I need to do is execute what the marketer asked me to do, perhaps add the email to the database and send the contact a personalized barcoded coupon. To take these two actions I just have to select a list of actions for the applications the marketer wants to use, say Salesforce and ConstantContact.

I don’t worry about how the technology works. I do not need to master either web forms, Salesforce or ConstantContact. I just need to define the marketing rules and build scenarios such as acquisition, loyalty, reactivation to name just a few. My current reality is that I am usually waiting for the agency to deliver the Creatives. This is a real change from my old life when the client was always waiting on technology.

The freedom that my current design and implementation tool provides me means that marketers are now free to “wield technology as a strategic marketing capability.” I would go further and say to wield emerging apps and digital media as a strategic marketing capability.

It also means that the time to market for a marketing opportunity is now drastically reduced. Unless resources need to be trained in a new technology it is now possible to implement marketing campaigns as quickly as you can generate the content and visuals.

This simple customer state diagram demonstrates what I am talking about. It’s a scenario that governs a loyalty program that makes use of NetSuite and an email marketing system. No programming needed, just Creatives!

Complexity killed marketing automation!

The problem

For marketing automation to really be effective it needs to be wielded by the marketer, not by the marketing automation expert. By expert I mean the consultant who knows how to configure this marketing automation suite or that marketing automation suite. Often, there may be various module experts involved as well. All of that effort, not to mention all of those resources, in order to automate what should be relatively simple marketing processes. As a result, marketing automation calls for a big up-front investment in training and implementation that result in a tough-sell ROI proposition.

The purpose of automation is to simplify and speed up processes   ̶  not complicate things! Marketers need and want a quick and efficient way to automate what are in reality relatively simple processes. The problem is that marketing automation solution providers need to integrate functionality in order to provide a rich cross-channel feature set that competes with the market leader. This is exacerbated by the market leader gobbling up and integrating emerging technology and media channels in order to stay in the lead. The net result is that the “integrated” technology is often more complicated to use than the processes to be automated, leading to a low process automation penetration rate, hence lower ROI.

The end-user needs a simple marketing automation interface if they are going to use it on a regular basis. Ideally the CMO and marketing directors brainstorm strategy and initial tactical scenarios using a design tool. These preliminary designs are then refined by the marketing analyst or admin assistant, depending on the size of the marketing department. The resulting marketing programs and campaigns are further refined and implemented using existing technology. Simple – or at least it should be. Sounds like a dream.

The solution

This is actually much closer to reality than you think! Customer State Marketing offers such a design interface. Due to its simplicity the productivity gains are astonishing, as I have alluded to in many of my blog postings. This got me thinking as to why this is. I think I have narrowed the design benefits of Customer State Marketing down to two components:

1)      Scenarios display the characteristics of object oriented programming

2)      Scenario programming is procedural

For programmers, these two statements are significant. For everyone else this sounds like some foreign language – definitely very obscure…

Let me put it another way:

1)      Scenarios are self-contained. They know how to behave in response to external stimulus (i.e. an event). This stimulus occurs randomly and the scenarios will automatically respond to the event according to the rules contained in the scenario itself. The scenario only knows what it needs to know in order to respond to the stimulus, and contains all of the information necessary in order to carry out its functions properly (i.e. actions), such as sending the appropriate email.

2)      Scenarios follow simple rules, and have a simple program flow and limited branching options. This makes it easy to design state-based event/action program flows that govern how and when a scenario responds to a random customer event.

The benefits

The benefits from combining these two design aspects, object and procedural, accrue when describing and building simple to complex marketing automation ecosystems that govern acquisition, conversion and retention tactics in accordance with a cross-channel strategy.

1)      The object nature of a scenario means that each scenario can stand alone. It does not need to be linked to other scenarios in order to function properly, something that would add complexity. By narrowly focusing on a specific goal, Customer State Marketing scenarios permit the marketer to consider only a limited set of relevant events thereby limiting complexity. This makes it possible to begin small, automate some quick wins, and then gradually build up to a complex Customer State Marketing ecosystem.

2)      The procedural nature of a scenario flow means that it is easy to understand, and similar to simple if/then/else branching that is familiar to non-programmers. As a result very little training is required, and a marketing person can quickly master the design tool. There is no longer the need for marketing automation solution experts and the time and expenses that entails, not to mention the loss of flexibility that occurs whenever you need to translate requirements from one department to another, what I like to call translating from marketing-ese into IT-ese.

Conclusion

These two aspects, object and procedural, of Customer State Marketing are what make it so simple to use and easy to apply in a tangible manner to automate marketing processes. It is such a pleasure to use. I get the best of both worlds, develop solutions in record time, and have yet to confront a marketing automation challenge that Customer State Marketing cannot resolve.

Remember: Simplicity, simplicity, simplicity because complexity killed marketing automation.

Marketing Automation in Frugal Times

Marketing, like most other corporate departments in 2012, is facing significant budgetary restraint, if not to say restriction, as part of corporate focus on cost cutting and the bottom line. The challenge for the marketer is that there is still a crying need to automate marketing processes in order to provide adequate marketing services with fewer staff. 

As big marketing automation budgets become a thing of the past another approach is required – Continual Gradual Automation. This approach starts small and implements quick win scenarios that finance the next step. Over time, it is possible to mash-up an efficient and effective customized marketing automation suite that encompasses database marketing, email, direct mail, social media, analytics, business intelligence, mobile, etc. to influence customer behavior across channels.

Customer State Marketing offers this ability. It allows for the design of independent marketing scenarios that govern the trigger and response behavior that automate various aspects of the marketing process and customer communications. Scenarios such as acquisition, conversion, retention, viral contests, etc. can be combined to build rich marketing ecosystems.

Action features such as sending emails, mobile messages, update databases, etc. are easily added as required. This approach eliminates the need to pay for unused features that are part of an integrated marketing automation suite. Rather, over time, additional channels and actions can be added as needed. The end result is a simple and faster marketing automation implementation eventually leading to a complete set of functions and features that are actually used by the marketing department.

Customer State Marketing is the ideal approach for marketers in lean times. It allows you to start small, win quick, and bootstrap a marketing automation process!

EZ ecommerce scenarios

I was recently asked to produce a Customer State Marketing ecosystem for an online retailer. In less than five minutes I designed a marketing ecosystem that does three things:

1)      Attempts to convert a recently signed up contact to a customer. A cascade of two promotions and reminders sent to the contact, one every 5 days. The promotion and reminder solicitations stop automatically as soon as the contact buys.

2)      Adds to contact to the daily email blast list and then adjusting the frequency of the mailings according to the contact’s open behaviour.

3)       Stimulate the customer to purchase by sending them different promotions 30, 60 and 90 days after their last purchase.

This is an example of a simple Customer State Marketing ecosystem that anyone can build quickly and easily. The three scenarios work together. The coordination of activities is governed by the customer's state at the time of the event.