Configure and launch

Transcript

Developers and product managers need a seamless way to build core mobile experiences and partner with marketers to create engaging customer journeys. Adobe Journey Optimizer brings developer and marketer tools together in a single application. As a foundation, Adobe Journey Optimizer supports developers by providing modern, streamlined integrations across mobile channels, such as push messaging, in-app messaging, and content personalization. Not only are technical integrations made easier but Adobe Journey Optimizer provides for increased programmatic control to customize experiences and make sure that they conform to your pixel-perfect expectations. Rest APIs supporting concurrent connections on batch operations are a standard. Headless email and push delivery APIs support industry-leading throughput volumes. These features, along with concise documentation, help you scale as you leverage Adobe Journey Optimizer within the enterprise. Mobile client-side SDKs are provided for all industry-standard platforms including Google Android, Apple iOS, React Native, Flutter and more, as well as common smart TV appliance platforms. These SDKs are compliant with the latest OS developer standards, relied upon by the biggest global brands, and are open sourced for maximum credibility and trust. Integrating SDKs and mobile channels in apps is made easier with powerful debugging and observability capabilities. Adobe Journey Optimizer provides integration event inspection in real time to ensure a quality, reliable implementation every time. Finally, validating experiences before they are shipped is a breeze. With tools such as preview, proofing, and simulation, Adobe Journey Optimizer makes it easy to validate experiences. Even geolocation-based experiences that are hard to test can be easily simulated. -

Transcript

Hi, I’m Travis Jordan on the Adobe Journey Optimizer product team. In this video, I’m going to highlight the guided channel setup that enables customers to rapidly set up and validate web and mobile channels in Journey Optimizer. The time it takes to get up and going with web and mobile engagements in Journey Optimizer can be time consuming, requiring multiple steps across multiple products. The guided channel setup improves the time to value by automating dozens of channel setup across data collection, experience platform, and Journey Optimizer. Now let’s jump over to Adobe Journey Optimizer and take a look. For this demo, I will show you how to quickly set up and validate a push channel notification on a sample iOS mobile marketing app. From the home screen on Journey Optimizer, click Begin. This launches the guided channel setup in a new window. Enter a name for your setup. Note, this name is used to name all your resources that are auto-created in subsequent steps.

For organizations with one or more data stream, you will select an existing data stream. If you don’t have a data stream, no worries, we will auto-create one for you. Next, select a platform. You can choose from iOS, Android, or web.

For this demo, we are setting up an iOS app, so I will select iOS.

Now click Auto-create resources to trigger the creation of resources across data collection, experience platform, and Journey Optimizer. This includes the creation of a mobile tag property and the necessary SDKs and extensions, as well as the creation of a channel configuration in Journey Optimizer. To see a full list of the auto-created resources, please reference the documentation.

Success! Your initial configuration is now complete. You’re ready to move on to the setup of the SDK. Click Setup to get started.

On this screen, I will add the necessary dependencies and code to my app. I will now open Xcode on the right side of my screen to do this. I have already added the package dependencies, so I will skip step one and proceed to step two. To import the required extension dependencies, I simply copy and paste that from AJO to Xcode. For step three, I will copy and paste the initialization code into my app. This code launches an experience platform assurance session upon opening my app. Assurance is a powerful technology used behind the scenes to help test and validate the SDK setup, as well as the channel setup in the upcoming steps. Note, this code is critical for testing and validating your app, but should be removed before pushing your app to production. Now that the code has been added to my app, I will click Build in Xcode to simulate the app experience. As you can see, I am prompted to connect to Assurance once my app launches. Click Allow Notifications and then Connect. Now you can see that my app appears in the list of available devices. Click Connect once more.

And there you go. I can now see that my device is connected to Assurance and that the mobile SDK was set up correctly. The green dot and Adobe icon in the upper right corner of my app indicates that I am indeed connected to Assurance and ready to test and validate my app. Click Finish to wrap up and move on to the final step. Lastly, I will add and validate the desired channels for Journey Optimizer. You can add multiple channels for each platform as needed. For this demo, I will just add and validate a mobile push notification. To do this, click Add.

I will first need to retrieve the device token by copying and pasting this line of code into my app.

Now I need to add the push certificate, the key ID and team ID for my app. If you are unfamiliar with these configurations, please refer to the documentation from the tooltips for more information. After rebuilding the app, I will click Send Push Message to ensure everything is working end to end. And there you go. I can now see a sample push message on my device with a notification informing me that everything is properly set up. Click Finish to close this window.

This setup is now complete. I will now share the name of the channel configuration with the team member responsible for creating campaigns and journeys in Journey Optimizer. To do this, click Share. Now I can close this out and exit channel setup.

You are now on your way to creating web and mobile experiences in Adobe Journey Optimizer. To make a connection between this setup and the creation of the marketing content, I simply select the name of the channel configuration that was auto-created under Actions in the campaign or journey UI. Now you are off and going.

This concludes this demo on Guided Channel Setup in Journey Optimizer. Thank you.

1. SDK versions and extensions not aligned with channel requirements

What you’ll notice

• Push or in‑app activities do not reach the device.
• Guided Channel Setup or channel validation fails.
• Assurance shows missing Journey Optimizer, Edge, or Identity extensions.

What to check

• Are you using the minimum Mobile Core and Journey Optimizer extension versions required by Guided Channel Setup?

• In Assurance, under extensions and events:

  • Do you see the expected extensions loaded?
  • Are events being sent to the Edge Network and acknowledged?

How to fix

• Upgrade to the supported Mobile SDK and Journey Optimizer extension versions.
• Rebuild the app, reconnect to Assurance, and re‑run Guided Channel Setup.

See: Set up mobile and web

2. Misconfigured datastreams or datasets

What you’ll notice

• Events or push tracking batches fail in Platform datasets.
• Data ingestion errors (for example, “Updates are not supported for events”).
• Push or in‑app reports show little or no tracking.

What to check

• Did anyone change system schemas or datasets created for Journey Optimizer tracking?

• In your datastream:

  • Are experience events mapped to an event dataset?
  • Are profile attributes mapped to a profile dataset?

How to fix

• Do not edit system datasets/schemas created by AJO.
• Correct the datastream mapping (events → event dataset, profiles → profile dataset).
• Prefer Guided Channel Setup or the documented datastream steps instead of ad‑hoc changes.

See: Push Notification flow in Adobe Journey Optimizer

3. Missing or inconsistent identity and consent

What you’ll notice

• Journeys don’t trigger as expected for app users.
• Personalization doesn’t match the user’s behavior in other channels.
• Events appear in Experience Platform, but profiles look fragmented.

What to check

• Is Identity for Edge Network implemented and sending a stable primary ID (for example, login ID)?

• Is Consent for Edge Network implemented and updated when preferences change?

• In Assurance:

  • Do outbound events include consent values?
  • Do they include ECID and your primary IDs consistently?

How to fix

• Implement or correct Identity for Edge Network in the app.
• Implement Consent for Edge Network and connect it to your app’s consent UI.
• Retest in Assurance until identity and consent appear on all relevant events.

See: Implement consent for Platform Mobile SDK implementations

4. Push token registration and tracking not wired correctly

What you’ll notice

• Users never receive push notifications, even though campaigns or journeys run.
• Push reports show no opens, dismisses, or interactions.

What to check

• Does the app register the push token with the Journey Optimizer extension:

  • On first install?
  • After each app update?
  • Whenever the OS refreshes the token?

• When a user opens or dismisses a notification, do you see tracking events in Assurance?

How to fix

• Add or correct the code that:

  • Registers the token via the Journey Optimizer mobile extension whenever it is created or refreshed.
  • Sends push interaction events (open, dismiss, custom actions) via the Mobile SDK.

• Use Assurance to confirm registration and tracking events are firing as expected.

See: Push Notification flow in Adobe Journey Optimizer

5. In‑app messages or content cards not displaying

What you’ll notice

• In‑app messages or content cards never appear, despite active campaigns or journeys.
• Reporting shows 0 impressions.

What to check

• Are the Journey Optimizer mobile messaging / in‑app extension and Messaging SDK installed and registered in the app?

• In your tags configuration:

  • Do you have rules that trigger requests on the correct events (for example, screen views or custom events)?

• In Assurance:

  • When those events fire, do you see in‑app or content‑card decision requests going out?
  • Do you see responses coming back from the Edge Network?

How to fix

• Install and register the required messaging extensions.

• Add or correct rules that trigger decisions on your target events (screens, custom events).

• For content cards, ensure you:

  • Fetch cards via the Messaging SDK APIs.
  • Render them in your UI.
  • Track interactions back via the SDK.

See:

• Create and send in‑app messages
• Configure content cards support in Mobile SDK