SocialCommonUserMentionData

Social CommonInfrastructure

GoogleApi.ContentWarehouse.V1.Model.SocialCommonUserMentionData

1
out of 10
Minimal
SEO Impact
Person metadata, for USER_MENTION segments. Should always contain at least one of user_gaia_id, user_id, email or user. The exact set of populated fields may differ depending on the context and the level in the serving stack; for example, emails will be elided on the viewing path. But as a general rule, a proto having any one of the four is valid, subject to the standard constraints of the applied annotations -- that is, communication between servers and clients will ignore jspb.ignore fields, and communication between servers and other servers (or between servers and storage) will ignore client_only fields. For more on the annotations, see the comments in social/common/segment_annotations.proto

SEO Analysis

AI Generated

Backend infrastructure with indirect SEO impact. This model (Social Common User Mention Data) contains 4 attributes that define its data structure. Key functionality includes: If the principal is backed by a gaia id, DO NOT use this field. Use user_gaia_id/user_id fields instead.

Actionable Insights for SEOs

  • Understanding this model helps SEOs grasp Google's internal data architecture

Attributes

4
Sort:|Filter:
emailstring
Default: nilFull type: String.t
userSecurityCredentialsPrincipalProto →
Default: nilFull type: GoogleApi.ContentWarehouse.V1.Model.SecurityCredentialsPrincipalProto.t

If the principal is backed by a gaia id, DO NOT use this field. Use user_gaia_id/user_id fields instead.

userGaiaIdstring
Default: nilFull type: String.t

An unobfuscated gaia ID:

userIdstring
Default: nilFull type: String.t

An obfuscated gaia ID: