adobe / adobe/xdm

Need Auxiliary Properties to be part of Experience Event Schema

Open
#545 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
266
Forks
380
Avg merge
5d 8h
Merged PRs (30d)
9

Description

Audience Manager accepts auxiliary properties from other solutions and third party providers which are basically key value pairs and do not have fixed set of keys (within a provider or across providers). These properties can be best captured as a map with in an instance of XDM. This will help in providing more context and information to the current instance of XDM.
This need not be limited to Audience Manager requirement but generic requirement as a whole.

## What are the schemas that are affected by the issue
Experience Event (Others later)

## What are examples of products that are impacted by the issue
Adobe Audience Manager
Adobe Cloud Platform

Contributor guide

Open the contributing guide

Research direction

Start by locating the Experience Event schema and reviewing how it currently represents properties and maps. Define how arbitrary provider-supplied key-value pairs should be represented without fixed keys, then confirm the schema accepts the proposed auxiliary properties and document the affected Experience Event behavior.

Written by the indexing model from the issue text.

Assessment

Domain
data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.