- Default Strategy - Any identifier attribute received across the sources is used to identify a customer profile or create a new profile. To more about how this configuration work, refer here.
- High-fidelity or Custom Strategy- We recommend using this strategy if you want the system to use a specific high-fidelity identifier for identity resolution and profile creation. Using this strategy, you can classify your high-fidelity identifier as primary, secondary or even disable the IDs for profile creation. You can also prioritise them for finer decision-making. To more about how this configuration work, refer here.
Preventing Faulty ID Values from being ingested into Catalogue
Zeotap CDP has developed a backend feature to prevent certain values in incoming fields from participating in the Identity resolution. According to that, if an ingested value has data quality issues, then such values are added to a blacklist. let’s assume that you have shared a dummy email address like xyz@gmail.com for all your customers in your incoming data. If this dummy address participates in the ID resolution, it leads to the unintended unification of thousands of user profiles. It can also compromise the matched profiles, necessitating extensive cleanup and re-ingestion owing to substantial time and effort. To mitigate such challenges, a criterion is established through this feature, wherein, if an incoming value matches with more than 101 profiles, then it is promptly added to the blacklist. The blacklisted values are enforced at the organisation level and cannot be disabled.Note:The blacklisted values are only blocked from participating in the Identity resolution and are not deleted from the system. Therefore, you cannot find them by searching in Customer 360 or Profile API.