Map inriver fields to Optimizely with confidence

Start with a compatible connection

Select a destination field in Field mapping, then choose or drag an inriver source field onto it. Compatible values can be copied directly. When formats differ, choose an available conversion and supply its settings.

For example, a Season list cannot be copied straight into a numeric Search Boost field. Map its codes to explicit numbers instead. The editor checks destination limits where the shop model provides them, such as a range from 1 to 5.

Choose how the value should be converted

Common conversions are built into the editor. You choose the rules rather than relying on the server to guess a format.

• Numbers: read 12,5 as 12.5 using the Swedish number format. Whole-number fields reject fractional values.
• Yes/no: define accepted values, such as ja;yes;1 for true and nej;no;0 for false.
• Dates: choose an exact format, such as yyyyMMdd or yyyy-MM-dd.
• List values: use readable CVL names or keep their codes. Several list names can be joined as text.
• Specific values: map a source code to an explicit text, number or yes/no result.
• Text cleanup: trim spaces, replace text, remove a prefix or suffix, and optionally limit length.
• Formatted text: turn plain text into an encoded paragraph for an Optimizely formatted-text field.

Preview examples from inriver automatically

Open a connection to load examples without typing product IDs. The preview fetches values from up to five matching records and shows their available language rows. Change conversion settings to see updated results, or refresh to load current values.

You can also try your own sample value. The preview checks these examples only; a successful preview does not prove that every product has a valid value. Sync applies the same conversion rules to each record it processes.

Understand formatted text and HTML

When a plain description is mapped to formatted text, the result includes paragraph markup. The preview shows readable text by default. Choose View HTML to inspect the stored markup.

Accented characters may appear as character references in HTML while displaying normally as text. Source text is encoded, so text that resembles a script is treated as content. Your shop controls the final typography and layout.

Handle missing or unexpected values deliberately

An unsupported value produces an explanation instead of silently becoming zero or false. You can configure an explicit fallback for a parsing failure, but the fallback must also pass the conversion and destination checks.

An absent source field and a present empty value are different. Review how empty values affect each connection, especially required fields. Without a valid fallback, a conversion error marks the affected record for retry before its catalog write.

Check languages and supported rules

Localized source values need a destination with values per language. The languages selected in Setup apply to preview and sync. Choosing one translation for a shared destination field is not currently supported.

Each field connection supports one conversion. Combining several source fields, following related records, chaining conversions and applying different business rules per market are not currently available in this editor. Check that your required mappings fit before using them for a live shop.