AEM forms to Marketo forms - is it possible to map multiple AEM form fields to one in Marketo | Community
Skip to main content
R
Romina-2
New Participant
July 20, 2023
Question

AEM forms to Marketo forms - is it possible to map multiple AEM form fields to one in Marketo

  • July 20, 2023
  • 1 reply
  • 4130 views

Hello all. We are looking to create a lenghty form to place on our AEM website. As we don't want to create additional Marketo fields, we are thinking of using AEM forms instead and have the submissions feed into Marketo. But we are not sure if we can do a many-to-one mapping. We would like most fields to map to only one field in Marketo (including the questions).

For example, we would have the following questions on the AEM form:
Q1: What is you favorite color?
A: Blue
B: Red

Q2: What is your favorite season?
A: Summer
B: Spring

If I fill in the form and I choose for Q1 answer A and for Q2 answer B, the information would be passed to only one field as follows:
What is you favorite color? Blue
What is your favorite season? Spring

Has anyone does this before? And if yes, please share any advice you may have.

Thanks All, hope you have a great day ahead!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

Darshil_Shah1
Darshil_Shah1
Community Manager
July 20, 2023

Well, since this is not a Marketo form you'd most likely be making Marketo form submissions in the background to register the form fill activity and send data to Marketo (you can use the submitForm API endpoint too, but background form submission using the form2 API is more robust due to multiple reasons). While making the form submit, you can set the value in the Marketo fields as per your requirement, e.g., concatenate multiple questions and their responses. It's just that the field should be able to accept that data in Marketo, e.g., the type should match (you would want an open text/string field most likely) and if the field to which you're writing data is a CRM synced picklist field, you may run into sync errors in case the value you have in the field isn't one of the available picklist values, so you may want to account for that. Additionally, goes without saying, but if this field's values are being referenced anywhere in campaigns, flow, etc., you'd have to account for the way you'd store data in it there as well.

 

R
Romina-2Author
New Participant
August 10, 2023

Thank you for your advice, @darshil_shah1 . I had a look at Marketo form submissions in the background and from what I am understanding this form will be placed on the same website page as the AEM form and capture the submissions "in parallel"?
How would this hidden form then be linked to the actual AEM form so that the information submitted is passed from one system to the other? Would you happen to know? Any resource you could share would be appreciated. Thank you!

Darshil_Shah1
Darshil_Shah1
Community Manager
August 10, 2023
@romina-2 wrote:

Thank you for your advice, @darshil_shah1 . I had a look at Marketo form submissions in the background and from what I am understanding this form will be placed on the same website page as the AEM form and capture the submissions "in parallel"?

Yes, this form would be placed on the same webpage where you've your AEM form.


How would this hidden form then be linked to the actual AEM form so that the information submitted is passed from one system to the other? Would you happen to know? Any resource you could share would be appreciated. Thank you!

Well, forms aren't technically linked. The background form submission method picks the data submitted by the visitor for each field on a non-Marketo form (in your case an AEM form), adds the respective field's data to a hidden field in the Marketo form, and makes a form submission post to Marketo. This method allows you to pass the form-fill data and activity in Marketo so you can seamlessly reference data and reference the form-fill activity in the triggers/filters in your campaigns/smart lists.

Terms & ConditionsAccessibility statement

Loading footer...