> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/playbook/sample-setups/sample-campaigns/3-earn-1-stamp-for-every-transaction.md).

# #3 Earn 1 stamp for every transaction

## #3 Earn 1 stamp for every transaction

**Business goals:**

* Number of transactions 
* Transaction frequency

**Loyalty mechanism:** Currency

**Description:**

* A stamp-based loyalty campaign, where members earn a single loyalty currency every time they do a transaction with the loyalty card.
* The campaign encourages customers to visit more often and reward shopping frequency instead of the transaction value.
* The campaign is highly effective in industries with a higher shopping frequency e.g. quick-service restaurants.

**Default configuration:**

<figure><img src="https://content.gitbook.com/content/JYxbcM03fnO79kn9uY8G/blobs/SaIRIABaPAkXZEgJWc1S/image.png" alt=""><figcaption></figcaption></figure>

* **Campaign type:** Direct
* **Trigger:** Transaction
* **Rules:**
  * **Conditions**: None
  * &#x20;**Effects:** Give 1 stamp for the transaction *(Add units -> Wallet type: Stamps wallet -> Calculation formula: 1)*

{% hint style="info" %}
**Actionable tips:**

* Set up a limit of transactions per day/hour to avoid fraud and control the costs of the campaign.
* To maximize customer shopping frequency even more, consider allowing members to exchange earned points for time-limited discount coupons for the next purchase.
* Offer different stamp ratios for different tiers, to encourage customers to progress between your tiering strategy.
  {% endhint %}

### Campaign JSON file to import

{% file src="/files/HpFw07WCHJnXNN94PisY" %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.openloyalty.io/playbook/sample-setups/sample-campaigns/3-earn-1-stamp-for-every-transaction.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.