Wednesday, May 16, 2012
"Ron Johnson - JcPenny CEO has done incalculable damage"
http://news.yahoo.com/j-c-penneys-shares-free-fall-1q-loss-213919061--finance.html
- Candice M. Narvaez
Wednesday, January 25, 2012
Random Rant: JcPennys adopt Walmart Pricing Strategy
JCPenny is adopting a pricing model like that of Walmart. My thoughts: JCPenny, despite the name, isn't a penny, nickle and dime retailer like Walmart, it is in the business of FASHION apparel. Walmart's everyday low pricing works for them because I have to shop for basic necessities everyday! I do not have to shop for fashionable items as often as I may need to purchase milk. Walmart's goods represent our ever day needs. A NEED to purchase in the fashion industry is created by a sense of URGENCY...that sense of urgency is created by deep discount sales not EVERYDAY low prices. Bad move JcPenny, bad move...
Thoughts?
- Candice M. Narvaez
Friday, January 6, 2012
Leverage Unica Campaign as a QA Tool!
Any data warehouse is developed and managed on a set of business rules that are built into ETL jobs to process data. The data integrity depends largely upon conformity to these rules. While there are exceptions to rules, thresholds are created to establish the degree of acceptable error. These thresholds should be monitored regularly by automated integrity checks as part of a complete quality assurance process.
Database marketing applications are largely at the mercy of these database side quality assurance processes. Many read database tables at face value and depend upon the integrity of the data, rendering these tools vulnerable to data issues. However, IBM’s Unica Campaign can be used as a kind of last line of defense. While the tool itself cannot repair data issues, it can proactively capture and mitigate these issues. Below is a list of business cases and steps to alleviate the impact of potential data issues.
Business Cases for Campaign QA Checks
Business Scenario #1: Consider a business that markets educational programs to students. The process to acquire student contacts includes the submittal of teacher nominations. Database ETL jobs that process these nominations files, create separate contacts for student and teacher, and loads a series of tables used to associate these contacts. Each contact is also associated with a school and home address as received on the nomination and other data sources. Marketers then use this information to contact these students and include the nominator’s information in the messaging. In this business scenario, it is vital that the ETL processes responsible for loading the tables within the campaign data mart is trustworthy and that the matching processes are reliable. A data discrepancy, such as a scholar-teacher misassociation, negatively impacts the success rate of marketing initiatives. The implications of this faulty relationship data issue are disastrous because of the business use of this data element in marketing materials. In this example, the development of quality assurance processes with the campaign application tool would have captured the data issue.
Every business has its own set of marketing rules. In the previous business case, the scholar and teacher must have a valid association to appropriately market to the target audience. For every business rule, it is strongly encouraged to incorporate high adverse impact ‘rule breakers’. If a scholar and teacher must have a valid association then any relationship with a location distance outside of an acceptable range should be deemed suspect when comparing their respective address information. This check can be done using a single Select process box within IBM’s Unica Campaign. Longitudinal and latitudinal data for scholar and teacher can be leveraged to calculate the distance between the locations and any cases with a distance outside an acceptable range can be suppressed and investigated further. Rule breakers such as this should be a standard suppression process in campaigns.
Business Scenario #2: Another business case for this type of campaign side integrity check relates to purchased lists. Consider the scenario of a retail company preparing the launch of a new store grand opening. A lack of existing customers within the surrounding area of the store location requires the retailer to purchase contacts from a list vendor. While companies that choose to purchase list normally conduct a series of validations it is often limited to matching existing contacts to list contacts, ensuring only those that are new to the database are purchased. However, in the case of this business scenario, it would benefit the retailer to guarantee the list’s contact addresses are all within a reasonable distance of the new store location. To execute a campaign for this type of promotion, qualifying records based on location is a crucial marketing requirement. Naturally, this check should be managed on the database side as the contacts are loaded. However, businesses sometimes operate on a limited timeframe where time to market is important. In this case, it is not uncommon for a list to be imported directly into the campaign system. Regardless, dedicated quality assurance campaign process boxes should be a standard in list generated campaigns to capture rule breakers. An appropriate process check for this scenario would include a Segment process box that would group contacts by State. A campaign developer would then get a read of contact count by state and could immediately identify issues such as a count greater than 0 of contacts located on the east coast for a campaign promoting the grand opening of a store on the west coast.
Campaign QA: 4 Step Process
Both of the business scenarios above could substantially benefit from the addition of quality assurance processes within campaign. Campaign developers can follow four simple steps to ensure the data used for marketing purposes is accurate and appropriately serves campaign specific objectives. These steps are:
1. Develop a list of ‘Rule Breakers’
2. Create campaign logic to capture each type of rule breaker
3. Suppress rule breakers
4. Escalate issue to IT department (include suppressed contacts)
The first step is to develop a list of ‘Rule Breakers’. In order to create this list, a campaign developer must fully understand the business and the campaign requirements. These rule breakers would represent data instances that do not adhere to marketing critical business logic. When a list of rule breakers is created, develop logic within a campaign process box to represent each of them. These will serve as the actual QA campaign processes. (Helpful Tip: Name each box after the represented broken rule. i.e. ‘Contact > 50mi away’ or ‘Contact Count by State’). Use these process boxes as exclusions and suppress these instances of nonconformity to critical business rules. Once these rule breakers are suppressed the remaining contacts can continue downstream. The final step in the process is to analyze each of the rule break instances. These excluded contacts may represent valid instances of non-conformity. For example, in business scenario #1, a teacher and student may have addresses that are a hefty distance apart, however research uncovers both are associated with a boarding school. In this case, the distance is acceptable. Unfortunately, when rule breakers are discovered, there are few that can be explained by valid exceptions. Most often, these quality assurance campaign checks uncover holes in ETL logic that only worsen with time. This is more common when new database processes and job are introduced to the system.
The Campaign QA Process is a simple way for any campaign developer to proactively guard against the adverse impacts of looming data issues and to take responsibility for data integrity.
Feel free to contact me directly with any questions. I always welcome the opportunity to expand my network of CRM enthusiasts!- Candice M. Narvaez
Wednesday, July 6, 2011
Unica Campaign: Let A Macro Decide Who to Contact and Where
Thursday, June 2, 2011
You can run, but you can't hide Rogue DHCP Server
Wednesday, May 25, 2011
Unica Campaign: Target Customer Based On Proximity to a Location
As a former marketer at Macy's Central, it was very typical of our department to pull list, sometimes adhoc, for local promotions. In all cases we leveraged state, zip and county data in our system to select contacts based on their proximity to the event. When Macy's was once divided into several districts it was easier (although not by much) for each corporate district to insert neighboring counties (in proximity to event location) in a Unica campaign and pull their own list. But if you are structured like most companies, there is typically a single national office pulling campaign lists. With that said, its difficult to pull list based on contact's locality without having detailed information or intimate knowledge of the surrounding areas (neighboring counties, zips, states-when event is on the border).
Well, have you ever tried leveraging longitudinal and latitudinal data to select contacts within a given radius of your event's location?
As a marketer you can do this in Campaign, independently of your hosting company or internal IT department and you can earn some serious brownie points with your manager!
It's pretty simple. Let's say you are a preparing an email or direct mail campaign for a local promotion. The promotion is only good at a given location (maybe at a store grand opening). The location is Charlotte, North Carolina (which is not too far from the border of South Carolina). Well, you wouldnt want to pull contacts based on state because you'd miss out on contacts near the border of South and North Carolina while picking up someone in Raleigh, 2hrs away from the location! It also wouldnt be feasible to look up neighboring counties and zip codes because everytime you pull a similar campaign you'd have to do the same leg work.
Instead, start out by selecting contacts based on state (yes, i know, i already told you not to do that but bare with me). Once you have a smaller subset of your database, you can refine this group based on distance from event location by applying 'Zip 50' logic to this group. In a select box, using raw sql (dont get scared, I'll provide the sql below) apply a trigonometric calculation to pick up only those records within a certain distance of the event. The guessing game is eradicated. You can finally choose contacts based on their exact proximity to an event and not based on some estimate. It is also a highly transferable solution. You can take the same logic and just pop it into another campaign. O Joy!
Below is the basic trigonometric calculation. Feel free to comment or contact me at mass.it.consulting@gmail.com if you have any issues implementing this solution.
select distinct t.master_individual_id (audience level)
from <temptable> t
inner join individual_table base with (nolock)
on t.individual_id = base.individual_id
inner join address_table s with (nolock)
on base.primary_address_id = s.address_id
where coalesce(s.longitude,'x') <> 'Unknown' and coalesce(s.latitude,'x') <> 'Unknown'
and
case when s.zip_code = (event location zip code) then 0.0
when s.longitude = (event location longitude) and s.latitude = (event location latitude) then 0.0 else
acos(cos(radians(s.latitude))*cos(radians(s.longitude))*cos(radians(event location latitude))*cos(radians(event location latitude)) + cos(radians(s.latitude))*sin(radians(s.longitude))*cos(radians(b.event location latitude))*sin(radians(event location longitude)) + sin(radians(s.latitude))*sin(radians(event location latitude))) * 3963.1 end
>= 50 (mean within 50 miles, you can change it)
order by 1
Too little bandwidth and too little time to figure out who is using it all
Tuesday, May 24, 2011
All Computer Support is not Good Computer Support
Sunday, May 22, 2011
Auto Populate Fields in Unica Plan
The problem:
1. The form was managed outside the system (Unica Plan) requiring marketers to manage their time and effort between planning processes within the tool and outside the tool, some of which included redundant tasks.
2. There existed common fields on the form and current project templates (redundancy)
3. Executives that are less IT savvy would need to access the tool once the form was incorporated into the system.
The solution (in a nutshell):
1. Introduce a new form to an existing project template. This brings marketing planning processes within a single system making it easier to manage and more importantly, easily tracked!
2. Remove redundancies between existing fields in Plan templates and fields on the latest form by creating auto populating functionality. The new form created should auto populate data into fields on shared project forms through a database linkage on object id. Now, Unica's Admin Guide and Forms Editor doesn't make this capability easy to implement. It requires a bit of creativity. Once the skeletal of the form is created through Forms Editor you will need to make manual edits within the xml file. I literally had to teach myself XML code for this solution, you can learn anything on Google!
3. Add an approval process on the workflow tab. Any approval created sends an email to an approver, the approver is then sent to the summary tab of the intended project. Therefore the newly introduced form should be added to the summary tab of a project template. This sends the less savvy approver directly to the content that is relevant to him or her. Yes, it does require additional licenses if these approvers don't already hold a license BUT only the most basic license is needed.
While this was a painful solution to create, it was implemented successfully and 50+ projects and counting are leveraging it. I experienced many firsts during this change order: designing AND implementing a Plan solution, writing XML code, creating a form and updating existing forms to auto populated data inputted from the newly introduced form, and creating a new template and transferring functionality over from existing templates.
For any questions on any part of this solution or any Unica Campaign, Plan or Emessage related question, feel free to leave a comment below.