---
schema_version: "1"
id: 8237b3fb71a52759b9598f366ae4a0ada72e4cfe245ddd008e2b17ebb3580577
title: Send Activities
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/commerce-cloud/einstein/guides/einstein-activities/send-einstein-activities.md
canonical_url: https://developer.salesforce.com/docs/commerce/einstein-api/guide/send-einstein-activities.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: d76941077b9f6c957d9bf9312ff8c22f8c235abaa1f869a74b5c130e5cae3033
products:
  - B2C Commerce Einstein API
  - Salesforce APIs
---
# Send Activities

When configuring Einstein Activities APIs, keep in mind these important call-related and identification-related API parameters.

## Important API Parameters

- Parameters needed for all API calls:
  - `siteId` - Your Einstein site ID, which can be found in the top right of the page on [Einstein Configurator](https://configurator.cquotient.com). It has the format `xxxx-<B2C Commerce Site ID>`
  - `clientId` - The API key. To use Einstein API, you must authenticate by passing a query parameter with your Account Manager client ID. Customer admins can [add an API Client ID](https://help.salesforce.com/s/articleView?id=cc.b2c_account_manager_add_api_client_id.htm&type=5) on the [Account Manager](https://account.demandware.com/) page.
  - `instanceType` - Indicates whether to use the event's data to feed the prediction engine and for reporting, or not use it, for example, in the case of a mock call.
- Identification-related parameters:
  - `userId` - Einstein does not handle cross-device management on our side. In order to link users across different devices, Commerce customers must collect and pass a shared ID through this `userId`. Typically, only if the shopper is logged in and the login parameter is passed through this field, can shoppers be identified across device. To comply with GDPR, this field must be obscured through hashing or some other method.
  - `cookieId` - Pass a unique identifier in this parameter so that subsequent activities can be linked to the same user.
  - `uuid` - If you cannot generate a consistent `cookieId` for a given user (don't have a way of distinguishing between people), you can use this parameter outputted by Einstein API instead. Each activity request returns a UUID representing the user, which can be stored and passed in subsequent calls.

## Activities and Einstein Recommendations

Primarily intended for B2C Commerce, the Einstein Recommendations API uses activities that it receives to output recommendations. The `viewProduct`, `viewReco`, `clickReco`, `addToCart` activities are required. The API calls send each activity to the Einstein engine when these events occur. The Einstein engine then uses the data gathered from these activities to generate recommendations that it returns to the site.

For more information about the Einstein Recommendations API and how to use it, see the [B2C Commerce Einstein API](https://developer.salesforce.com/docs/commerce/einstein-api/overview/).

## Activities and PWA Kit

The Progressive Web App (PWA) Kit is a framework for creating storefronts using the Retail React App. It's available as an open-source project on GitHub. The Retail React App is a customizable storefront that implements core ecommerce flows from home page to checkout.

To get started, see the [PWA Kit and Managed Runtime](https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/getting-started.html) documentation.