Is your database ready to take the plunge into analytics?

I just returned from a vacation to the Pacific Northwest.  What a place!  The highlight was a whitewater rafting trip we took on the White Salmon River in Washington.  The trip is scenic and chaotic.  The track of river we ran delivers a steady barrage of class 3-4 rapids and is capped off by dropping over a 14-foot waterfall. The picture below is our raft right before we went over the falls.

One of the raft guides told me that to successfully navigate the falls and to reduce your chances of flipping the raft, you must account for quite a few variables in real-time:

  1. Water Speed (does the raft need more paddling or less?)
  2. Raft speed (must be around 6 mph)
  3. Alignment (raft position must be precise)
  4. Balance (everyone in the raft must lower his or her center of gravity by ‘getting down!’ right before the raft reaches its tipping point)
  5. The Lady of the River (will she be nice to you that day?)

The day we went out, six rafts went over the falls, and one of them flipped.  An 84% success rate is pretty good, but not good enough for the raft guides I spoke with – and especially not good enough for the rafters getting pulled out of 40-degree water.  Unfortunately for the guides, and despite their best efforts, they can’t control all the variables before taking the plunge.  But if a guide could accurately account for all these variables, he could predict what adjustments should be made well in advance of going over the falls and improve his rate of success.

This experience got me thinking about how we are using Marketing Optimization at SAS to successfully predict the best segments of customers and prospects for our marketing campaigns.  But instead of having to account for variables in Mother Nature, we are accounting for variables in our marketing database.

Below is an example list of variables we use to find profitable opportunities, predict the best marketing action, and manage cross-campaign communications.

  1. Person variables:
    1. Job Title
    2. Job Function
    3. Industry
    4. Online behavior
    5. Offline behavior
    6. Recency of response
  2. Company variables:
    1. Physical location
    2. Industry
    3. Sales Revenue
    4. Software installed
    5. Current open sales opportunities
    6. Recency of last invoice

Using information we know about our customers and prospects over time can help us predict performance of segments in our data that are not active with SAS.  How do we do it?  We create models from these variables and apply them to ‘like’ contacts in our database that are not active.  Applying these models, we can accurately identify the best contacts in our database to deliver relevant messages, through the right campaign, at the right time.  Using analytics creates the best opportunity for every campaign list we build to successfully generate revenue.

Speaking of success, in case you were wondering, my raft didn’t flip.  Mother Nature was kind to us and we got lucky.  Take the plunge into analytics and don’t let luck play a role in your database marketing efforts.

tags: analytics, customer analytics, customer intelligence, customer segmentation, database marketing, marketing optimization, predictions

One Comment

  1. Posted December 26, 2011 at 5:37 am | Permalink

    Nice information about database marketing. Its an important part. Many are not using it but it is sometimes a good practice.

One Trackback

  1. By Marketing analytics and why Google matters on January 18, 2013 at 3:05 pm

    [...] of analytical methodologies that drive our decision making (Matt Fulk writes about how we use marketing optimization ). Our goal is to bring all of this rich search and web data into our  marketing analytics [...]

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <p> <pre lang="" line="" escaped=""> <q cite=""> <strike> <strong>