@algolia/client-insights 5.9.0 → 5.10.0-beta.1

package/model/purchasedObjectIDsAfterSearch.ts

@@ -1,57 +0,0 @@
-// Code generated by OpenAPI Generator (https://openapi-generator.tech), manual changes will be lost - read more on https://github.com/algolia/api-clients-automation. DO NOT EDIT.
-
-import type { ConversionEvent } from './conversionEvent';
-import type { ObjectDataAfterSearch } from './objectDataAfterSearch';
-import type { PurchaseEvent } from './purchaseEvent';
-import type { Value } from './value';
-
-/**
- * Use this event to track when users make a purchase after a previous Algolia request. If you\'re building your category pages with Algolia, you\'ll also use this event.
- */
-export type PurchasedObjectIDsAfterSearch = {
-  /**
-   * Event name, up to 64 ASCII characters.  Consider naming events consistently—for example, by adopting Segment\'s [object-action](https://segment.com/academy/collecting-data/naming-conventions-for-clean-data/#the-object-action-framework) framework.
-   */
-  eventName: string;
-
-  eventType: ConversionEvent;
-
-  eventSubtype: PurchaseEvent;
-
-  /**
-   * Index name (case-sensitive) to which the event\'s items belong.
-   */
-  index: string;
-
-  /**
-   * Object IDs of the records that are part of the event.
-   */
-  objectIDs: Array<string>;
-
-  /**
-   * Anonymous or pseudonymous user identifier.  Don\'t use personally identifiable information in user tokens. For more information, see [User token](https://www.algolia.com/doc/guides/sending-events/concepts/usertoken/).
-   */
-  userToken: string;
-
-  /**
-   * Identifier for authenticated users.  When the user signs in, you can get an identifier from your system and send it as `authenticatedUserToken`. This lets you keep using the `userToken` from before the user signed in, while providing a reliable way to identify users across sessions. Don\'t use personally identifiable information in user tokens. For more information, see [User token](https://www.algolia.com/doc/guides/sending-events/concepts/usertoken/).
-   */
-  authenticatedUserToken?: string;
-
-  /**
-   * Three-letter [currency code](https://www.iso.org/iso-4217-currency-codes.html).
-   */
-  currency?: string;
-
-  /**
-   * Extra information about the records involved in a purchase or add-to-cart events.  If provided, it must be the same length as `objectIDs`.
-   */
-  objectData: Array<ObjectDataAfterSearch>;
-
-  /**
-   * Timestamp of the event, measured in milliseconds since the Unix epoch. By default, the Insights API uses the time it receives an event as its timestamp.
-   */
-  timestamp?: number;
-
-  value?: Value;
-};

package/model/value.ts

@@ -1,6 +0,0 @@
-// Code generated by OpenAPI Generator (https://openapi-generator.tech), manual changes will be lost - read more on https://github.com/algolia/api-clients-automation. DO NOT EDIT.
-
-/**
- * Total monetary value of this event in units of `currency`.
- */
-export type Value = number | string;

package/model/viewEvent.ts

@@ -1,3 +0,0 @@
-// Code generated by OpenAPI Generator (https://openapi-generator.tech), manual changes will be lost - read more on https://github.com/algolia/api-clients-automation. DO NOT EDIT.
-
-export type ViewEvent = 'view';

package/model/viewedFilters.ts

@@ -1,40 +0,0 @@
-// Code generated by OpenAPI Generator (https://openapi-generator.tech), manual changes will be lost - read more on https://github.com/algolia/api-clients-automation. DO NOT EDIT.
-
-import type { ViewEvent } from './viewEvent';
-
-/**
- * Use this method to capture active filters. For example, when browsing a category page, users see content filtered on that specific category.
- */
-export type ViewedFilters = {
-  /**
-   * Event name, up to 64 ASCII characters.  Consider naming events consistently—for example, by adopting Segment\'s [object-action](https://segment.com/academy/collecting-data/naming-conventions-for-clean-data/#the-object-action-framework) framework.
-   */
-  eventName: string;
-
-  eventType: ViewEvent;
-
-  /**
-   * Index name (case-sensitive) to which the event\'s items belong.
-   */
-  index: string;
-
-  /**
-   * Applied facet filters.  Facet filters are `facet:value` pairs. Facet values must be URL-encoded, such as, `discount:10%25`.
-   */
-  filters: Array<string>;
-
-  /**
-   * Anonymous or pseudonymous user identifier.  Don\'t use personally identifiable information in user tokens. For more information, see [User token](https://www.algolia.com/doc/guides/sending-events/concepts/usertoken/).
-   */
-  userToken: string;
-
-  /**
-   * Identifier for authenticated users.  When the user signs in, you can get an identifier from your system and send it as `authenticatedUserToken`. This lets you keep using the `userToken` from before the user signed in, while providing a reliable way to identify users across sessions. Don\'t use personally identifiable information in user tokens. For more information, see [User token](https://www.algolia.com/doc/guides/sending-events/concepts/usertoken/).
-   */
-  authenticatedUserToken?: string;
-
-  /**
-   * Timestamp of the event, measured in milliseconds since the Unix epoch. By default, the Insights API uses the time it receives an event as its timestamp.
-   */
-  timestamp?: number;
-};

package/model/viewedObjectIDs.ts

@@ -1,40 +0,0 @@
-// Code generated by OpenAPI Generator (https://openapi-generator.tech), manual changes will be lost - read more on https://github.com/algolia/api-clients-automation. DO NOT EDIT.
-
-import type { ViewEvent } from './viewEvent';
-
-/**
- * Use this event to track when users viewed items in the search results.
- */
-export type ViewedObjectIDs = {
-  /**
-   * Event name, up to 64 ASCII characters.  Consider naming events consistently—for example, by adopting Segment\'s [object-action](https://segment.com/academy/collecting-data/naming-conventions-for-clean-data/#the-object-action-framework) framework.
-   */
-  eventName: string;
-
-  eventType: ViewEvent;
-
-  /**
-   * Index name (case-sensitive) to which the event\'s items belong.
-   */
-  index: string;
-
-  /**
-   * Object IDs of the records that are part of the event.
-   */
-  objectIDs: Array<string>;
-
-  /**
-   * Anonymous or pseudonymous user identifier.  Don\'t use personally identifiable information in user tokens. For more information, see [User token](https://www.algolia.com/doc/guides/sending-events/concepts/usertoken/).
-   */
-  userToken: string;
-
-  /**
-   * Identifier for authenticated users.  When the user signs in, you can get an identifier from your system and send it as `authenticatedUserToken`. This lets you keep using the `userToken` from before the user signed in, while providing a reliable way to identify users across sessions. Don\'t use personally identifiable information in user tokens. For more information, see [User token](https://www.algolia.com/doc/guides/sending-events/concepts/usertoken/).
-   */
-  authenticatedUserToken?: string;
-
-  /**
-   * Timestamp of the event, measured in milliseconds since the Unix epoch. By default, the Insights API uses the time it receives an event as its timestamp.
-   */
-  timestamp?: number;
-};