[MKTAUT-8] [RESEARCH] Functionality to get external traits into MGNL Created: 25/Jul/19  Updated: 17/Apr/20  Resolved: 14/Apr/20

Status: Closed
Project: Marketing Automation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Ilgun Ilgun Assignee: Chuong Doan Huy
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 4d 3h
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: Personal traits
Sprint: Add-Ons 35
Story Points: 8

 Description   

AC

  • Research External systems (Marketo and Salesforce) to figure out what kind of traits they provide
    • Is our Segments capabilities sufficient? meaning what Marketo provides, can we consume them right away or do we need something else?
    • Do they have an API to get those segments to our side?
      • Are those APIs expose what we need or not?


 Comments   
Comment by Laura Delnevo [ 31/Mar/20 ]

Does Mgnl fetch from the ext system just the traits (gender), and when visitors visit Mgnl site we keep check traits on the ext system? Or does Mgnl fetch those visitor profiles and store them on Mgnl side (when we check traits, we don't go back to the ext system anymore)?

Comment by Chuong Doan Huy [ 13/Apr/20 ]

Hi ilgun, ldelnevo, here is some information after research :

  • Marketo and Salesforce traits are different from Magnolia's traits. While Magnolia traits are using browsing information (cookie, ip...) or general information (date) to serving different variants of pages, components...Marketo and Salesforce's traits based entirely on FORM's FIELDS, for example gender, age, email...which user already input
  • Marketo's and Salesforce's filtering based on generic comparison like : [FieldA]  [less than, equal to, greater than, contains...]  [ValueB] while Magnolia is using specific hardcoded condition like country equals to 'abc' or date from/to
  • Marketo is providing API to get overall information of created traits (segments), but not the detail how the condition/rule of traits are implemented, for example we can get segments named 'Geographical' which have Asia, Europe...but no information how Asia is defined although in their system we define a list of country in the Asia type.
  • Salesforce is also not providing API to get those traits ( they see them like a filter to their form's list view)

Feel free to give your ideas and how to proceed next, thanks

Generated at Mon Feb 12 10:11:23 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.