Skip to content

Commit c22fba7

Browse files
authored
Merge pull request #7259 from segmentio/jfoskin-patch-2
Payload order info
2 parents 37beb61 + 6772461 commit c22fba7

File tree

1 file changed

+2
-1
lines changed
  • src/connections/sources/catalog/libraries/website/javascript

1 file changed

+2
-1
lines changed

src/connections/sources/catalog/libraries/website/javascript/faq.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -141,4 +141,5 @@ If you need this functionality, you have a couple of options:
141141
**Use downstream tools**: Many analytics platforms, like Google Analytics, can automatically handle IP-to-geolocation conversion.
142142
**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.
143143

144-
144+
## Why is my payload populating incorrectly?
145+
Payload parameters aren't populated in a guaranteed order. Your payload should still be ingested as long as all necessary parameters are included.

0 commit comments

Comments
 (0)