Classification rules for campaign stacking with unknow length (xxx>yyy>zzz)

Hi Laurent,

Per the screenshot attached I would expect the 3 reports : tracking code, campaign names and campaigns categories to have the same data/values in each report.

Classification rule builder is useful when you your variable always follow the same pattern and/or you can identify specific values in the string. 

I think instead of using rule builder, you should use classification importer (which is the new name for saint classification).

So if you go to Star >> Admin tools >> Classification importer >> export, then export all the tracking code that you want. Then you will have the file with all the keys.

You can then populate each column for each raw manually with the value that you need.

Best regards.

Alexis

Hi Laurent,

What is the maximum length of you campaign, by length I mean separate value in the tracking code ?

Does each level goes under a separate classified report or the same classified report ? 

Best regards.

Alexis Cazes

Hi Alexis,

each campaign code is alpha 16 but it's not a problem is the codes don't have the same number of characters.

The campaign stacking could have 1 to 16 codes for example (3 cases although I have less than 12 codes) :

752747d53fce0e1d

752747d53fce0e1d>3224749ae671f8e7>752747d53fce0e1d

752747d53fce0e1d>3224749ae671f8e7>752747d53fce0e1d>752747d53fce0e1d>3224749ae671f8e7>752747d53fce0e1d>752747d53fce0e1d>3224749ae671f8e7>752747d53fce0e1d>752747d53fce0e1d>3224749ae671f8e7>752747d53fce0e1d>752747d53fce0e1d>3224749ae671f8e7>752747d53fce0e1d>752747d53fce0e1d>3224749ae671f8e7>752747d53fce0e1d

the main poitn is to create a rule to split wit hthe separator > if there is only one code or several codes.

I almost found but the conditional rule is not easy to add when you don't know ho many codes we will find.

The classified values are linked on the eVar Campaign Stacking (the plugin insert the codes in a stack stores in the evar).

Campaign stacking -- Campaign codes (x>y>z)

                             -- Campaign name (I would like to classify from my campaign Saint files)

                             -- Campaign category (I would like to classify from my campaign Saint files)

                             -- Campaign sub-category (I would like to classify from my campaign Saint files)

Best,
Laurent

Hi,

yes I started to test this.

I  need to check if I could avoid to classify all the stacking as 1 new long string when I have a campaign code classification  SAINT file because there are a huge number of combinations.

I don't know if it's possible (in my case) to use it to classify as a second file each campaig ncode in the campaign code stacking. 

Best,

Laurent

Hi Laurent,

I think what you are trying to obtain might not work for the following reason. The initial string campaign stacking is your key.

Lets take the following example that you provided 

752747d53fce0e1d>3224749ae671f8e7>752747d53fce0e1d

The key that will be used to tie your saint classification data is 

752747d53fce0e1d>3224749ae671f8e7>752747d53fce0e1d

So we create a regex to split the different campaign id and we obtain the following

When we have that we can put the value of $1 $2 and $3 in different classified report 

-- Campaign name (I would like to classify from my campaign Saint files)

-- Campaign category (I would like to classify from my campaign Saint files)

-- Campaign sub-category (I would like to classify from my campaign Saint files)

BUT it will not create 3 separate unique key that we would be able to classify independently, meaning that we can only specify one campaign name, one campaign category and one campaign sub-category for the key 

752747d53fce0e1d>3224749ae671f8e7>752747d53fce0e1d

So you will not be able to classify a different campaign name, campaign category and campaign sub category.

I need to check if sending your data in a listvar variable will allow the classification that you desire

I believe each combination of code will be a unique key. 

http://microsite.omniture.com/t2/help/en_US/sc/implement/index.html#List_Variable