Contact Updating via SDK
Updating contacts via SDK may seem convenient, but it has significant limitations. One of the primary issues is that SDK-based updates rely on the app's version. This means that if a user doesn’t update to the latest version of the app, any changes to their contact profile may not be synced with the Reteno. Here’s why this can be problematic:
- Missed Profile Updates: Users who haven't updated the app won't have their data changes (such as new preferences, behaviors, or status updates) reflected in Reteno, leading to outdated or incomplete profiles.
- Unreliable Targeting: Outdated contact data can result in poorly targeted campaigns. For instance, if a user’s fitness goals or subscription status changes but isn’t updated in Reteno, they may receive irrelevant messages, decreasing engagement and possibly causing frustration.
- Limited Reach and Personalization: Marketing relies on timely, personalized content. When SDK updates aren’t transferred, campaigns lose this personalization and relevance, reducing their effectiveness.
- Fragmented Data Management: Depending on app updates to sync data creates a fragmented approach, with some users having accurate profiles and others lagging behind. This inconsistency affects overall reporting and analysis, complicating decision-making.
For seamless and reliable contact management, backend updates to contact profiles are generally recommended. The backend remains independent of app versions, ensuring data is continuously accurate and up-to-date for every user. This approach maintains effective targeting and improves campaign results, as all changes sync automatically without relying on user app updates.
However, you can configure non-critical information to be updated using SDK.
Setting Up Contact Updating via SDK
When a user opens the app after downloading it, the SDK creates an anonymous contact with a Device ID and a push token if the user has given permission to receive push notifications. To update additional fields of such a contact, use the updateAnonymousUserAttributes method.
When the user logs into the app, transfer the contact identifier (email/phone) with User ID (External ID in Reteno) and the data of additional profile fields using the [updateUserAttributes](https://docs.reteno.com/reference/using-updateuserattributes-method) method.
If such an External ID exists in Reteno, the contact will be updated; if not, it will be created.
For more information about tracking user data, follow the links below:
Updated 10 days ago