Versions Compared

Old Version 5

changes.mady.by.user Lopes da Costa, Valentina

Saved on

compared with

New Version Current

changes.mady.by.user Lopes da Costa, Valentina

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • All items within the rule are treated like an ‘OR’ ie: must purchase a coke or a sprite

    • Can only list items and/or combos here

Cart Requirements Exclusion

Cart must not include the items added in this rule for the benefit to be able to be ordered successfully.

  • All items within the rule are treated like an ‘OR’ ie: must NOT purchase a coke or a sprite

    • Can only list items and/or combos here

User Created

User must have been created in the loyalty system within this defined time band to be eligible for the incentive

...

User must pay with a given card type / payment method in order to redeem the benefit

Info

Note

...

: evaluation happens at payment, so you should use this rule sparingly to avoid user frustration so close to the sale.

Cool Down Period

If user has redeemed this particular incentive in the last n seconds, they are not eligible to redeem again

...

  • ON - on this transaction only

    • BETWEEN - between your x-y transactions

    • EVERY - on every multiple transaction

    • NOTE: Counts total loyalty transactions, not total transactions

Offers only Rules

Stackable

This is set in Earning Calculations. Offer can exist alongside a second, third, fourth (number is set in the configuration) offer(s) in the cart.

...

Authentication Required

When Authentication Required rule = false a signed out user can redeem the offer in-store. This does not apply for mobile order, given our app does not allow guests to do a mobile purchase. When Authentication Required rule = true only a signed in user is able to redeem the offer in-store.

  • Note: The default is all users need to Sign Up in order to be able to redeem offers in-store (in the case the rule is not added).

  • Note: This rule is not available for Reward given all users need to be signed in to redeem Rewards.

User Attribute

This ruleset allows operators to show an offer to an user, only if that user has user attributes that fulfill the rules set in Sanity. The list of user attributes that can be configured in this ruleset are:

Attribute in Sanity

Description

Battery level (batteryLevel)

  • can be <, > to a specific number from 1 - 100 (this is the battery level)

Was Date of Birth deleted? (dobDeleted?)

  • can be set to true or false

  • shows offer based on if date of birth of user was deleted

Was Phone number verified?(phoneVerified)

  • can be set to true or false

  • shows offer based on if user verified their phone number

Opted In to Promotional Emails? (promotionalEmails)

  • can be set to true or false

  • shows offer based on if user has opted in or not to promotional email

Zip Code (zipcode)

  • can be = or !=

  • shows offer based on the user’s saved zip code (e.g. 8002)

Delivery Address saved? (deliveryAddresses)

  • can be set to true or false

  • shows offer based on if guest has saved a delivery address in the app

Favorite Stores (favoriteStores)

  • can be = or !=

  • shows offer based on the user’s favorited store number(s)(e.g. 13651)

Favorite Offers (favoriteOffers)

  • can be = or !=

  • shows offer based on the user’s favorited offer sanity ID(s)(e.g. 6ad6850e-0dba-4314-a47d-759d93cca6f2)

Rewards only Rules

Loyalty Points

...