Activity: birthday
Success team avatar
Written by Success team
Updated over a week ago

You can offer your customers points for their birthday!

Customers will enter their date of birth in the "Earn Points" section of the panel. Once a year on that specific date, the customer will be awarded the points.

As a store, you can choose whether to give your customers enough points to claim a reward on their birthday (for example 500 points to give them a £5/$5 discount) or whether to give them a smaller amount of points to add to their points balance.


Common Questions:

Q. Can a customer change their birthday?

You have the ability to edit your customer's birthday through your merchant area screen. To make this change simply go to members, select the customer you wish to change, and at the top right click Actions > Change birthday.

The 365-day cool-off period applies. This means that if your customer already received points within a year, they will not receive them again, after changing the date.

Q. When do customers receive points during their birthday?


Customers will receive points around midnight UTC.

Q. If a customer enters their birthday as part of the sign-up process, will they receive points?

Customers will only receive points if they have entered their birthday via the loyalty panel or if we have imported their birthday into LoyaltyLion (learn more about birthday imports).

Q. How can I see when a customer has changed their birthday?

Q. Why is there a limitation on changing the birthday?

We require birthdays to be more than five years ago and less than 110 years ago. So for example, on 5 August 2021, you can set a birthday to a minimum of 5 August 2016.e current year. If this happens, we will ask them to enter a valid date.

Q. How can I see when a customer has changed their birthday?

Q. Why is there a limitation on changing the birthday?

We require birthdays to be more than five years ago and less than 110 years ago. So for example, on 5 August 2021, you can set a birthday to a minimum of 5 August 2016.

Did this answer your question?