diff --git a/apps/about-apps/components/external-product-catalog.md b/apps/about-apps/components/external-product-catalog.md index 9c345aae..2672656b 100644 --- a/apps/about-apps/components/external-product-catalog.md +++ b/apps/about-apps/components/external-product-catalog.md @@ -100,12 +100,16 @@ Never hardcode sensitive credentials in your configuration. Always store API key After your External Product Catalog component is configured and the app is installed, it can be used within epilot's Journeys. Currently we support seamless integration of the external product catalog into the journey via Product Blocks and Product Recommendations Blocks (beta). -When a journey creator adds a **Product Block** or **Product Recommendations Block** in a journey, they can select the integration as the source for products. Only hooks that are supported for the selected block type will be available (e.g. only `products` hook for Product Block, only `productRecommendations` hook for Product Recommendations Block). +When a journey creator adds a **Product Block** or **Product Recommendations Block** in a journey, they can select the integration as the source for products. Only hooks that are supported for the selected block type will be available (e.g. only `products` hook for Product Block, only `products-recommendation` hook for Product Recommendations Block). This allows the journey to dynamically fetch products and pricing from your external catalog in journeys. +By default, only data from preceding steps (in their defined order) is passed to the steps/blocks data context. While this works for most use cases, you can configure the data context to also include data from subsequent steps, enabling non-linear journey flows. This configuration also makes the data each integration passes to the journey more explicit, lighter and easier to manage. + + + ## Usage in Portals After your External Product Catalog component is configured and the app is installed, it can also be used within epilot's Portals. diff --git a/docs/apps/about-apps/components/external-product-catalog.md b/docs/apps/about-apps/components/external-product-catalog.md index 94c9e5c4..2672656b 100644 --- a/docs/apps/about-apps/components/external-product-catalog.md +++ b/docs/apps/about-apps/components/external-product-catalog.md @@ -28,8 +28,8 @@ They typically rely on your API for the execution of any necessary logic and exp ### Supported Hooks / Catalog Types The interface supports two types of data exchange, depending on the block being used in the journey: -- **Products**: Returns an array of products. -- **Product Recommendations**: Returns a source product and a list of offer products. +- **Products**: Returns an array of products (`type: "products"`). +- **Product Recommendations**: Returns a source product and a list of offer products (`type: "products-recommendation"`). ### Template Variables @@ -100,12 +100,16 @@ Never hardcode sensitive credentials in your configuration. Always store API key After your External Product Catalog component is configured and the app is installed, it can be used within epilot's Journeys. Currently we support seamless integration of the external product catalog into the journey via Product Blocks and Product Recommendations Blocks (beta). -When a journey creator adds a **Product Block** or **Product Recommendations Block** in a journey, they can select the integration as the source for products. Only hooks that are supported for the selected block type will be available (e.g. only `products` hook for Product Block, only `productRecommendations` hook for Product Recommendations Block). +When a journey creator adds a **Product Block** or **Product Recommendations Block** in a journey, they can select the integration as the source for products. Only hooks that are supported for the selected block type will be available (e.g. only `products` hook for Product Block, only `products-recommendation` hook for Product Recommendations Block). This allows the journey to dynamically fetch products and pricing from your external catalog in journeys. +By default, only data from preceding steps (in their defined order) is passed to the steps/blocks data context. While this works for most use cases, you can configure the data context to also include data from subsequent steps, enabling non-linear journey flows. This configuration also makes the data each integration passes to the journey more explicit, lighter and easier to manage. + + + ## Usage in Portals After your External Product Catalog component is configured and the app is installed, it can also be used within epilot's Portals. diff --git a/static/img/apps/external-product-catalog/blocks-data-selection.png b/static/img/apps/external-product-catalog/blocks-data-selection.png new file mode 100644 index 00000000..43352515 Binary files /dev/null and b/static/img/apps/external-product-catalog/blocks-data-selection.png differ