diff --git a/src/connections/sources/catalog/libraries/website/javascript/faq.md b/src/connections/sources/catalog/libraries/website/javascript/faq.md
index 905b79cc34..99b4bfe514 100644
--- a/src/connections/sources/catalog/libraries/website/javascript/faq.md
+++ b/src/connections/sources/catalog/libraries/website/javascript/faq.md
@@ -141,4 +141,5 @@ If you need this functionality, you have a couple of options:
 **Use downstream tools**: Many analytics platforms, like Google Analytics, can automatically handle IP-to-geolocation conversion.
 **Use a third-party API**: Alternatively, you can use third-party services like Geolocation API to convert IP addresses to geolocation data. Afterward, you can pass this information as a trait in Identify calls or as a property in Track calls to Segment. This allows you to manage geolocation data according to your specific needs, though it will likely require engineering resources.
 
-
+## Why is my payload populating incorrectly?
+Payload parameters aren't populated in a guaranteed order. Your payload should still be ingested as long as all necessary parameters are included.