Use case requirements

To run a use case, ensure your project has the required data. During the requirements step, you will:

• Identify the data needed to run a use case.
• Map your data in data mapping.

We understand your business may have its data naming structure. Rather than requiring you to rename your data, Bloomreach Engagement offers a data mapping feature. This allows you to map your existing data to the data required by the use case, enabling you to run it without changing your existing data structure.

Meet the requirements

Before using the selected use case, ensure your project meets the following:

• All icons green: Use case downloads with customized data matching your structure.
• All icons gray: Downloads with default best-practice data; can be updated later.
• Mixed icons: Customized data matches your structure, but some items use default data.

Next steps

Resolve any unmet requirements in Data Manager to align your project’s data structure with predefined naming conventions before downloading the use case. You can adjust optional requirements at any time after download.

1. Go to Data & Assets > Data manager and click Mapping.
2. Map the data.
3. Click Save changes.
4. Return to the use case.
5. Refresh the requirements page.
6. Click Continue.

📘

Note

When the requirements step appears, you can map all the data in your data structure or only the data required for the specific use case you downloaded.

Data mapping

Here's the list of required or must-have events, catalogs, properties, and consents you need to map for use cases to function successfully.

Events

Purchase (Completed): This event should trigger campaigns for active, successful purchases. It is also used to list purchased items and in evaluations.

• Purchase_status: This is used whenever we refer to a successful purchase as a “narrow down” criterion.
• Total_price: Primarily used in evaluations.
• Product_IDs: Used when listing all purchased products.

Purchase_item:

• Product_ID

• Total_price

Add to Cart Event: This event maps the basic action of adding an item to the cart.

• Product_ID
• Total_price

View_item:

• Product_ID

Customer Properties

• Email: Required for any email-related use cases.
• Phone: Required for any SMS-related use cases.

Catalogs

It is essential to have one main catalog being tracked. This catalog is primarily used to visualize products in templates. If there are multiple "main catalogs" (for example, for different countries or brands), select one and edit the email templates once the use case is downloaded. Every email template includes a parameter to specify the chosen catalog.

• Item ID
• Image
• Price
• Title
• URL
• Original Price
• Active Status

Consents

• Newsletter Emailing: This applies if email integration is implemented.
• SMS: This applies if SMS integration is implemented.

📘

Note

Each project's requirements must be set up individually.

Troubleshooting

For answers to common questions about launching and managing use cases, refer to the FAQ section of the Use Case Center.