Consecutive

The Consecutive restriction determines whether members need to complete events on consecutive days to earn the outcome associated with a rule. A day is defined as a calendar day (for example, Monday). The action must occur on two (or more) consecutive days for the member to earn the outcome.

For example, events that place on Jan 1st, 23:55 and Jan 2nd, 00:05 are considered consecutive. Events that take place on Jan 1st, 23:55 and a Jan 3rd, 00:05 action are not considered consecutive.

The Consecutive restriction works in tandem with the Total Number of Times restriction. Specify the number of consecutive days in the Total Number of Times restriction. You must enter a value of 2 or greater to enable the Consecutive restriction.

Time zone settings

The Consecutive restriction first looks at the time zone of the user. If that is not set, it looks at default system time zone. For example,

User Time Zone: nil

System Default Time Zone: America/New_York

Note that there is an underscore in “America/New_York”. A common mistake is to make this “America/NewYork”.

Events for which this is a core restriction

None.

Example

A promotional campaign challenges members to read an article in the brands’ online magazine on three consecutive days. If members do this, they earn an outcome (for example, 100 bonus points).

Look at the following image. For the “read_article” event, the Total Number of Times restriction indicates that members must complete the event at least 3 times. In conjunction with this, the Consecutive restriction specifies that the member needs to complete the events on consecutive days.