--- schema_version: "1" id: 16f32a24c6189eab07f0d6ff13a2818e7dfbaf8b800c4954df56e3814817c76f title: Catalog Schema collection: developer version: current locale: en-us portal_url: https://docs.salesforce.com/developer/current/en-us/data-cloud/data-cloud-engagement-mobile-sdk/guides/c360a-api-engagement-mobile-sdk-catalog-schema.md canonical_url: https://developer.salesforce.com/docs/data/data-cloud-engagement-mobile-sdk/guide/c360a-api-engagement-mobile-sdk-catalog-schema.html source_site: developer.salesforce.com content_type: documentation content_hash: aaa6a90ff03023f92f136d00e1abdb7b6f3c6a3bd8d3ddd56c4b8821d9dfa48a products: - Data 360 Engagement Mobile SDK - Data 360 Developer Documentation --- # Catalog Schema Map an Engagement Mobile SDK catalog event to the catalog schema. | Source Event Property | Target Schema Developer Name | Field Type | Description | CIM Object / Attribute | | ----------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | | \ | `eventId` | text | **Required**. Typically, the primary key for the engagement events. | Product Browse Engagement / Product Browse Engagement Id | | \ | `dateTime` | dateTime | **Required**. Used for data partitioning for engagement events. ISO8601 supported format. | Product Browse Engagement / Created Date, Last Modified Date, Engagement Date Time | | \ | `eventType = "catalog"` | text | **Required**. The `developerName` of an event defined in the [Web Connector schema](https://help.salesforce.com/s/articleView?id=c360_a_mobile_web_sdk_schema_quick_guide.htm&type=5). | - | | \ | `sessionId` | text | **Required**. An identifier for a session. | - | | \ | `deviceId` | text | **Required**. Typically, the primary key for profile events. | Product Browse Engagement / Individual | | \ | `category = "Engagement"` | text | **Required**. Possible values are:
  • `Engagement`
  • `Profile`
| - | | \ | `interactionName: "View Catalog Object" \| "Comment Catalog Object" \| "View Catalog Object Detail" \| "Favorite Catalog Object" \| "Share Catalog Object" \| "Review Catalog Object" \| "Quick View Catalog Object"` | text | **Required**. A descriptive name for the event. | Engagement / Engagement Channel Action | | \ | `channel = "mobile"` | text | The SDK event channel. For Engagement Mobile SDK the value is `mobile`. | Engagement / Engagement Channel Type | | `catalogObject.type` | `type` | text | Required. A type name representing the catalog object. | - | | `catalogObject.id` | `id` | text | Required. A unique identifier representing the catalog object. | Product Browse Engagement / Product | | `catalogObject.attributes.customField0` | `attributeCustomField0` | any | A user-supplied value. | - | | `catalogObject.attributes.customFieldN` | `attributeCustomFieldN` | any | A user-supplied value. | - | | `catalogObject.relatedCatalogObjects.Example` | `relatedCatalogObjectExample0` | any | The first value in a list of related catalog object identifiers. | - | | - | `relatedCatalogObjectExampleN` | any | The n-th value in a list of related catalog object identifiers. | - | | \ | `longitude` | number | The longitudinal coordinate in decimal degrees reported by the device at the time the event was captured. | Engagement / Device Longitude | | \ | `latitude` | number | The latitudinal coordinate in decimal degrees reported by the device at the time the event was captured. | Engagement / Device Latitude | **note:** Properties added to `catalogObject.attributes` and `catalogObject.relatedCatalogObjects` aren’t automatically defined in the recommended schema. They’re shown to demonstrate how the source properties are mapped to the target schema. Manually add the properties to the schema.