Plan, execute, measure and optimize customer experiences

% split node (after optimization)

Accepted Solution Solved
Reply
Occasional Contributor
Posts: 11
Accepted Solution

% split node (after optimization)

Good morning  ..  Please help 

 

In my diagram,  have an available contact base of 272,251 customers 

 

and I'm using a percentage split node 34% and 66%

 

In my campaign group, I have specified a required count on campaign level of 60,000

 

I also have a cellsize constraint of 60,000 in my scenario on campaign_cd

 

I need an end result (after optimization) with a total of 60,000 customer that is split accordingly to the above specifications  ?

 


Accepted Solutions
Solution
‎05-30-2017 02:11 AM
SAS Employee
Posts: 76

Re: % split node (after optimization)

This functionality is being considered for a future release, but for now the only reliable way to accomplish it is to have a post-process node handle it in code, or put a linkable cell node after the optimized communication node and do your split by percentage in a follow-up (non-optimized) campaign (link > split > cell/cell > comm).

 

If you try to force the logic into your optimization scenario, you'll either:

  • have potentially biased results (since the higher value customers will likely go into the larger cell, since that will result in a higher objective value)
  • get an undesired result (if the input size is < 60,000 total and you specify 40,000 and 20,000 respectively as maximum constraints) since there's no guarantee the split cells will have the correct ratio
  • have infeasible constraints (if your input size is < 60,000 and you try and specify 40,000 and 20,000 respectively as minimum constraints for two other cells)
  • have to frequently maintain the results (if the "main" cell size changes from 60,000)

View solution in original post


All Replies
Super User
Posts: 5,317

Re: % split node (after optimization)

Are you BY any chance using CI Studio or any other of product in the CI/MA offerings?
Also, what have you tried so far?
Data never sleeps
Occasional Contributor
Posts: 11

Re: % split node (after optimization)

hello  ..  yes, i am using Customer Intelligence Studio, Version 6.3

 

I have tried to limit my campaign's overall cellsize to 60000 in the Campaign Group

 

I have also added a Contraint in my senario but it doesn't seem to work

 

I have attached a document (first message)

 

Thanks for your help  Smiley Happy

 

Gerda

Contributor
Posts: 46

Re: % split node (after optimization)

What exactly are you trying to achieve - do you want these 60000 to be split between these two cells as 1:2?     Since you know the total count, you also know that this will mean 20.000 and 40.000 counts in the cells.  You can enable two cell-level constraints instead of one campaign-level aggregate constraint.

 

 

-------
Dmitriy Alergant, Tier One Analytics
Solution
‎05-30-2017 02:11 AM
SAS Employee
Posts: 76

Re: % split node (after optimization)

This functionality is being considered for a future release, but for now the only reliable way to accomplish it is to have a post-process node handle it in code, or put a linkable cell node after the optimized communication node and do your split by percentage in a follow-up (non-optimized) campaign (link > split > cell/cell > comm).

 

If you try to force the logic into your optimization scenario, you'll either:

  • have potentially biased results (since the higher value customers will likely go into the larger cell, since that will result in a higher objective value)
  • get an undesired result (if the input size is < 60,000 total and you specify 40,000 and 20,000 respectively as maximum constraints) since there's no guarantee the split cells will have the correct ratio
  • have infeasible constraints (if your input size is < 60,000 and you try and specify 40,000 and 20,000 respectively as minimum constraints for two other cells)
  • have to frequently maintain the results (if the "main" cell size changes from 60,000)
Occasional Contributor
Posts: 11

Re: % split node (after optimization)

Thanks  Smiley Happy

☑ This topic is solved.

Need further help from the community? Please ask a new question.

Discussion stats
  • 5 replies
  • 180 views
  • 0 likes
  • 4 in conversation