8
6 years agoIn Review0

Please to the handbook to vote or submit new ideas
Don’t have a Handbook account? Just send us an email

Let’s facilitate engagement and increase lead conversion allowing the EN form block to display next to articles, as take action boxout do.

 

Jira ticket

 

== UPDATE 23/06/2021==

 

RECAP from Community feedback:  Generally very good feedback, as the community feels it would reduce a click. Frontend behaviour smth like this petition from Brazil

This was even in scope of the original TA boxout idea, but at the time no tech was available. Even with the new block design this could even be placed within the para / sticky etc. Petition / data capture forms would be the preferred type of forms in this case, perhaps opening up progressively as you enter one field? TBD 

For posts, it would be great if forms could be  made available as a reusable block available in the  “Select take action selector” command.

About the happy point, mixed feelings, perhaps the right mix with the Group block. It depends on how the form block evolves (e.g. “Apply for this job”) with the form embed. Potential for any embed really. 

PROs CONs 
  • Very clear scope 
  • Voted “I need this” by most (1 “I’d love”) 
  • Relatively low design work required  
  • Double engineering this to support EN + Hubspot? 
  • Complexity to support all iFrames?
  • Implications to support other forms?  
P4 tech team gut-feeling recommendation → Besides making the form behave like the Boxout (design input needed to align it with the style guide), we need to consider the expansion of the block itself (for pages) and of the  “Select take action selector” command. The analytics component (to track conversions) need to be taken into consideration as well. Overall high complexity if we want to replicate the EN form rendering in such a small container. 
Decision:

The P4 council decided to decline this idea for now. Despite a lot of ppl liking this, there’s hesitancy in spending time adding this functionality for the Engaging Networks (EN) forms, when most offices are phasing EN out. We should keep this option in mind when scoping out the upcoming native form builder feature, making sure we support global systems (HubSpot, ControlShift, Universe) and give options for extending the functionality to other systems.