For the complete documentation index, see llms.txt. This page is also available as Markdown.

Collections

In this article, you will learn what Collections are, how they work, and how to use them in the Open Loyalty platform.

Collections let you upload a reusable list of values (for example cities, SKUs, or emails). You can then reference that list in campaign conditions. This keeps campaigns fast to build and easy to maintain.


📌 Limits

Check these limits before importing:

  • Collection name: up to 255 characters

  • CSV minimum: 3 values

  • Collection maximum: 1,000,000 values

📥 Import values from CSV

1

Create a collection

  1. Go to Collections.

  2. Click ADD NEW COLLECTION.

  3. Fill in the basic settings.

  4. Set the collection to Active (if needed).

  5. Click ADD COLLECTION.

2

Upload the CSV

  1. Open the collection details (click the collection name).

  2. Click IMPORT VALUES.

  3. Select your CSV file and confirm.

3

Verify the import

After the upload finishes, the collection list refreshes with new values. You will also see a new import job in Imports / Exports.

Update an existing collection

Use Update values to import a new CSV and replace existing values.

➕ Add a single value

1

Open the collection

  1. Go to Collections.

  2. Click the collection name to open its details.

2

Add the value

  1. Click Add single item.

  2. Fill in:

    • Value (required)

    • Description (optional)

  3. Click Save changes.

✏️ Edit or delete values

In the collection details:

  • Use the edit icon next to Value or Description to change it.

  • Use the menu on a row to Delete it.


🎯 Use Collections in campaigns

You can select a collection when configuring supported campaign conditions.

Common places where collections are available:

  • Member fields: building name, flat/unit name, first name, last name, gender, email, phone number, loyalty card number

  • Address fields: street, city, postal code, province, country

  • Program fields: tier, custom attributes, member custom attributes

  • Transaction fields: channel, delivery city, document number, purchase place

  • Product-related conditions: transactions with products that have a specific attribute

Last updated

Was this helpful?