Contact your Iterable CSM to discuss adding Catalog to your plan.
When sending messages to your users—using any medium—it's almost always necessary to include information about your organization's products, places, events, or services. With Catalog, you can store this information directly in Iterable and use it to personalize the messages you send.
For each of their recipients, campaigns can use collections to search, at send time, the information stored in catalogs. Collections match users with catalog data based on their interests, preferences, locations, and historical activity—anything stored on their Iterable user profile.
Historically, this type of personalization at scale required your organization to host and maintain a set of web services that could be queried for each of a campaign's recipients. With catalogs, there's no additional infrastructure required: Iterable hosts the data and queries it while sending a campaign.
To learn more about Catalog, read the documents mentioned below.
Using Catalog details how Catalog works, describes how it relates to data feeds and metadata stores, and provides instructions for creating, viewing, and deleting catalogs.
Catalog Items provides an overview of how to add, update, and delete catalog data.
Defining Data Types for Catalog Item Fields
Defining Data Types for Catalog Item Fields takes a look at how to set the data types (string, long, double, geo_location, object, date, or boolean) for the fields in a catalog item. Collections can only search data that has been given an explicit data type, making this a crucial step.
Collections search catalogs, finding items relevant to static search criteria or the fields on a user's Iterable profile. Additionally, they have powerful capabilities such as geo location searches: finding catalog data associated with a location close to the user.
Collections describes how to use the collection builder to create and edit collections that find the precise catalog data needed by a campaign.
Using Collections in Messages
Using Collections in Messages demonstrates how to reference the data stored in a catalog when sending messages with Iterable.
Catalog Issues and Limitations
Catalogs, catalog items, and collections have various limitations and known issues, as listed in Catalog Issues and Limitations.
For information about APIs that can be used to work with catalogs and catalog items, take a look at the following documents:
Metadata stores are the precursor to Catalog. This document describes their basic usage.
For information about metadata store APIs, take a look at Iterable's API documentation.
Migrating from Metadata Stores to Catalog
To learn how to migrate from metadata stores to Catalog, read Migrating from Metadata Stores to Catalog. This document discusses API and Handlebars differences between metadata stores and Catalog, and describes how to modify metadata stores so that they can be used with collections.