Using 3rd Party Video Components for Experience Creation in Adobe Target

[JacobDiaz]

Hello Target Community,

I am experiencing issues altering or modifying an AEM video component using a third party based player (Wistia) for experience creation in Adobe Target. When the VEC is used to perform any experience modification within the video components div container, upon trying to save the activity it returns an Unsupported Characters error message :

"ERROR Only characters within the basic multilingual plane are supported. Characters outside of this plane typically show up as corrupted in the browser. Please remove them from any input field and re-try saving."

Because we want to use this component in different sections of a webpage for a Target test activity, my thought was to leverage the AEM Experience Fragment integration with Adobe Target we have enabled to export and place this video component without the need for editing the div video section's unsupported code. However exporting this video component as an Experience Fragment to Target returns the same unsupported symbols error :

"ERROR Only characters within the basic multilingual plane are supported. Characters outside of this plane typically show up as corrupted in the browser. Please remove them from any input field and re-try saving."

Since this component is embedded using a 3rd party player, using the VEC to edit the HTML/CSS and remove the unsupported multiplane code has not proven to be successful.

Curious if anyone has had a similar experience with video components? Or if anyone has found a workaround for utilizing embedded video components with Multiplane code in Adobe Target?

Thank you!

[JacobDiaz · Accepted solution]

The issue has been identified. The embedded AEM component utilized characters that were outside the UTF-8 plane. These characters were found in the components script. Which resulted in an error when modifying the component in a Target activity or when exporting to Target as an Experience Fragment.