diff --git a/gatsby-config.js b/gatsby-config.js
index 2deebd9f99..e07338f9f9 100644
--- a/gatsby-config.js
+++ b/gatsby-config.js
@@ -246,6 +246,10 @@ module.exports = {
{
title: "API reference",
path: "/edge/adobe-journey-optimizer/code-based/api-reference"
+ },
+ {
+ title: "Tutorial",
+ path: "/edge/adobe-journey-optimizer/code-based/tutorial"
}
]
},
diff --git a/src/pages/edge/adobe-journey-optimizer/code-based/tabs/tutorial.md b/src/pages/edge/adobe-journey-optimizer/code-based/tabs/tutorial.md
new file mode 100644
index 0000000000..3e708f3940
--- /dev/null
+++ b/src/pages/edge/adobe-journey-optimizer/code-based/tabs/tutorial.md
@@ -0,0 +1,184 @@
+
+
+#### Java
+
+```java
+final Surface surface1 = new Surface("mainActivity#banner");
+final Surface surface2 = new Surface("secondActivity#promotions");
+
+final List surfaces = new ArrayList<>();
+surfaces.add(surface1);
+surfaces.add(surface2);
+
+// fetch propositions from server and cache in-memory
+Messaging.updatePropositionsForSurfaces(surfaces)
+```
+
+
+
+#### Swift
+
+```swift
+let surface1 = Surface("mainActivity#banner")
+let surface2 = Surface("secondActivity#promotions")
+
+/// fetch propositions from server and cache in-memory
+Messaging.updatePropositionsForSurfaces([surface1, surface2])
+```
+
+
+
+#### Java
+
+```java
+final Surface surface1 = new Surface("mainActivity#banner");
+final Surface surface2 = new Surface("secondActivity#promotions");
+
+final List surfaces = new ArrayList<>();
+surfaces.add(surface1);
+surfaces.add(surface2);
+
+Messaging.getPropositionsForSurfaces(surfaces, new AdobeCallbackWithError>>() {
+ @Override
+ public void fail(final AdobeError adobeError) {
+ // handle error
+ }
+
+ @Override
+ public void call(Map> propositionsMap) {
+ // get the content for the given surfaces
+ if (propositionsMap == null || propositionsMap.isEmpty()) {
+ // bail early if no propositions are found
+ return;
+ }
+
+ // read surface1 propositions
+ List propositionsForSurface1 = propositionsMap.get(surface1);
+
+ // read surface2 propositions
+ List propositionsForSurface2 = propositionsMap.get(surface2);
+ }
+});
+```
+
+
+
+#### Swift
+
+```swift
+let surface1 = Surface(path: "myView#button")
+let surface2 = Surface(path: "myViewAttributes")
+
+Messaging.getPropositionsForSurfaces([surface1, surface2]) { propositionsDict, error in
+ guard error == nil else {
+ /// handle error
+ return
+ }
+
+ guard let propositionsDict = propositionsDict, !propositionsDict.isEmpty else {
+ /// bail early if no propositions are found
+ return
+ }
+
+ /// get the content for the given surfaces
+ if let propositionsForSurface1 = propositionsDict[surface1] {
+ /// read surface1 propositions
+ }
+
+ if let propositionsForSurface2 = propositionsDict[surface2] {
+ /// read surface2 propositions
+ }
+}
+```
+
+
+
+#### Java
+
+```java
+// get the propositions for surface1
+if (propositionsForSurface1 == null || propositionsForSurface1.isEmpty()) {
+ // bail early if no propositions are found for surface1
+ return;
+}
+
+// iterate through items in proposition
+for (final PropositionItem propositionItem: propositionsForSurface1.get(0).getItems()) {
+ if (propositionItem.getSchema() == SchemaType.HTML_CONTENT) {
+ // retrieve the HTML content
+ final String htmlContent = propositionItem.getHtmlContent();
+
+ // use retrieved html content
+ }
+}
+```
+
+
+
+#### Swift
+
+```swift
+/// get the propositions for surface1
+if let codePropositions: [Proposition] = propositionsDict?[surface1], !codePropositions.isEmpty {
+ /// iterate through items in proposition
+ ForEach(codePropositions.first?.items as? [PropositionItem] ?? [], id:\.itemId) { propositionItem in
+ if propositionItem.schema == .htmlContent {
+ // retrieve the HTML content
+ let htmlContent = propositionItem.htmlContent
+
+ // use retrieved html content
+ }
+ }
+}
+```
+
+
+
+#### Java
+
+```java
+// Tracking display of PropositionItem
+// use the same propositionItem object that was used to get the content in the previous section
+propositionItem.track(MessagingEdgeEventType.DISPLAY);
+
+// Tracking interaction with PropositionItem
+// use the same propositionItem object that was used to get the content in the previous section
+propositionItem.track("click", MessagingEdgeEventType.INTERACT, null);
+```
+
+
+
+#### Swift
+
+```swift
+/// Tracking display of PropositionItem
+/// use the same propositionItem object that was used to get the content in the previous section
+propositionItem.track(withEdgeEventType: MessagingEdgeEventType.display)
+
+/// Tracking interaction with PropositionItem
+/// use the same propositionItem object that was used to get the content in the previous section
+propositionItem.track("click", withEdgeEventType: MessagingEdgeEventType.display)
+```
+
+
+
+#### Java
+
+```java
+// Tracking interaction with PropositionItem with tokens
+// Extract the tokens from the PropositionItem item data
+final List tokenList = new ArrayList<>();
+tokenList.add(dataItemToken1);
+tokenList.add(dataItemToken2);
+propositionItem.track("click", MessagingEdgeEventType.INTERACT, tokenList);
+```
+
+
+
+#### Swift
+
+```swift
+/// Tracking interaction with PropositionItem with tokens
+/// Extract the tokens from the PropositionItem item data
+propositionItem.track("click", withEdgeEventType: .interact, forTokens: [dataItemToken1, dataItemToken2])
+```
diff --git a/src/pages/edge/adobe-journey-optimizer/code-based/tutorial.md b/src/pages/edge/adobe-journey-optimizer/code-based/tutorial.md
new file mode 100644
index 0000000000..5705b1a450
--- /dev/null
+++ b/src/pages/edge/adobe-journey-optimizer/code-based/tutorial.md
@@ -0,0 +1,120 @@
+---
+title: Code-based experiences implementation tutorial
+description: This document describes how to fetch, display and track code-based experiences using the Adobe Journey Optimizer extension.
+keywords:
+- Adobe Journey Optimizer
+- Messaging
+- Code-based experiences
+- Tutorial
+---
+
+import Tabs from './tabs/tutorial.md'
+
+# Code-based experiences implementation tutorial
+
+This document describes how to fetch, display and track code-based experiences using the Adobe Journey Optimizer extension.
+
+## Pre-requisites
+
+[Integrate and register Messaging extension](../index.md#implement-extension-in-mobile-app) in your app.
+
+## Fetch and cache the code-based content
+
+To fetch the content for the surfaces configured in Adobe Journey Optimizer campaigns, call the [updatePropositionsForSurfaces](../api-reference.md#updatepropositionsforsurfaces) API . You should batch requesting multiple [Surface](../public-classes/surface.md) URIs in a single API call when possible. The returned code-based experiences are cached in-memory by the Messaging extension and persists through the lifecycle of the app (i.e as long as the app is running). An example of the call is shown below:
+
+
+
+Android
+
+
+
+iOS
+
+
+
+## Retrieve cached propositions
+
+To retrieve the previously fetched content from the in-memory cache, call the [getPropositionsForSurfaces](../api-reference.md#getpropositionsforsurfaces) API with a list of required surface URIs and a completion handler. The completion handler will be invoked with a list of [Proposition](../public-classes/proposition.md) objects corresponding to the requested surfaces, or `AEPError` object if an error occurs.
+
+
+
+If a requested surface was not previously cached prior to calling `getPropositionsForSurfaces` (using the `updatePropositionsForSurfaces` API), no propositions will be returned for that surface.
+
+The following example shows how to retrieve the content for the previously cached surfaces:
+
+
+
+Android
+
+
+
+iOS
+
+
+
+## Using the retrieved propositions
+
+The [Proposition](../public-classes/proposition.md) object returned in the completion handler encapsulates the content specified for the corresponding surface, as well as information needed for tracking interactions with the content. Multiple `Proposition` objects can be returned for a single surface based on the number of campaigns configured for it in Adobe Journey Optimizer. Each `Proposition` object in turn can contain multiple items, represented by the [PropositionItem](../public-classes/proposition-item.md) class, based on how the campaign's content is defined. To access the content, iterate through the list of `PropositionItem` present in the returned list of `Proposition`. The `SchemaType` of the `PropositionItem` indicates the type of content it contains and can be used to determine how to render or interpret the returned content. The `PropositionItem` class contains helper functions to access the different types of supported content.
+
+The following example shows how to iterate through the propositions returned earlier and retrieve the HTML content. Please adapt the solution to suit the needs of your application and use the returned proposition content appropriately.
+
+
+
+Android
+
+
+
+iOS
+
+
+
+## Tracking interactions with code-based experiences
+
+Since the onus of rendering the code-based experience lies with the app developer, you must monitor the desired end user interactions and call the appropriate tracking APIs. To record an interaction with the code-based content, call the [track](../public-classes/proposition-item.md#track) API provided in the `PropositionItem` class. The following code shows two examples of tracking: when the content is displayed to the user and when the user clicks on the content. These examples are for illustrating how to call the track API and not a recommendation on where it should be called. Please examine your app workflow to find the appropriate way to perform tracking.
+
+
+
+Android
+
+
+
+iOS
+
+
+
+### Tracking items from embedded decisions
+
+When Adobe Journey Optimizer campaigns are created with embedded decisions, the server can respond with one or more items based on the number of items requested in the decision. To track these embedded items, the Adobe Journey Optimizer campaign UI provides `item._trackingToken` attributes. When authoring the campaign's content, you would need to embed the provided token as an HTML data-attribute in case of HTML content or JSON attribute in case on JSON content. The following example campaign shows content with embedded decision, where multiple paragraph tags containing image URLs can be returned.
+
+```html
+
+
+ {{#each decisionPolicy.1234567.items as |item|}}
+
+ {{/each}}
+
+
+```
+
+For the above example, the server can return a response with two decision items in the item data within a single `PropositionItem`
+
+```html
+
+
+
+
+
+
+```
+
+Since the embedded items are located inside a single PropositionItem's data, the app developer will need to extract the `data-item-token` when tracking the interactions with the item. The token, along with the other tracking information, will need to be passed to the [track](../public-classes/proposition-item.md#track) API provided by the Messaging SDK. If no tracking tokens are supplied, normal tracking events will be sent. If tracking tokens were used during authoring, it will be assumed that all the corresponding embedded items were displayed. The following code shows an example of calling the track API with tokens.
+
+
+
+Android
+
+
+
+iOS
+
+
