Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MVP #1

Open
7 of 33 tasks
jalagari opened this issue Jul 4, 2024 · 0 comments
Open
7 of 33 tasks

MVP #1

jalagari opened this issue Jul 4, 2024 · 0 comments

Comments

@jalagari
Copy link

jalagari commented Jul 4, 2024

Use Case

  • Banner - new or existing vistor
  • Nudge -- Customize message
  • Interest rate

MVP - RTCDP

Segment notion.

  • Create the Form Template with audiences Dropdown.
  • In every form this audiences needs to be included
  • Segment dropdown should be by default hidden in Authoring & Runtime.

Profile Field

  • Ability to select field as part of profile.
  • xdmBind Ref details
  • In this approach author need to aware of XDM Scheme
  • Alternative — it will be sent via data and need take care in data stream.
  • Transformation -- Custom function for masking

Scheduler

  • Update the Segment dropdown enum based API Response

Runtime

OOTB Audiences Resolver

  • Resolve Audiences and updated prefill data
  • Audiences Preview option

RTCDP Integration

  • Load web sdk
  • Gather all profile fields and add listener.
  • sendEvent integration
  • Set segment field value.

Fast follow-up

Personalisation Extension

  • Capture properties (label, placeholder, show, enable, readOnly, help text and value, ) per segment
  • On save create rule (when segment is changed & segment == “” then …)
  • Also profile on field change or load

MVP — AJO- Decision management

  • Define custom schema for Form Field (like dom-action) - fieldId, content, type ( enum, value),
  • Custom Placement for form field or above?
  • Evaluate how to surface form field selector in Offer.
  • Can we define Channel?

Runtime

  • Automatic rendering
  • Manually rendering – Listen to response and use forms API to update

MVP -- Non AEP

Default Segments

  • Device -- mobile, desktop,
  • Visitor - new or returning-visitor
  • GeoLocation
  • UTM parameters

Extending Segments

  • Similar to Edge Delivery AUDIENCES
  • This segments need to evaluated before form load and include it in prefill data
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant