# LogRocket Destination

## About this integration

LogRocket combines session replay, error tracking, and product analytics—helping you create the ideal web and mobile product experience. This integration sends user telemetry and event data to LogRocket for enhanced analytics and filtering.

[Mode How we forward source data to the destination: through Customer.io's servers or directly from our JavaScript client.](/cdp/destinations/getting-started/#connection-mode)

[Web sources Indicates whether or not this integration supports our the JavaScript client.](/cdp/sources/getting-started/#types-of-sources)

[API sources Indicates whether or not this integration supports our server libraries (Go, NodeJS, Python), API, Mobile SDK, and other data sources.](/cdp/sources/getting-started/#types-of-sources)

[Supported calls The API methods this integration supports.](/cdp/sources/source-spec/source-events/)

[Integration name The name of this integration if you want to enable or disable it in the `integrations` object.](/cdp/sources/source-spec/common-fields/#the-integrations-object)

Web

[track](/api/cdp/#operation/track) and [identify](/api/cdp/#operation/identify)

logrocket

## Getting started[](#getting-started)

1.  Go to **[Data & Integrations > Integrations](https://fly.customer.io/workspaces/last/journeys/integrations/all/directory)** and select the **LogRocket** entry in the *Directory* tab.
    
2.  (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.
    
3.  Configure your integration.
    
    1.  **App ID**: The LogRocket app ID.
        
    2.  **Network Sanitization**: Sanitize all network request and response bodies from session recordings.
        
    3.  **Input Sanitization**: Obfuscate all user-input elements (like <input> and <select>) from session recordings.
        
4.  Click **Enable Destination**.
    

## Actions[](#actions)

When you’re done setting things up, you can go to the *Actions* tab to see how we map incoming data to your integration.

You may need to add actions for this integration

While we often have default triggers for actions, we don't always add those actions as defaults. You may need to add actions to make sure that you're sending all the data that you want to send to your integration. See our [actions](/integrations/data-out/actions/) page for help setting up actions.

Action

Default Trigger

Description

Track

`type = “track”`

Send track events to logrocket for filtering and tagging.

Identify

`type = “identify”`

Send identification information to logrocket.