> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/loyalty-and-rewards/points-and-ways-to-earn/award-points-for-account-sign-up.md).
# Award points for account sign-up
Award customers a one-time bonus when they get a store account, and understand why enrolling and earning the sign-up bonus are two different moments.
**Account Signup** awards a one-time bonus that gives new members a points balance from day one.
Account Signup settings — one points value, awarded once.
#### When the bonus is awarded
In most cases the sign-up bonus is awarded when the customer **signs in for the first time**, on both participation settings. POS is the exception, and is covered below.
This matters because joining your programme and earning the sign-up bonus are not always the same moment:
| Member Participant Criteria | Customer joins the programme | Sign-up bonus is awarded |
| ------------------------------------------- | ------------------------------------ | --------------------------------------------------------------------------------------- |
| **All customers** | When their email is captured | Later, when they sign in for the first time. POS customers are the exception, see below |
| **Only customers who have a store account** | When they sign in for the first time | At the same moment |
So on **All customers**, a shopper who checks out as a guest is enrolled straight away and starts earning on orders, but the sign-up bonus waits until they create an account and log in. They have not missed it, it is still owed to them.
{% hint style="info" %}
What counts as getting a store account depends on which account system your store runs. On Shopify's new customer accounts it is the first successful login, including Sign in with Shop, Google or Facebook. On legacy accounts it is registering with an email and password. See [Loyalty membership eligibility settings](/loyalty-and-rewards/getting-started/loyalty-membership-eligibility-settings.md) for the full list of what does and does not count.
{% endhint %}
#### The POS exception
An email captured in POS awards the sign-up bonus without the customer needing a store account. What it takes depends on your setting:
* **All customers**: an email on the POS customer profile is enough. No order is needed.
* **Only customers who have a store account**: a POS order placed against a profile that has an email.
This is deliberate. Someone standing at your counter has handed over their email, and making them go home and create an account before they get their welcome bonus would undermine the moment.
If a POS customer has no email on their profile, the bonus is not lost. Adding an email later, in POS or in the admin, awards it at that point.
#### What does not award the bonus
None of these award the sign-up bonus on their own, because none of them create a store account:
* Guest checkout
* Shop Pay checkout
* Newsletter or email capture forms
* A customer created by a third-party app
* A customer created in the admin, or by the Admin API, without the customer then logging in
On **All customers** these all still enrol the customer, so they earn on orders from that point. On **store account only** they do not enter the programme at all yet.
{% hint style="warning" %}
A customer with no email address on their profile cannot be awarded the sign-up bonus, whichever setting you run.
{% endhint %}
#### Before your programme goes live
The bonus follows your programme status:
* While the programme is **inactive**, nobody becomes eligible and nothing is awarded.
* While it is **scheduled**, only accounts on your **tester email domains** behave like live customers and can earn the bonus. Everyone else waits for the start date.
See [Program status, start date, and tester domains](/loyalty-and-rewards/getting-started/program-status-start-date-and-tester-domains.md).
#### Settings
* **Points awarded on signup** sets the one-time bonus.
* **Display name** and **Description** appear in storefront loyalty widgets.
* Set **Status** to **Active** and **Storefront widget display** to **Visible** for a launch.
Customers do not need to reach a membership tier first.
#### The Klaviyo link
Awarding the sign-up bonus is what sets the Klaviyo profile property `roadmap_has_account` to true.
That makes it the property to gate loyalty flows on, since it marks the point at which someone is a full member with an account rather than an enrolled email address. See [Loyalty profile properties and email snippets](/loyalty-and-rewards/loyalty-klaviyo-integration/loyalty-profile-properties-and-email-snippets.md).
#### Related guides
* [Loyalty membership eligibility settings](/loyalty-and-rewards/getting-started/loyalty-membership-eligibility-settings.md)
* [Program status, start date, and tester domains](/loyalty-and-rewards/getting-started/program-status-start-date-and-tester-domains.md)
* [Ways to earn points: overview](/loyalty-and-rewards/points-and-ways-to-earn/ways-to-earn-points-overview.md)
* [Loyalty profile properties and email snippets](/loyalty-and-rewards/loyalty-klaviyo-integration/loyalty-profile-properties-and-email-snippets.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.roadmap.so/loyalty-and-rewards/points-and-ways-to-earn/award-points-for-account-sign-up.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
