Skip to content

Commit 8ff58bb

Browse files
Add note about Adobe timestamp options
1 parent d882e53 commit 8ff58bb

File tree

1 file changed

+3
-0
lines changed
  • src/connections/destinations/catalog/adobe-analytics

1 file changed

+3
-0
lines changed

src/connections/destinations/catalog/adobe-analytics/index.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -131,6 +131,9 @@ Segment's server-side integration is not open-source. Let's explore what happens
131131
- `userId`
132132
- `anonymousId`
133133

134+
> info ""
135+
> Adobe Analytics timestamp options need to match in the Segment destination settings and Adobe setting. Otherwise, events might be silently dropped by Adobe despite sending a 200 success response to Segment
136+
134137
5. Segment maps a number of other supported XML tags. For example, it sets `<ipAddress>` with the `ip` of the call.
135138

136139
**Note**: For server side libraries, the `ip` is by default be the `ip` address of your company servers, NOT the customers' own. This means that for server side events, it is best practice to record the customer's `ip` from their requests, and manually send that to Segment as `context.ip`.

0 commit comments

Comments
 (0)