What it is & the business problem it solves
Before any module of Inspire - AI Personalization Engine can produce results, your customer data, website events and product catalogue must reach Inspire in the right shape. This page describes the one-off onboarding that every Inspire customer goes through. The settings of the Data module, the foundation module that loads your data for all other modules, are described on the Data page.
Most "no results" or "poor results" problems trace back to this setup: a missing event type, product IDs that do not match the product feed, or a module that was never scheduled.
How it works
Inspire reads data from your customer data platform (CDP, where customer profiles and events are stored) and from CM Product Feed (your product catalogue, also called the item feed). The Data module loads both every 30 minutes by default and prepares them for the other modules. Results are written back to your customer data platform, the Product Feed or an analytics screen.
CDP and CXP in short
|
|
CDP |
CXP |
|---|---|---|
|
What it is |
CM's Customer Data Platform: customer profiles with the events that belong to them |
CM's customer experience platform: customers, orders and other things are stored as connected objects, with events that update them |
|
Standard events (Purchase, Add to cart and so on) |
Set up by the Retail & Ecommerce adapter, included in onboarding: nothing extra to buy or configure |
The adapter does not apply. Templates (installable configuration presets) are used instead |
|
Where Inspire results go |
Properties on the customer profile |
Events sent to a CXP event definition, which update the customer in CXP |
|
Setting that points to it |
Profile connection settings and the delivery method of a module ("cdp") |
Profile connection settings and the delivery method of a module ("cxp") |
The word cockpit means Inspire's front-end tooling for adjusting the business rules behind your predictions. All modules work on both CDP and CXP.
Onboarding steps
-
Customer data platform, profile type and standard events. On CDP you need a CDP tenant (your CDP environment) with a customer profile type. On CXP you need a CXP tenant, set up with Templates (the CXP equivalent of the adapter). These standard events must arrive:
|
Event |
Typical source |
Used for |
|---|---|---|
|
Product view (product detail page) |
Webtracking |
Recommendations, triggers, profiling |
|
Add-to-cart |
Webtracking |
Triggers, recommendation engines, profiling |
|
Remove-from-cart |
Webtracking |
Triggers (item removed from cart) |
|
Begin-checkout |
Webtracking |
Checkout triggers; stops cart reminders |
|
Purchase lines (one event per order line: product ID, price, quantity, order ID) |
Webshop or back office |
Everything that uses purchases |
On CDP, events must use CDP's standard event types, which the Retail & Ecommerce adapter sets up during onboarding. An event type created under a custom type is silently ignored by Inspire. A generic page view is not used, only product views.
-
Product Feed. Load your catalogue into CM Product Feed. Follow Product Feed Best Practices (the leading page on how to set up your feed). The column names below are the ones Inspire recognises:
-
-
The product ID in the feed must be identical to the product ID in your web events and purchase lines.
-
Provide at least a name, category, image, price and availability, and a brand if you want brand-based rules. Inspire recognises these attribute names (not case sensitive): name or title; category or categories; image_url or image_link; description or short_description; price or regular_price; availability as
isAvailable,is_available,available,availabilityor any name starting withavailability_. Any other attribute (for example brand) keeps its own name and can be selected in module settings. The full list and two pitfalls (availability counts presence, not value; price must be numeric) are on the Data page. -
Category is used by fallbacks, brand by boosts and filters, price by price-drop triggers.
-
For product variants (sizes, colours), an attribute that groups variants into one product (for example a parent ID) is optional, but needed if modules should treat the variants as one product (the item grouping level setting).
-
-
Profile connection settings (done by CM). In the cockpit, CM creates a profile for you: a container, for example per brand or country, holding the shared connection settings that every module instance in it uses: your CDP tenant, profile type, product catalogue and access token. If results should also go to CXP, CM adds the CXP tenant and token. You do not set these on the Data module and you do not have to create a separate read token for the Product Feed.
-
Data module settings. See the Data page. Up to two years of history are loaded on the first run; events are retained for 730 days.
-
Delivery per module (done by CM). For each module that writes to your customer data platform, CM sets up where the results go: on CDP the event type the module sends, on CXP the event definition it sends, and maps the fields to customer properties. The results then appear on the customer profile and can be used in segments, workflows, MMC email campaigns and Web Personalization.
-
Channel apps.
-
-
For Attribution: Email Campaigns and/or Campaigns, whose delivered and clicked events flow into your data platform.
-
For A/B Testing: Web Personalization with at least two active variants, the A/B Testing app, and the Webtracking click events published.
-
-
Attribution account (done by CM). CM registers your account in the attribution results service before the first Attribution run. You find the attribution results in the Campaigns app, with the statistics of the campaign.
-
Schedules. Most modules are not scheduled by default and only run once a schedule is set. At go-live, set a schedule for every module you use. See Personalization Modules, section "Schedules".
Example use cases
|
Scenario |
Channel |
Required products |
|---|---|---|
|
A fashion retailer starts with abandoned-cart emails |
MMC email campaign via CDP workflow |
CDP or CXP, Webtracking (view, add-to-cart, remove-from-cart, begin-checkout), purchase lines, Product Feed, Data, Behavioral Trigger |
|
A DIY retailer adds a "you may also like" carousel |
Web Personalization |
Above + Base Item Item Recommender, Contextual Product Recommendation, Web Personalization |
|
A pet-food webshop measures email revenue |
Attribution results (Campaigns app) |
CDP or CXP, purchase lines, MMC Email Campaigns, Data, Attribution, account registration by CM |
What you can configure
Onboarding itself is mostly done by CM. What you can influence:
|
Setting |
What it does |
Default |
When to change |
Who can change |
|---|---|---|---|---|
|
Product Feed content |
Product IDs, names, categories, brands, prices, availability |
Your feed |
Before go-live and when your catalogue changes |
You |
|
Data module settings (Enable Product Feed, Enable Filter Events, Filter Attribute Mappings, Data Reload Cron, Enable Transformer Loader, Force Event Log Rebuild, resources) |
Control what the Data module loads and when |
See the Data page |
See the Data page |
Standard or Expert per setting |
|
Module schedules |
When each module runs |
Not scheduled for most modules |
At go-live |
Standard or Expert per module |
|
Profile connection settings |
Connection to your CDP or CXP tenant and catalogue |
Set by CM |
When you add a brand or country |
CM |
Settings marked Expert need expert rights; both CM staff and customer admins can hold them, and you request them through your CM contact person. How expert settings, setup versus tuning settings, and preview and publish work is explained on Personalization Modules.
Prerequisites & required CM products
|
Product |
Needed for |
|---|---|
|
CDP, or CXP |
All modules |
|
On CDP: Retail & Ecommerce adapter (standard event types; included in onboarding) |
All modules |
|
On CXP: Templates (the adapter does not apply) |
All modules |
|
Webtracking (CM's website tracker) |
Web events: recommendations, triggers, profiling |
|
Product Feed |
Recommendations, triggers, Item Enricher, Attribute Tagger, Persona Generation |
|
MMC Email Campaigns / Campaigns |
Attribution; email delivery of results |
|
Web Personalization + A/B Testing app |
A/B Testing; on-site recommendations |
|
Cockpit access |
Managing modules |
|
Attribution account registration (by CM) |
Attribution |
Packaging tier
The Data module is required for every Inspire module. It is a Pro module: it is included wherever Inspire is available, which is from the MMC Pro package upward (not in Basic or Advanced). See Inspire - AI Personalization Engine for the module table and MMC package mapping.
Data requirements
-
Standard events and purchase lines as listed in step 1; Product Feed with matching IDs and the attribute names in step 2.
-
Up to two years of history is loaded; events are kept for 730 days. History that was never sent to your data platform cannot be added later, and the export that Inspire reads can lag a few hours behind real time.
-
Minimum volumes are per module and are listed as technical minimum requirements on each module page; the Data module itself has no minimum.
How to check it works
-
The Data module's run history in the cockpit shows a successful run about every 30 minutes.
-
On CDP, check that test events arrive on the standard event types (not a custom type).
-
Compare a few product IDs from purchase lines and product views with the Product Feed: they must be identical.
-
Once a module runs, check its event viewer (if it has one), its profile properties or its Product Feed attributes.
Limitations & common pitfalls
-
A custom event type is silently ignored: results stay empty without an error.
-
Product IDs in events that do not match the feed (for example variant ID versus parent ID) give poor or empty recommendations.
-
Conversions tracked outside your data platform leave Inspire with only views.
-
Changing how an event type is read affects only new data until a Force Event Log Rebuild is run once.
-
Modules whose schedule is "not scheduled" never run until a schedule is set.
-
Attribution fails on its first run if the account has not been registered by CM.
-
A/B experiments with only one active variant record nothing.
-
Web Personalization click events must be published in Webtracking, otherwise clicks are missing.