Configuring Automated Wave Campaigns
Contents
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. |
- 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.
- The specified path is a sub-directory of data/config and must exist.
- 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. |
| CampaignName | The name of the campaign for that wave step. |
| Step | The step number. |
| 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 |
Selection 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. |
| CampaignName | The name of the campaign for that wave step. |
| Step | The step number. |
| 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 | 5;17;21 |
| Welcome | 5 | Survey | Export | MBR_ADDR_DATA |
The configuration file is called VSCampaigns.
| Excel Column (Note) | Purpose |
| NAME (1) | The unique campaign name. |
| START-DATE (2) | The launch date of the campaign. Leave blank for Wave campaigns. |
| PROD_TYPE | One of: Share, Loan, Service, Member, Dormant. |
| PROD_CODES (3) | The specific product code(s) for the target product. |
| FILENAME (4) | The name of a file containing the members who are part of the campaign. |
- Notes:
- The campaign must be unique, and must not conflict with any automatically generated wave campaign names.
- 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
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.
