Using Key Codes

Keycodes – a specific promotional code - can be added and used in your outbound marketing, the principle being that these unique codes are then quoted by recipients when transacting, allowing the activity to be tracked in PeopleStage as a response to a particular campaign Message.

Keycodes are not created at the individual level but do reflect and represent different ‘flavours’ of message. For example, a DM message with Content including 2 different styles and 4 brochures potentially creates 8 different message combinations; PeopleStage can issue a code to indicate which one of those 8 variations an individual is to receive.

To add a keycode:

  • Navigate to the Delivery step and into the Output grid view

Delivery Step Grid View

  • Click on Add Keycode Column…

In the window that opens, there are 3 options for generating your keycode(s) – accessed via the KeyCode Generation Type drop-down:


  • PeopleStage will generate the code according to the combination of selected Content fields.
  • You can optionally add a Keycode Prefix. This could, for example, identify the type of campaign.

Add KeyCode Column Auto-Generated

A Keycode column is added into the output grid as an additional Content Field and, by default, will be output on the Delivery file unless you override the default by right-clicking on the column header.

Auto-Generated KeyCode Column Added


  • PeopleStage combines the various/selected Content Fields into a single concatenated text string.

Concatenated KeyCode Column Added

Load From File

PeopleStage allows you to navigate to and insert a saved file containing the required keycode(s).

The keycode information generated must tie back to a variable found on the transactional table. This variable must link to the Keycode Definitions within the Diagram Settings Editor… This is an Admin function which is accessed via the File – Administration menu.

Diagram Settings Editor KeyCode Definitions

The variable reference is added into the Keycode Definitions tab on the transactional table, using the variable reference name and not the variable name/description.

Once applied to the PeopleStage instance, using a Keycoded Response successfully will always depend on the variable defined in the Diagram Settings Editor being updated with the referenced keycodes.