- Sequential Property Building: Begin the import process with a subset of properties and gradually build up the profile until all properties are included. This ensures a smooth transition and avoids overwriting or omitting critical data.
- Consistent Property Lists: Avoid submitting inconsistent sets of properties for the same user or company in sequential identify_useroridentify_companyevents. Always include the full list of properties for eachidentifyevent. Populate known attributes and leave the remaining attributes asnullor empty values.
- Avoid Overwriting with Partial Data: Submitting partial data in subsequent identifycalls can cause critical attributes to be overwritten with null values, leading to inaccurate reporting and inconsistent profiles.
| Attribute | First identify | Second Identify | Third Identify | 
|---|---|---|---|
| name | ”John Doe" | "John Doe" | "John Doe” | 
| ”john@example.com" | "john@example.com" | "john@example.com” | |
| location | null | ”Dublin" | "Dublin” | 
| job_title | null | null | ”Architect” | 
- Best Practice: Gradually build up the user profile by adding properties in each step until the full profile is complete. This ensures the merge process maintains data consistency.
- Incorrect Practice: Reducing the set of properties in subsequent calls. This may result in missing or overwritten data.