Why Are Location Values Not Updated on the User Profile?

Problem

Location details such as City, State, and Country passed through Server-to-Server API (S2S API) or Amazon Simple Storage Service (S3) imports are not updated on the user profile in the MoEngage dashboard.s3 import.png

Explanation

  1. Internal attributes:
    • Location attributes (city, state, and country) are internal attributes derived from the user’s IP address during an SDK call triggered by the App/Site opened event.
    • These attributes are managed by the SDK to avoid potential conflicts and inconsistencies.
  2. Update restrictions:
    • These attributes cannot be updated through:
      • File imports (S3)
      • S2S API calls (v1/customer and v1/transition)
    • Updates attempted through these methods may be overridden by SDK updates, making debugging difficult for large user bases.
  3. User creation behavior:
    • These attributes are supported during the user creation process but remain unmodifiable afterward through non-SDK sources.
    • The values can be updated only after the SDK call occurs.
  4. SDK integration alternatives:
    • If SDK integration is not planned, use custom user attributes to store and manage location details.
    • This avoids conflicts with the internal attributes tracked by the SDK.

Was this article helpful?
0 out of 0 found this helpful

How can we improve this article?