Join expert-led sessions on Real-Time CDP & Journey Optimizer designed to boost your impact.
SOLVED
Issue with Multilingual Data Not Capturing Correctly During Migration from Adobe Analytics to Web SDK
1 Accepted Solution
Correct answer by
Hello @NG23 ,
I’ve come across a similar issue before—though not specifically with Web SDK—but based on what you’re describing, it definitely sounds like a character encoding issue. The Web SDK might not be correctly handling UTF-8 encoding for multilingual content like video titles, CTAs, or form labels.
This kind of issue usually happens in one of two ways:
1. The browser or client app isn’t sending the data in UTF-8, or
2. The Web SDK (or the Adobe Edge Network) is misinterpreting the encoding, assuming it’s something like Latin1 instead of UTF-8.
Here are a few suggestions to help debug and fix this:
Steps to Check
1. Ensure the client/browser sends data in UTF-8
• Check the request payload in DevTools (Network tab) to see how the multilingual text appears before it’s sent.
• Add this meta tag in your HTML <head> if it’s missing
<meta charset="UTF-8">
• Confirm that your request headers include:
Content-Type: application/json; charset=UTF-8
If the data isn’t properly encoded from the client side, the Adobe Edge Network won’t be able to decode it correctly.
2. Verify the response from Adobe Edge
• Also ensure that any responses from the Edge Network or AEP are encoded in UTF-8.
• You can inspect the response headers to confirm the charset.
If your client/browser is definitely sending UTF-8 encoded data and you’ve confirmed the headers are correct, but the issue still occurs, then it might be an issue on the Adobe Edge Network side.
I’m not sure if there’s a specific setting in the Data collection, when reading data to explicitly define character encoding—but it’s worth checking the documentation or reaching out to Adobe Support if needed.
Hope this helps!
Kind regards,
Parvesh
Correct answer by
Hello @NG23 ,
I’ve come across a similar issue before—though not specifically with Web SDK—but based on what you’re describing, it definitely sounds like a character encoding issue. The Web SDK might not be correctly handling UTF-8 encoding for multilingual content like video titles, CTAs, or form labels.
This kind of issue usually happens in one of two ways:
1. The browser or client app isn’t sending the data in UTF-8, or
2. The Web SDK (or the Adobe Edge Network) is misinterpreting the encoding, assuming it’s something like Latin1 instead of UTF-8.
Here are a few suggestions to help debug and fix this:
Steps to Check
1. Ensure the client/browser sends data in UTF-8
• Check the request payload in DevTools (Network tab) to see how the multilingual text appears before it’s sent.
• Add this meta tag in your HTML <head> if it’s missing
<meta charset="UTF-8">
• Confirm that your request headers include:
Content-Type: application/json; charset=UTF-8
If the data isn’t properly encoded from the client side, the Adobe Edge Network won’t be able to decode it correctly.
2. Verify the response from Adobe Edge
• Also ensure that any responses from the Edge Network or AEP are encoded in UTF-8.
• You can inspect the response headers to confirm the charset.
If your client/browser is definitely sending UTF-8 encoded data and you’ve confirmed the headers are correct, but the issue still occurs, then it might be an issue on the Adobe Edge Network side.
I’m not sure if there’s a specific setting in the Data collection, when reading data to explicitly define character encoding—but it’s worth checking the documentation or reaching out to Adobe Support if needed.
Hope this helps!
Kind regards,
Parvesh
