Home > Property Management > Situations Where We Backfill User Attributes

Download this article
お知らせ: このページは現在英語のみで提供されています。日本語版は準備中です。ご不便をおかけして申し訳ございません。

Situations Where We Backfill User Attributes

Because we use your own data to segment your user populations the quality of the visualizations in our reports relies on the strength of your data. Whatever the user field is in Active Directory, Workday, or other integrated fields will be what shows in tyGraph with the exception of the following three scenarios:

  • No Information

    We will backfill null records for a user with . This way you can understand that we have a user record and activity but there was no data for that category. Either they have nothing in AD for the field or in the case of Workday/HRIS, Microsoft has records for the user but they weren't listed in the source provided by your organization.

  • External User

    We backfill external user information with the attribute if it is null. The reason is that external users get captured by our tool, but they are rarely listed in Active directory.

  • Anonymized

    If a user’s information was anonymized by our data protection logic the users PII will be replaced with this value.

Backfilling Priority for Augmented Data

When you bring your own User Attributes we can set a few levels of priority.

  • Overwrite

    For columns populated in External Load, it will be overwritten with provided data for all users. Columns not populated in the external load will not be overwritten. If a user is in tyGraph but not in the external load file their data will not overwritten.

  • Augmentation

    Overwrite when empty.

Content Backfill

The User Continent field is a dimension that is generated by tyGraph intelligence. We look up the users Country (not usage location) and use that to infer their Continent (often listed as region in some companies).

Refer to Appendix A: User Continent (Region) in tyGraph for a full list of countries by continent. If you would like your list changed. Please send this table to tyGraph support with your updated naming convention in the same structure.