|
1 | | -Several key factors can prevent events from being successfully ingested into the Segment platform through server-side libraries as sources. Understanding these reasons is crucial for troubleshooting and ensuring data integrity. Here are some suggestions to address these challenges: |
| 1 | +{% assign currentSlug = page.url | split: "/" | last %} |
| 2 | +{% assign currentIntegration = site.data.catalog.sources.items | where: "slug", currentSlug | first %} |
2 | 3 |
|
3 | | -If you are experiencing loss of events ingested from your {% page.title %}, |
| 4 | +### Other common errors |
4 | 5 |
|
5 | | -- **Payload is too large**: If you attempt to send events larger 32KB per normal API request or batches of events larger than 500KB per request, Segment’s tracking API responds with 400 Bad Request. Try sending smaller events (or smaller batches) to mitigate this error. |
| 6 | +If you are experiencing data loss from your {{ currentIntegration.display_name }} source, you may be experiencing one or more of the following common errors: |
6 | 7 |
|
7 | | -- **Identifier is not present**: Segment's tracking API requires that each payload has a `userId` and/or `anonymousId`. If you send events without either the `userId` or `anonymousId`, Segment's tracking API responds with ERROR CODE ERROR NAME. |
| 8 | +- **Payload is too large**: If you attempt to send events larger 32KB per normal API request or batches of events larger than 500KB per request, Segment’s tracking API responds with `400 Bad Request`. Try sending smaller events (or smaller batches) to correct this error. |
8 | 9 |
|
9 | | -- **Track event is missing name**: All Track events to Segment must have an event field. |
| 10 | +- **Identifier is not present**: Segment's tracking API requires that each payload has a `userId` and/or `anonymousId`. If you send events without either the `userId` or `anonymousId`, Segment's tracking API responds with an `no_user_anon_id` error. Check the event payload and client instrumentation for more details. |
10 | 11 |
|
11 | | -- **Event dropped during deduplication**: Segment automatically adds a `messageId` field to all payloads and uses this value to deduplicate events. If you're manually setting a `messageId` value, ensure that each event has a unique value to avoid data loss. |
| 12 | +- **Track event is missing name**: All Track events to Segment must have a name in string format. |
| 13 | + |
| 14 | +- **Event dropped during deduplication**: Segment automatically adds a `messageId` field to all payloads and uses this value to deduplicate events. If you're manually setting a `messageId` value, ensure that each event has a unique value. |
| 15 | + |
| 16 | +- **Incorrect credentials**: Double check your credentials for your downstream destination(s). |
| 17 | + |
| 18 | +- **Destination incompatibility**: Make sure that the destination you are troubleshooting can accept server-side API calls. You can see compatibility information on the [Destination comparison by category](/docs/connections/destinations/category-compare/) page and in the documentation for your specific destination. |
| 19 | + |
| 20 | +- **Destination-specific requirements**: Check out the [destination's documentation](/docs/connections/destinations/) to see if there are other requirements for using the method and destination that you're trying to get working. |
0 commit comments