Contact your Iterable CSM to discuss adding Catalog to your plan.
This release introduces Catalog, which allows you to store data in Iterable and query it at send time to customize your campaigns.
With Catalog, Iterable can store information about your organization and projects and use this data to dynamically personalize messages for each recipient of a campaign at send time.
For example, the catalogs associated with an Iterable project might contain data about stores, deals, products, events, services, and locations relevant to your organization.
For each of a campaign's recipients, Iterable queries this data at send time using collections. Then, templates use the data returned by the collections to customize the message.
Historically, this type of personalization at scale required you to host and manage a set of web services. With Catalog, the data lives right in Iterable, so there's need to create and maintain additional infrastructure.
Catalog is an upgrade to Iterable's metadata stores. Metadata store APIs
#metadata Handlebars helper will sunset on March 10, 2020.
For more information about catalog, take a look at the following documents:
- Catalog Overview
- Using Catalog
- Catalog Items
- Defining Data Types for Catalog Item Fields
- Using Collections in Messages
- Catalog Issues and Limitations
- Catalog APIs
- Metadata Stores
- Migrating from Metadata Stores to Catalog
Questions about Catalog?
If you have any questions about Catalog, please contact your Iterable CSM.