Difference between revisions of "Configuring Automated Wave Campaigns"

From Vital Soft Wiki
Jump to: navigation, search
>Johno
(Created page with "== Summary == Automated Wave Campaigns are configured in a spreadsheet called '''WaveCampaigns''', located in the ''data/config'' directory. The file contains two global wor...")
 
>Johno
 
(8 intermediate revisions by the same user not shown)
Line 59: Line 59:
 
| WaveName
 
| WaveName
 
| The unique wave campaign name.
 
| The unique wave campaign name.
−
|-
 
−
| CampaignName
 
−
| The name of the campaign for that wave step.
 
 
|-
 
|-
 
| Step
 
| Step
 
| The step number.
 
| The step number.
 +
|-
 +
| StepName
 +
| The name of the individual step.
 
|-
 
|-
 
| ExportType
 
| ExportType
Line 120: Line 120:
 
| MBR_ADDR_DATA
 
| MBR_ADDR_DATA
 
| Loan
 
| Loan
−
| 5;17;21
+
| 21;31;41
 
|-
 
|-
 
| Welcome
 
| Welcome
Line 130: Line 130:
 
|  
 
|  
 
|}
 
|}
 +
 +
* When tracking campaigns, Vital Signs will concatenate the WaveName and StepName together.  Our sample Welcome Wave would consist of 5 total campaigns, however since only 3 of them contain product offers, only 3 will be tracked:  Welcome_eStatements, Welcome_CDs and Welcome_Loans.
  
 
== Selection Worksheet ==
 
== Selection Worksheet ==
  
−
The '''Campaigns''' worksheet contains one record for each '''step''' of each different wave campaign:
+
Each wave campaign needs a '''Selection''' worksheet to specify the selection criteria for each step of the wave.  The worksheet name is the same as the WaveName.
 +
 
 +
The column names in this worksheet are the same as a selection worksheet in document distribution.
 +
 
 +
See [[Defining a Selection|defining a selection]] for more information on how to create a selection.
 +
 
 +
With wave campaigns, an optional '''Global''' selection is followed by an optional selection specific for that step in the wave.  The StepName is used as the selection name.
 +
 
 +
The following table shows an example for the Welcome wave campaign:
  
 
{| class="wikitable"
 
{| class="wikitable"
−
| '''Excel Column (Note)'''
+
| '''Name'''
−
| '''Purpose'''
+
| '''Step'''
 +
| '''Type'''
 +
| '''TypeName'''
 +
| '''TypeValue'''
 +
|-
 +
| Global
 +
| 1
 +
| SetVar
 +
| OpenStartDate
 +
| =Date(MonthStart(Only(Wave_Start_Date)),'YYYY-MM-DD')
 
|-
 
|-
−
| WaveName
+
| Global
−
| The unique wave campaign name.
+
| 2
 +
| SetVar
 +
| OpenEndDate
 +
| =Date(MonthEnd(Only(Wave_Start_Date)),'YYYY-MM-DD')
 
|-
 
|-
−
| CampaignName
+
| Global
−
| The name of the campaign for that wave step.
+
| 2
 +
| SetVar
 +
| OpenEndDate
 +
| =Date(MonthEnd(Only(Wave_Start_Date)),'YYYY-MM-DD')
 
|-
 
|-
−
| Step
+
| Global
−
| The step number.
+
| 3
 +
| Field
 +
| MBR_OPEN_DATE
 +
| >=$(OpenStartDate)<=$(OpenEndDate)
 
|-
 
|-
−
| ExportType
+
| Global
−
| The export type is usually '''Export''', but can be any type supported by document distribution.
+
| 4
 +
| Field
 +
| OK_TO_MAIL
 +
| Yes
 
|-
 
|-
−
| Definition
+
|  
−
| The ID of the object being exported.  Usually one of MBR_ADDR_DATA or MBR_PHONE_DATA.
+
|  
 +
|
 +
|
 +
|
 
|-
 
|-
−
| ProdType
+
| eStatements
−
| The product type being promoted.  One of: Share, Loan or Service.
+
| 1
 +
| Field
 +
| MBR_ACCOUNT
 +
| =age(only(Wave_Start_Date), MBR_BIRTH_DATE)>=18
 
|-
 
|-
−
| ProdCodes
+
| eStatements
−
| A list of valid product codes.
+
| 2
−
|}
+
| Field
−
 
+
| eSTATEMENTS
−
For example, the Welcome wave campaign might look like this:
+
| No
−
 
 
−
{| class="wikitable"
 
−
| '''WaveName'''
 
−
| '''Step'''
 
−
| '''CampaignName'''
 
−
| '''ExportType'''
 
−
| '''Definition'''
 
−
| '''ProdType'''
 
−
| '''ProdCodes'''
 
 
|-
 
|-
−
| Welcome
+
|  
−
| 1
+
|  
−
| JoinLetter
+
|  
−
| Export
 
−
| MBR_PHONE_DATA
 
 
|  
 
|  
 
|  
 
|  
 
|-
 
|-
−
| Welcome
 
−
| 2
 
 
| eStatements
 
| eStatements
−
| Export
+
| 1
−
| MBR_ADDR_DATA
+
| Field
−
| Service
+
| MBR_ACCOUNT
−
| 79
+
| =age(only(Wave_Start_Date), MBR_BIRTH_DATE)>=18
 
|-
 
|-
−
| Welcome
 
−
| 3
 
 
| CDs
 
| CDs
−
| Export
+
| 2
−
| MBR_ADDR_DATA
+
| Field
−
| Share
+
| MBR_TOTAL_SH_BAL
−
| C06;C12;C18;C24
+
| >=5000
 
|-
 
|-
−
| Welcome
 
−
| 4
 
−
| Loans
 
−
| Export
 
−
| MBR_ADDR_DATA
 
−
| Loan
 
−
| 5;17;21
 
−
|-
 
−
| Welcome
 
−
| 5
 
−
| Survey
 
−
| Export
 
−
| MBR_ADDR_DATA
 
 
|  
 
|  
 
|  
 
|  
−
|}
+
|  
−
The configuration file is called VSCampaigns. 
+
|  
−
 
+
|  
−
{| class="wikitable"
 
−
| '''Excel Column (Note)'''
 
−
| '''Purpose'''
 
 
|-
 
|-
−
| NAME (1)
+
| Loans
−
| The unique campaign name.
+
| 1
 +
| Field
 +
| MBR_ACCOUNT
 +
| =age(only(Wave_Start_Date), MBR_BIRTH_DATE)>=18
 
|-
 
|-
−
| START-DATE (2)
+
| Loans
−
| The launch date of the campaign.  Leave blank for Wave campaigns.
+
| 2
 +
| Field
 +
| MBR_TOTAL_LN_CNT
 +
| <1
 
|-
 
|-
−
| PROD_TYPE
+
| Loans
−
| One of:  Share, Loan, Service, Member, Dormant.
+
| 3
 +
| Field
 +
| MBR_CREDIT_SCORE
 +
| >620
 
|-
 
|-
−
| PROD_CODES (3)
+
| Survey
−
| The specific product code(s) for the target product.
+
| 1
−
|-
+
| Field
−
| FILENAME (4)
+
| MBR_ACCOUNT
−
| The name of a file containing the members who are part of the campaign.
+
| =age(only(Wave_Start_Date), MBR_BIRTH_DATE)>=18
 
|}
 
|}
  
−
:Notes:
+
# The step '''JoinLetter''' uses the '''Global''' selection and does not have any additional selection criteria.
−
:# The campaign '''must''' be unique, and must not conflict with any automatically generated wave campaign names.
+
# The age restriction is repeated in all steps except '''JoinLetter''' since members under 18 will still get the welcome letter.
−
:# Standard campaigns have a single start date which is entered here.  Since wave campaigns have multiple start dates, no start date should be entered here.  The start date of a wave campaign must be appended to the FILENAME in the form YYYYMMDD.
+
 
−
:# For Share, Loan and Service campaigns, the target product(s) must be identified here.  The field should contain a semi-colon delimited list of share desc-abrv(s), loan collateral code(s) or service control flag number(s).  Leave blank for Member and Dormant campaigns.
 
−
:# Enter the name of the file in ''data/config/Campaigns'' that identifies the members who received the campaign.  If this is a '''manually''' generated wave campaign, enter the file name prefix.  The actual filenames will be this prefix followed by the start date in the format YYYYMMDD. For example, if the actual files are called NewIRAPromo20160315, NewIRAPromo20160615 and NewIRAPromo20160915, enter NewIRAPromo as the filename. 
 
  
−
* Vital Signs will track campaigns that have been configured in the VSCampaigns file '''plus''' all automatically generated wave campaigns configured in WaveCampaigns.
 
  
−
== FILENAME Layout ==
+
Back to [[Automated Wave Campaigns]].
  
−
For all campaigns (except New Member), the file '''must''' contain a list of member account numbers in a column called MBR_ACCOUNT.  The file may contain other columns, but only the MBR_ACCOUNT column is required/used.  The file must be stored in the ''data/config/Campaigns'' directory.  For New Member campaigns designed to attract new members to the Credit Union, the file will have a different layout described here.
+
Back to [[Campaign Fundamentals]].

Latest revision as of 00:41, 13 February 2016

Summary

Automated Wave Campaigns are configured in a spreadsheet called WaveCampaigns, located in the data/config directory.

The file contains two global worksheets (tabs) called WaveConfig and Campaigns, plus an additional worksheet (tab) for each Wave name. For example, a wave campaign called Welcome, will include a worksheet called Welcome containing all of the specific selection criteria needed to execute all steps of the wave campaign.

WaveConfig Worksheet

The WaveConfig worksheet contains one record for each different wave campaign:

Excel Column (Note) Purpose
WaveName The unique wave campaign name.
WaveStartDays (1) The ending month day number the wave uses. May be a semi-colon delimited list if the wave runs multiple times per month.
WaveMaxSteps The maximum number of steps executed by this wave campaign.
WaveFilePath (2) The output file path where the wave files are created.
WaveEmailList (3) A semi-colon delimited list of email addresses to receive confirmation that the wave files were created.
  1. This day number represents the day the wave was created and may be used as part of the selection criteria. If the wave runs more than once per month, this is a semi-colon delimited list.
  2. The specified path is a sub-directory of data/config and must exist.
  3. Not all configurations support email notifications. Since GenWaveData uses the Vital Signs document distribution engine, the ViewDocLog document is a good way to review the results of GenWaveData.

For example, a Welcome wave campaign might look like this:

WaveName WaveStartDays WaveMaxSteps WaveFilePath WaveEmailList
Welcome 15 5 WelcomeWave

Campaigns Worksheet

The Campaigns worksheet contains one record for each step of each different wave campaign:

Excel Column (Note) Purpose
WaveName The unique wave campaign name.
Step The step number.
StepName The name of the individual step.
ExportType The export type is usually Export, but can be any type supported by document distribution.
Definition The ID of the object being exported. Usually one of MBR_ADDR_DATA or MBR_PHONE_DATA.
ProdType The product type being promoted. One of: Share, Loan or Service.
ProdCodes A list of valid product codes.

For example, the Welcome wave campaign might look like this:

WaveName Step CampaignName ExportType Definition ProdType ProdCodes
Welcome 1 JoinLetter Export MBR_PHONE_DATA
Welcome 2 eStatements Export MBR_ADDR_DATA Service 79
Welcome 3 CDs Export MBR_ADDR_DATA Share C06;C12;C18;C24
Welcome 4 Loans Export MBR_ADDR_DATA Loan 21;31;41
Welcome 5 Survey Export MBR_ADDR_DATA
  • When tracking campaigns, Vital Signs will concatenate the WaveName and StepName together. Our sample Welcome Wave would consist of 5 total campaigns, however since only 3 of them contain product offers, only 3 will be tracked: Welcome_eStatements, Welcome_CDs and Welcome_Loans.

Selection Worksheet

Each wave campaign needs a Selection worksheet to specify the selection criteria for each step of the wave. The worksheet name is the same as the WaveName.

The column names in this worksheet are the same as a selection worksheet in document distribution.

See defining a selection for more information on how to create a selection.

With wave campaigns, an optional Global selection is followed by an optional selection specific for that step in the wave. The StepName is used as the selection name.

The following table shows an example for the Welcome wave campaign:

Name Step Type TypeName TypeValue
Global 1 SetVar OpenStartDate =Date(MonthStart(Only(Wave_Start_Date)),'YYYY-MM-DD')
Global 2 SetVar OpenEndDate =Date(MonthEnd(Only(Wave_Start_Date)),'YYYY-MM-DD')
Global 2 SetVar OpenEndDate =Date(MonthEnd(Only(Wave_Start_Date)),'YYYY-MM-DD')
Global 3 Field MBR_OPEN_DATE >=$(OpenStartDate)<=$(OpenEndDate)
Global 4 Field OK_TO_MAIL Yes
eStatements 1 Field MBR_ACCOUNT =age(only(Wave_Start_Date), MBR_BIRTH_DATE)>=18
eStatements 2 Field eSTATEMENTS No
eStatements 1 Field MBR_ACCOUNT =age(only(Wave_Start_Date), MBR_BIRTH_DATE)>=18
CDs 2 Field MBR_TOTAL_SH_BAL >=5000
Loans 1 Field MBR_ACCOUNT =age(only(Wave_Start_Date), MBR_BIRTH_DATE)>=18
Loans 2 Field MBR_TOTAL_LN_CNT <1
Loans 3 Field MBR_CREDIT_SCORE >620
Survey 1 Field MBR_ACCOUNT =age(only(Wave_Start_Date), MBR_BIRTH_DATE)>=18
  1. The step JoinLetter uses the Global selection and does not have any additional selection criteria.
  2. The age restriction is repeated in all steps except JoinLetter since members under 18 will still get the welcome letter.


Back to Automated Wave Campaigns.

Back to Campaign Fundamentals.

Retrieved from "https://wiki.vital-soft.com/index.php?title=Configuring_Automated_Wave_Campaigns&oldid=2485"