In this article I’ll talk through an example of a multi-solution use case that gets CDP, e-mail, optimisation & analytics working in harmony. I’ll be using Tealium AudienceStream, Adobe Campaign, Adobe Target & Adobe Analytics in this particular example, but the theory remains the same regardless of which vendors you are using.

#1 Use Case Hypothesis

Every CDP project will have a handful of initiatives that have been identified, based on existing business challenges or opportunities to mature previous success cases. However, it is quite easy to spend too long at the initiative level in a project, where it’s still a high-level discussion about…

This is a simple, but not exhaustive, checklist of what to think about when it comes to integrating your Adobe products. It’s split out based on each product, so there’s a bit of repetition, but I wanted to make it easy regardless of what your product focus is

#1 AEM

Launch Integration
- create an IMS configuration using Adobe I/O, which then means you can link your AEM instance with your Launch property

Target Integrations - create Experience Fragments in AEM, which can then be utilised directly via the Target VEC - connect Assets with Target via Scene7, allowing for use of…

This short article will provide a brief introduction to Adobe’s new On Device Decisioning capabilities. There is some very useful documentation available here that explains when to use On-device vs existing Edge decisioning, so my main focus will be providing some answers to questions that have come up quite regularly since the announcement, as well as a quick run through of the implementation basics.

#1 What you should know

Availability
The good news for the server-side fanatics amongst us is that On Device Decisioning is available in the latest Java & Node.js SDKs. …

The Adobe I/O Runtime is a serverless platform, which allows you to deploy an application that can to respond to events and then take action. It is integrated with both Adobe I/O Events and API Gateway, which means that it’s very easy to subscribe to events dispatched by Adobe solutions and then subsequently communicate with a wide range of Adobe APIs. You’re not only limited to Adobe APIs though; for example, I could subscribe to the Privacy Service Job Complete event and then set up a simple application that e-mails the information to relevant stakeholders.

A while ago I wrote…

It’s simple enough (with the right admin credentials) to get an overview of which users can access a particular account/container, as well as what level of access they have. However, there’s no way of getting a simple view of access levels for all users across all accounts & containers, which means it’s not that easy to monitor who has access to what.

Fortunately, all of the information that’s required to build this view is available via the GTM APIs. The steps below explain how to it’s possible to generate a user access table, which can then be exported in CSV…

There has been a growing sense of excitement around the capabilities of Adobe’s new Experience Platform as more and more information becomes available. What has quickly become apparent is that there are a number of key areas to think about, ranging from data schema design and data governance through to identity management and activation channels. However, in this post I’m going to focus on the very beginning of the data supply chain, and more specifically, what steps are needed in order to migrate to the Web SDK.

#1 Design Overview

The requirements for the project are very simple — migrate to the Web…

Having worked with a number of different clients that use Launch, it’s often the case that there isn’t one central Launch property that controls all of the web platforms. For larger companies with a web presence across many markets it’s normal to see separate properties for each market/region; similarly, it can make sense to separate properties by product/development team if ways of working, technology, release cycles etc differ significantly.

Whatever the reason, managing multiple properties in Launch can significantly increase the time spent maintaining everything. For example, if you have added a new property to your data layer across 25…

#1 Overview

This post adds to the Adobe Experience Platform SDK series, so if you’re just getting started on the implementation journey then I’d recommend starting here. QA is an essential part of any implementation project, and mobile app validation is often more challenging to co-ordinate, so Griffon has been a timely addition.

There are no pre-requisites for the implementation phase but, in order to access the Griffon UI, you will need to fill out the request form here. The steps below cover implementing Griffon in your app, connecting to a Griffon session, understanding the basics of the UI and exporting data…

I started looking into Launch Audit Events a while back, which then lead me to the topic of creating Callbacks using the Launch APIs. The general idea is pretty simple — you subscribe to one or more events based on a combination of resource type (e.g. property) & event (e.g. updated) and specify an endpoint for the request. …

If you have a steady stream of GDPR requests that need processing, using the Privacy UI can quickly become pretty time consuming. Fortunately Adobe’s Privacy Service is also available via APIs, which got me thinking about what could be done to speed up a fairly time consuming manual process.

The end result of that thinking time was a pretty simple UI but one that has reduced the processing time by more than 50%. This article will give you an overview of the different component parts and the process of joining them all together.

#1 Design Overview

The screenshot at the top of the…

Alex Bishop

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store