[MKTAUT-138] Propose new submit form feature for creating event "Fill out form" in Marketo Created: 13/May/22  Updated: 06/Jul/23  Resolved: 23/May/23

Status: Closed
Project: Marketing Automation
Component/s: None
Affects Version/s: 1.0.3
Fix Version/s: 1.0.4, 2.0.0

Type: Improvement Priority: Neutral
Reporter: Oanh Thai Hoang Assignee: Oanh Thai Hoang
Resolution: Fixed Votes: 1
Labels: DevX_AuthX_Support
Σ Remaining Estimate: 0d Remaining Estimate: 0d
Σ Time Spent: 3d 3h Time Spent: 1d 3.5h
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: PNG File curent-submited-data.png     PNG File image (1).png     PNG File image.png     PNG File marketo-api.png     PNG File submit-the-same-email.png    
Issue Links:
Cloners
Relates
relates to MKTAUT-155 Release 1.0.4 Closed
relates to MKTAUT-156 DOCU: Provide a user guide for submit... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MKTAUT-149 Implement Sub-task Closed Oanh Thai Hoang  
MKTAUT-150 Review Sub-task Closed Thuy To  
MKTAUT-151 piQA Sub-task Closed Thuy To  
MKTAUT-152 QA Sub-task Closed Thuy To  
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: AuthorX improvements
Sprint: DevX 38
Story Points: 3
T-Shirt Size: X-Small
Team: DeveloperX
Work Started:
Approved:
Yes

 Description   

Problem: When submitting marketo form with the same email that used to submit before. Marketo will recognize that is updated lead and only updated changed data in 1 recored instead creating a new record data in Marketo server.

See marketo document:

Since our connected don't set "action" in json body so it will be set as action defaults to createOrUpdate due to Marketo document. See our submited json:

 

Another problem is missing 'Fill out form' events as below https://jira.magnolia-cms.com/browse/MKTAUT-138?focusedId=306651&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-306651

Solution: Propose new config in yaml to recognize user choice of action for marketo and new Submit form implementation for creating "a "Fill out Form" activities



 Comments   
Comment by Tomáš Gregovský [ 17/May/22 ]

From user point, when submitting form currently: my data in Marketo gets updated, but there is no event "Fill out form" in Marketo:

versus (when submitting html embedded code):

this is key functionality for our marketing team since there are actions connected to "fill out form" events.

thank you

Comment by Michael Schneider [ 20/Jun/22 ]

Hi oanh.thai - just curious, can you provide a status for this ticket? Any progress?

Thanks,

Michi (from Marketing)

Comment by Oanh Thai Hoang [ 05/Jul/22 ]

Hi mschneider, Sorry for late reply. I proposed PR already, but this ticket need to be checked over (add to backlog, discovery, plan release...) and this module is owned by AuthX team . Would you mind contacting PM of AuthX team so they can consider prioritize this ticket just in case. Thank you Michi

Comment by Michael Schneider [ 19/Jul/22 ]

Thank you dmaslanka, I will get back you you after the company trip then  

Comment by Michael Schneider [ 16/Sep/22 ]

Hi dmaslanka ,

just following up here on this ticket. Any new progress?

Thanks,

Michi

Comment by Michael Schneider [ 29/Nov/22 ]

Hi dmaslanka ,

Again, do you have an update on this? We would like to use this going forward for the corp-web...

Thanks,

Michi

Comment by Michael Schneider [ 30/Jan/23 ]

Hi dmaslanka and ldelnevo ,

as agreed, here are a couple of pain points/advantages we expect from the Marketo extension on our corporate setup:

 

Marketo forms via extension

The use of the extension over the current implementation via simple HTML embed of Marketo form would help us to:

  • Centralize the form management via the Forms app (currently, we would need to change the HTML code on every page with a form manually)
  • Enable a feature of Pre-filled form Marketo on landing pages. So we can improve the user experience by showing already existing data or even hiding fields we already know. (WEBSITE-2748)
  • We need more flexibility in terms of form fields we need. In the Marketo extension, it is possible to choose the form fields individually, which can be helpful in certain campaigns.
  • There might also be better performance vs. the HTML version (needs to be properly tested)

 

Thanks,

Michi

Comment by Michael Schneider [ 16/Feb/23 ]

Hi again dmaslanka

Progressive Profiling as an additional advantage, especially in a 1st Party Cookies:

Progressive profiling is a method of gradually collecting data on leads with the help of dynamic web forms. Each time a user interacts with a new form on the website, they are asked to fill in different pieces of information.

https://userguiding.com/blog/progressive-profiling/ 

Is there any progress? We would like this one to be fixed if possible in Q1. How can we speed up the process here?

Thanks

Michi

Comment by Michael Schneider [ 03/May/23 ]

Hi dmaslanka , ldelnevo & plendenmann / pierre-yves lendenmann 

Is there any update on this ticket? Do you consider it now, after the SaaS focus was shifted?

Thanks for your feedback,

Michi

Comment by Michael Schneider [ 09/May/23 ]

Hi czimmermann & ldelnevo

thanks a lot for looking into this. Can you already see when it can be implemented?

(We would need another backend deployment in order to use it on corpweb).

Thanks for your update.

/M

Comment by Oanh Thai Hoang [ 10/May/23 ]

Sorry for late response. I haven't had time yet for looking into this ticket but I will start  this ticket today. czimmermann 

 

Comment by Oanh Thai Hoang [ 10/May/23 ]

Discovery output: 

The "Fill out form" activity in Marketo when submit form from Magnolia is missing because our connector call different API endpoints.

Reason: Currently our extension submit lead via this endpoint https://developers.marketo.com/rest-api/lead-database/leads/#create_and_update. in  this class . but it won't create event "Fill out form" in Marketo like above comments from tgregovsky  

Suggestion: Follow marketo document. To create a “Fill out Form” activity, our connector should submit via another rest api instead. See https://developers.marketo.com/rest-api/lead-database/leads/#submit_form. So we can create a new SubmitForm implementation for supporting create Fill out form. Propose PR here

Comment by Oanh Thai Hoang [ 10/May/23 ]

Hi mschneider, cc: ldelnevo czimmermann : This ticket is created due to report from tgregovsky about missing 'Fill out form' events when submitting form via Magnolia marketo marketing automation. It does not related to Progressive profiling feature. Would you minding create another ticket and put your use case, requirement there. Thank you

Comment by Michael Schneider [ 10/May/23 ]

Hi oanh.thai , thanks for fixing this; highly appreciated.

About the progressive profiling feature, that's something we looked into and don´t need at the moment. 

We should entirely focus on fixing this missing form fill-out events in the extension.

Thanks,
Michi

Comment by Oanh Thai Hoang [ 23/May/23 ]

This ticket has been closed. Just for your information about how to config a new submit form implementation that create 'Fill out form' event.

 

Instead of config: `submitBy: info.magnolia.mkautomation.marketo.forms.SubmitBy`, pls change your config to `submitBy: info.magnolia.mkautomation.marketo.forms.SubmitForm`

 

Here is example configuration: 

class: info.magnolia.mkautomation.definition.DefaultMarketingFormDefinition
type: marketo
enabled: true
implementation:
  forms:
    all: info.magnolia.mkautomation.marketo.forms.All
    byId: info.magnolia.mkautomation.marketo.forms.ById
    byName: info.magnolia.mkautomation.marketo.forms.ByName
    submitBy: info.magnolia.mkautomation.marketo.forms.SubmitForm
  leads:
    searchBy: info.magnolia.mkautomation.marketo.leads.SearchByFilterType
connection:
  baseUrl: https://641-OQJ-158.mktorest.com
  authUrl: https://641-OQJ-158.mktorest.com/identity/oauth/token  
  clientId: your-client-id 
  clientSecret: your-client-secret 

There has docu ticket https://jira.magnolia-cms.com/browse/MKTAUT-156 and will update user guide as well. 

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