SocialGraphApiProtoContactMutationContext

Social Graph APIInfrastructure

GoogleApi.ContentWarehouse.V1.Model.SocialGraphApiProtoContactMutationContext

1
out of 10
Minimal
SEO Impact
This message is the generic mutation message which will encapsulate the fields which are shared between the create, update, and delete actions, including source of change, timestamp, and metadata messages passed in from the source for any source specific data (such as phone name/model from FSA).

SEO Analysis

AI Generated

Backend infrastructure with indirect SEO impact. This model (Social Graph Api Proto Contact Mutation Context) contains 5 attributes that define its data structure. Key functionality includes: Android device info should always be set when using either ANDROID_FSA1 or ANDROID_FSA2 as the source of the delete.

Actionable Insights for SEOs

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

Attributes

5
Sort:|Filter:
androidDeviceInfoSocialGraphApiProtoAndroidDeviceInfo →
Default: nilFull type: GoogleApi.ContentWarehouse.V1.Model.SocialGraphApiProtoAndroidDeviceInfo.t

Android device info should always be set when using either ANDROID_FSA1 or ANDROID_FSA2 as the source of the delete.

hostAppInfoSocialGraphApiProtoHostAppInfo →
Default: nilFull type: GoogleApi.ContentWarehouse.V1.Model.SocialGraphApiProtoHostAppInfo.t

Host app info should always be set when using CONTACTS_COMPANION as the source.

sourcestring
Default: nilFull type: String.t

The source of a mutate should provide all needed information a user should know, and should be enough information for the front end to generate a proper human readable string to describe the mutate to the user.

thirdPartyInfoSocialGraphApiProtoThirdPartyInfo →
Default: nilFull type: GoogleApi.ContentWarehouse.V1.Model.SocialGraphApiProtoThirdPartyInfo.t

Third party info should always be set when using THIRD_PARTY as the source.

timestampdatetime
Default: nilFull type: DateTime.t

Timestamp representing when the contact was mutated. This should not be set on write, as it is the job of focus backend to determine this timestamp. This field will be populated on read with the data written by FBS.