[Content]:

[lizkane222]

What article on segment.com/docs is affected?

https://segment.com/docs/connections/destinations/catalog/amplitude/

What part(s) of the article would you like to see updated?

This requirement should be included in Amplitude Classic destination docs :

Minimum ID Length | Type: INTEGER |Amplitude has a default minimum id length of 5 characters for user_id and device_id fields. This field allows the minimum to be overridden to allow shorter id lengths.

Additional information

After replaying data for a user into an Amplitude Classic destination there were events that threw this error : discarded.INVALID_ID_LENGTH, which I believe corresponds to the latest documentation of Amplitude's HTTP API.

The Amplitude (Actions) destination has this requirement (pasted below) already laid out in each of its events, and should probably be included in the Amplitude Classic documentation as well.

Minimum ID Length | Type: INTEGER |Amplitude has a default minimum id length of 5 characters for user_id and device_id fields. This field allows the minimum to be overridden to allow shorter id lengths.

[cmastr]

@lizkane222 We plan to close this issue on Friday, January 26, 2024. If we still need to do this work, please let us know.

[lizkane222]

@cmastr Just reviewed the documentation and this doc update should still be applied.

Since we've launched the Amplitude Actions destination since I created this PR, I might also add a section directly below it though with this information below. "This minimum id length restriction can now be bypassed by using the Amplitude Actions destination, where this minimum id length can be customized to accept a shorter length within the Actions mappings."

[cmastr]

Ok will leave this open.