The promo code module allows you to insert unique discount codes for contacts in your communications. This way, you can minimize code sharing and reward your loyal contacts with exclusive bonuses.
|Prerequisites||The module mut be activated as well as have promo codes imported.|
|Path||> Campaigns > Recurrent campaign|
Once the configuration of the module and message is done, you can create campaigns to assign codes and send the communication.
To start, slide the Grant promo code node in the campaign. The configuration of the node will ask you to select the lot of promo codes that you want to use. You will also find the instructions to configure the message node.
In the Send an email node, input the parameters exposed by the promo code node. The idAssociatedProcess and idPrimary can be found in the parameters available for the entire campaign.
If you do not see appear the parameters in the email node, your message is not properly configured to support promo codes. Consult the message configuration further in this article.
In the message. to display the code assigned to the contact, use the following script.
You may use it as many times as desired. For example, if your system allows it to be redeemed through a link, you may add it inside of a button link.
Testing the message
Since the message uses a data unique for each contact, tests with the default contact will not work. To test, you must test launch the campaign. Then, find the parameters assigned to the contact in the PromoCodes_UsedCodes table and input them as the test and preview values in the parameter configuration.
Note that assigned codes for testing purposes will be removed of the lot and therefore not assigned later on.
|Path||> Relational Data > Promo codes|
To start with the promo codes module, activate it on the project level. You will then need to create your firts code lot which allow you to separate the usage of the promo codes used for different campaigns.
The creation of the lot creates a new system relationnal table which you can manipulate like regular relational tables. You can therefore populate it using standard import or API methods.
The table contains two fields, one for the code (required) and another for the expiration of the promo code (optional). The date will be used to delete the codes at the specified date.
Remaining code threshold
Each lot can be configured a code threshold that will send a notification once the number of codes falls below that level. To subscribe to these notifications, you will need to be subscribed to the notification in the Notification Feeds. For more information on Notification Feeds, consult this article.
To use promo codes, you must also configure a message that supports receiving the parameters of the promo code node. We recommend making it as a template so that you can easily find and reuse it.
In the additionnal options of the message find the Parameters tab. Once in the tab, you will need to add the three following parameters :
|idAssociatedProcess||Whole number (int)||Yes|
|idPrimary||Whole number (int)||Yes|
|idSecondary||Whole number (int)||Yes|
It should look like this.
You will also need to activate the Promo codes query, in the Data sources tab. You will be prompted to insert the parameters for the query, use the left dropdowns to choose Parameter, then select the corresponding parameter that you configured previously.