From 9f8a052620ca45425c2bd955d93debaa9e45db9f Mon Sep 17 00:00:00 2001 From: Jazma Foskin <82051355+jfoskin@users.noreply.github.com> Date: Mon, 25 Nov 2024 10:09:36 -0500 Subject: [PATCH 1/2] Payload order info --- .../sources/catalog/libraries/website/javascript/faq.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/connections/sources/catalog/libraries/website/javascript/faq.md b/src/connections/sources/catalog/libraries/website/javascript/faq.md index 905b79cc34..c44991d8d6 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. - +## My payload is populating incorrectly +There is not a guaranteed order that parameters are populated, your payload should still be ingested as long as all neccessary parameters are included. From 6772461300cd58d20a16d528016b9f7152b7db17 Mon Sep 17 00:00:00 2001 From: stayseesong <83784848+stayseesong@users.noreply.github.com> Date: Fri, 13 Dec 2024 15:12:12 -0800 Subject: [PATCH 2/2] Update src/connections/sources/catalog/libraries/website/javascript/faq.md --- .../sources/catalog/libraries/website/javascript/faq.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/sources/catalog/libraries/website/javascript/faq.md b/src/connections/sources/catalog/libraries/website/javascript/faq.md index c44991d8d6..99b4bfe514 100644 --- a/src/connections/sources/catalog/libraries/website/javascript/faq.md +++ b/src/connections/sources/catalog/libraries/website/javascript/faq.md @@ -141,5 +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. -## My payload is populating incorrectly -There is not a guaranteed order that parameters are populated, your payload should still be ingested as long as all neccessary parameters are included. +## 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.