Integrations

The Integrations page of My Relewise allows you to track the different types of entity integrations that are being sent to your dataset. This gives you an overview of the number of entities, sorted by type, that exist on your dataset and lets you track the progress of entity updates and administrative actions happening in real time, as well as user updates and administrative actions. For user behavior tracking, see our Behavioral Trackings page.

The top of the Integrations page displays different information pertaining to the entity data stored in Relewise, as well as the various API calls being performed.

Overview of API requests for selected time period.

Tracking API Calls

The following entities are tracked by My Relewise:

Type	Description
Stored Products	Tracks the number of Products currently stored in Relewise.
Stored Variants	Tracks the number of Variants currently stored in Relewise.
Stored Product Categories	Tracks the number of Product Categories currently stored in Relewise.
Stored Brands	Tracks the number of Brands currently stored in Relewise.
Stored Content	Tracks the number of Content currently stored in Relewise.
Stored Content Categories	Tracks the number of Content Categories currently stored in Relewise.
Stored Companies	Tracks the number of Companies currently stored in Relewise.
Stored Display Ad Templates	Tracks the number of Display Ad Templates currently stored in Relewise.
Stored Display Ads	Tracks the number of Display Ads currently stored in Relewise.

The following API calls list the entity-level requests in your dataset, including queries, updates, and administrative actions, along with user updates and administrative actions.

Type	Description
Product Queries	Tracks the number of ProductQuery requests made to read Product data in Relewise.
Product Updates	Tracks the number of product updates done via the TrackProductUpdate request. This tracking request type is used to add and update products in Relewise.
Product Administrations	Tracks the number of product administrative actions done via the TrackProductAdministrativeAction request. This tracking request type is used to disable, enable, and delete products in Relewise.
Product Engagements	Tracks favorites and sentiment on products and product variants through engagement integration events. See User Engagement for how to track and view this data.
Product Category Queries	Tracks the number of ProductCategoryQuery requests made to read Product Category data in Relewise.
Product Category Updates	Tracks the number of product category updates done via the TrackProductCategoryUpdate request. This tracking request type is used to add and update product categories to Relewise.
Product Category Administrations	Tracks the number of product category administrative actions done via the TrackProductCategoryAdministrativeAction request. This tracking request type is used to disable, enable, or delete product categories to Relewise.
Content Queries	Tracks the number of ContentQuery requests made to read Content data in Relewise.
Content Updates	Tracks the number of content updates done via the TrackContentUpdate request. This tracking request type is used to add and update content data in Relewise.
Content Administrations	Tracks the number of content administrative actions done via the TrackContentAdministrativeAction request. This tracking request type is used to disable, enable, and delete content data in Relewise.
Content Engagements	Tracks favorites and sentiment on content through engagement integration events. See User Engagement for how to track and view this data.
Content Category Queries	Tracks the number of ContentCategoryQuery requests made to read Content Category data in Relewise.
Content Category Updates	Tracks the number of content category updates done via the TrackContentCategoryUpdate request. This tracking request type is used to add and update content categories to Relewise.
Content Category Administrations	Tracks the number of content category administrative actions done via the TrackContentCategoryAdministrativeAction request. This tracking request type is used to disable, enable, or delete content categories to Relewise.
Brand Queries	Tracks the number of BrandQuery requests made to read Brand data in Relewise.
Brand Updates	Tracks the number of brand updates done via the TrackBrandUpdate request. This tracking request type is used to add and update brands in Relewise.
Brand Administrations	Tracks the number of brand administrative actions done via the TrackBrandAdministrativeAction request. This tracking request type is used to disable, enable, and delete brands in Relewise.
User Queries	Tracks the number of UserQuery requests made to read User data in Relewise.
User Updates	The number of user updates tracked. User updates are done with the TrackUserUpdate tracking request type and are used to explicitly update users, e.g. when a user signs up for the newsletter, updating the user with a newsletter ID. Note: Users are also tracked and updated on all other tracking requests that include a user.
User Administrations	Tracks the number of user administrative actions done via the TrackUserAdministrativeAction request. This tracking request type is used to delete users and remove Classifications or Identifiers based on user conditions.
Company Updates	Tracks the number of Company updates done via the API to add or update Company entities in Relewise.
Company Administrations	Tracks the number of Company administrative actions done via the API to disable, enable, or delete Company entities in Relewise.
Display Ad Updates	Tracks the number of Display Ad updates done via the API to add or update Display Ads in Relewise. See Retail Media Display Ads.
Display Ad Template Updates	Tracks the number of Display Ad template updates done via the API to add or update Display Ad Types in Relewise. See Retail Media Display Ads.

Live View

Use Live View to confirm that entity updates and administrative actions reach the selected Dataset. Filter by request type to focus on the integration you are checking.

Inspect Entity to check the affected entities. For User updates, expand identifiers and Classifications to verify the data supplied by your integration. Batch summaries help you check the types and number of updates sent together.

Open a request's details to inspect its JSON.