Adobe Experience Platform

Michael_Soprano · 10/4/25

Could somebody explain me what is in that configuration:

- Surface ?

- and what is Scope ?

To put it here?

Devyendar · 10/5/25

Surface in AJO / Experience Platform

A surface is a logical container or location where personalized content can be injected or replaced. It’s identified by a URI.
It can represent a whole page, a specific app screen, or even a granular element (e.g. div, banner) within a page.
Example: web://domain.com/path/page.html#element
When you define a code-based channel in AJO, you register those surfaces so that your website or app code can match them.
In the Web SDK, when you send an event, you include the surfaces list (URIs matching those definitions) so that AJO knows for which surfaces it should return content.

In short: Surface = where to render the content (on which page or within which element).

Scope in AJO / Experience Platform:

A scope in AJO is used to define which decision you want — i.e. which placement or offer context. It's similar (in purpose) to a Target mbox.
When you create a Decision Activity in AJO, you add one or more placements. Each placement becomes a decision scope.
The long encoded string you saw is a scope token (an encoded representation of the decision + placement context) that the system uses internally.
In your request event (via the Web SDK or Edge API), you supply decisionScopes — these could be simple names (hero-banner) or encoded tokens. The system then knows: “For this scope, which offer(s) should I return?”

In short: Scope = what content/decision to fetch (which placement or offer context).

How They Work Together (Scope + Surface):

In AJO, you configure Decision Activities and Placements. Each placement corresponds to:
- A scope (which decision to resolve)
- A surface URI (where that decision’s content will go)
- You must ensure your placement’s surface URI matches what your code sends.
Your website/app (using the Web SDK) sends an event, including:
- decisionScopes: which scopes to evaluate
- surfaces: which surfaces to return content for
The AEP Edge Network (via AJO decisioning) processes those scopes, determines eligible offers, and returns propositions tied to those surfaces. The SDK then injects or applies the content to the matching surface

Devyendar · 10/5/25

Surface in AJO / Experience Platform

A surface is a logical container or location where personalized content can be injected or replaced. It’s identified by a URI.
It can represent a whole page, a specific app screen, or even a granular element (e.g. div, banner) within a page.
Example: web://domain.com/path/page.html#element
When you define a code-based channel in AJO, you register those surfaces so that your website or app code can match them.
In the Web SDK, when you send an event, you include the surfaces list (URIs matching those definitions) so that AJO knows for which surfaces it should return content.

In short: Surface = where to render the content (on which page or within which element).

Scope in AJO / Experience Platform:

A scope in AJO is used to define which decision you want — i.e. which placement or offer context. It's similar (in purpose) to a Target mbox.
When you create a Decision Activity in AJO, you add one or more placements. Each placement becomes a decision scope.
The long encoded string you saw is a scope token (an encoded representation of the decision + placement context) that the system uses internally.
In your request event (via the Web SDK or Edge API), you supply decisionScopes — these could be simple names (hero-banner) or encoded tokens. The system then knows: “For this scope, which offer(s) should I return?”

In short: Scope = what content/decision to fetch (which placement or offer context).

How They Work Together (Scope + Surface):

In AJO, you configure Decision Activities and Placements. Each placement corresponds to:
- A scope (which decision to resolve)
- A surface URI (where that decision’s content will go)
- You must ensure your placement’s surface URI matches what your code sends.
Your website/app (using the Web SDK) sends an event, including:
- decisionScopes: which scopes to evaluate
- surfaces: which surfaces to return content for
The AEP Edge Network (via AJO decisioning) processes those scopes, determines eligible offers, and returns propositions tied to those surfaces. The SDK then injects or applies the content to the matching surface

Code experience - web channel - Decision Scope vs Surface