Automated Wave Campaigns

Summary

Wave campaigns run over multiple start dates and typically target a different pool of members each time they drop. The wave campaign may include multiple steps (or phases) where the same group of selected members will receive promotions for different products during each step of the wave. The target group of members will be reselected each time the wave is run to ensure that the member still qualifies to receive the promotion.

Any campaign can be a wave campaign as long as the name is the same, the same products are being targeted and the campaign runs multiple times. See Configuring Campaigns for more information.

This section, however, discusses automated wave campaigns which use the GenWaveData document to select qualifying members and create the output files to use for the campaign.

Sample Multistep Wave Campaign

A campaign that contacts new members after they have joined the Credit Union is a good example of a multistep wave campaign. This campaign has the following attributes:

• Runs monthly on the 15th of the month, and selects members based on the date they joined the CU.
• Step 1 generates a welcome letter thanking them for joining, but does not make any product offers.
• Step 2 promotes e-statements to new members over 18 without this service.
• Step 3 promotes CD products to new members over 18 with more than $5,000 in total assets.
• Step 4 promotes loan products if the member is over 18, has no loans and their credit score is at least 620.
• Step 5 sends an email with a member satisfaction survey to all members over 18.

All steps are generated every month using different dates to select the new members. Each step within the Welcome campaign has it's own name. The following table demonstrates this in more detail for a Wave Campaign, called Welcome, executed April 15, 2016:

Step	Name	New Member Dates	Product Type	Product Codes	File Created
1	JoinLetter	2016-03-01 to 2016-03-31			Welcome_JoinLetter20160615
2	eStatement	2016-02-01 to 2016-02-29	Service	79	Welcome_eStatement20160615
3	CDs	2016-01-01 to 2016-01-31	Share	C06;C12;C18;C24	Welcome_CDs20160615
4	Loans	2015-12-01 to 2015-12-31	Loan	21;31;41	Welcome_Loans20160615
5	Survey	2015-11-01 to 2015-11-30			Welcome_Survey20160615

1. The files will be created in the data/config/WelcomeWave directory.
2. The files will contain a pre-defined list of member name and address fields needed to complete the campaign.
3. If the campaign is targeting specific products, a similar file will be created in the data/config/Campaigns directory which contains the MBR_ACCOUNT number and may contain additional columns for data verification purposes. This file is required for campaign tracking and will be generated automatically each time the wave is executed.

Configuring Automated Wave Campaigns

All automated wave campaigns are configured in the WaveCampaigns spreadsheet located in the data/config directory.

The configuration file includes a information about the campaign, a description of each step (phase) in the wave and the selection criteria to be applied to each step of the wave. Each step is assigned a name, start day, target product information and the name of the GenWaveData chart to export for the campaign.

Generating the Wave Campaign Files

The campaign files are produced by executing the GenWaveData document from the host. The most common way to schedule the creation of wave files is to launch the request from a UC4 task using JVSRELOAD.

The syntax is:

   /VSJOBS/JVSRELOAD GenWaveData PRINT=WaveName vWaveCurrDay=nn

Where:

• WaveName: Is the name of the wave campaign.
• nn: Is the starting day of the wave.

For example:

   /VSJOBS/JVSRELOAD GenWaveData PRINT=Welcome vWaveCurrDay=15

Back to Campaign Fundamentals.