Campaign Levels

PeopleStage can run campaigns at either the Person or Transaction Level.

Person level campaigns ensure that each message in a campaign can only send one communication per person. Deduplication is performed at the Person level and this, most typical, style of campaign works well for a marketing campaign where it is the person who is of interest.

Operational campaigns, however, often require you to send multiple communications to the same person. Take, for example, an insurance company needing to send multiple communications to the same person at the same time – perhaps a reminder for each insurance policy that is about to expire.

The levels you can use to create campaigns are set by your system administrator.

You can start a campaign by dragging the relevant New Campaign template from the Library and onto your Diagram workspace. Based on their level, PeopleStage filters out any incompatible elements, including that:

• You cannot use selections or variables if they are from a table that is a sibling to the campaign table level – e.g. in the Holidays system, Bookings and Policies are sibling tables and you cannot, therefore, add Policies’ selections to a Bookings campaign

• Templates cannot be used if they are created from a campaign of a different level – e.g. a Message template created in a People Campaign can only be used in other People level campaigns

The way in which selections and variables are used within a campaign will depend on the relationship between their levels. For example, if a transactional level variable is output from a Person campaign, you have to specify a “one per” option to determine which transaction to use. However, if a transactional variable is output in a transactional level campaign, no other information is needed.

The table below provides a summary of the different relationships between the level of the campaign, and that of selections and variables:

Summary of Relationships for Campaign Levels and Selections & Variables

	Person Level Audience Selection	Transactional Level Audience Selection
Person Level Campaign	Traditional default marketing scenario Example Select high value customers and send them messages that could refer to their ‘most recent’ or ‘highest value’ transaction. Each message can refer to transactional data, but only from a single transaction which is identified in the Content step using a “One per” option. One communication per person per Message step.	Useful single transaction scenario Example Select the last transaction per person and send a sequence of messages to that person, consistently referencing the same transaction. All messages in the campaign can consistently refer to the one transaction per person identified in the Audience selection. One communication per person per Message step.
Transactional Level Campaign	Unusual, but supported scenario Example Select all high value customers and send them a survey for each of their transactions. Potentially multiple communications per person per Message step – i.e. one for every transaction made by the person. Person level selections would more typically be used as an Exclude and would suppress all transactions by that person.	Typical operational scenario Example Select all insurance policies due for renewal next month and send a separate communication for each. Potentially multiple communications per person per Message step – i.e. one for each selected policy. All messages can refer to the selected policy or to any person level data.