Zipy
  • Welcome to Zipy ai
  • Getting Started
    • Install Zipy
    • Installing with Google Tag Manager
    • Supported frameworks
    • Security Overview
    • Sensitive User Data
    • SOC2 Type II
  • Zipy For Mobile
    • React Native Setup
      • Install React Native
      • Input Masking
      • Session Replay
      • Screen Transition Capture
      • Gesture Capturing
      • Unhandled Exception Capture
      • Custom Logging
      • Fetch and XHR Network Calls
      • Profiling
      • Device Information Capture
      • Session URL Retrieval
      • Identify Users
      • Firebase Integration
    • Flutter Setup
      • Install Flutter
      • Session Replay
      • Input Masking & Custom Masking
      • Screen Transition Capture
      • Gesture Capturing
      • Unhandled Exception Capture
      • Custom Logging
      • Http Network Calls
      • Dio Network Calls
      • Profiling
      • Device Information Capture
      • Session URL Retrieval
      • Identify Users
      • Firebase Integration
      • Session Recording Control
      • Data Sanitization
  • iOS Setup
    • Install in an iOS app
    • Identify Users
    • Screen Tracking & Tagging
    • Custom Logging
    • Session URL Retrieval
    • Session Recording Control
    • Input Masking & Custom Masking
  • Chrome Extension
    • Zipy Plug and Play Support
  • Configure
    • Zipy Recording Control
    • Release Version
    • Identifying Users
    • Adding Custom Identifiers
    • Anonymize Users
    • Source Maps
    • Blocking PII data
    • Ignoring Errors/Noise
    • npm Update
    • Support Integration
    • Session Stitching (rootDomain)
  • Product Features
    • Custom Events
    • Session Replay
    • Errors
    • Analytics
    • Time Filters
    • Multiple Filters
    • Clicked Element Filters
    • Manage Teams
    • Stack Trace
    • Console Logs
    • Network Requests
    • Network Headers and Payload
    • Custom Logs
    • Live Users
    • Alerts
      • Slack Alerts
      • Email Alerts
      • Live Alerts
    • Auto Resolve Errors
    • Zipy Labels Plugin
    • iFrame Support
    • API Performance
    • Heatmaps
    • Page Performance
    • Seen/Unseen Sessions
  • FAQs
    • Install Zipy
    • Session Replay Definition
    • Error Tracking
    • Error Classification
    • Environment Support
    • Impact on your App
    • Performance Impact
    • Mobile Support
    • Network Data Capture
    • API Performance Diagnostic Help
      • High DNS Time
      • High SSL Connection Time
      • High Connection Setup Time
      • Large API Response Size
      • High Response Time
      • Compression Not Enabled
      • Server side API Failures
      • Client side API Failures
      • Insecure Connections
  • Troubleshooting
    • Errors in npm
    • Network header missing in Zipy
    • Can't see user data in sessions
    • No recordings or errors visible
    • No network timing split available
  • Product Videos
    • Ask AI
    • Getting Started
    • Session Replay
    • Multiple Project Creation
    • Team Management
    • Alerting on Slack
    • Time Filters and Daily Alerts
    • Custom Identifiers
    • Ignore Errors
    • Identify Users
    • Dashboard
    • Resolve Errors
    • New Error Digest
    • Jira and Slack
    • Online/Offline Network Status
    • Zipy on Zipy
      • Zipy Product Roadmap
  • Whats new
    • Product Updates
  • Legal & Policy
    • Terms of Service
    • Privacy Policy
    • Fulfillment Policy
    • Cookie Policy
    • Acceptable Usage Policy
    • Zipy Sub Processor List
  • Integration
    • Azure DevOps
    • Factors
    • RB2B
    • Webflow
    • WordPress
    • Amplitude
    • Coralogix
    • DevRev
    • Drift
    • Errorception
    • Freshchat
    • Google Analytics
    • Heap
    • HelpScout
    • Honeybadger
    • Hubspot
    • Intercom
    • Mixpanel
    • New Relic
    • Pendo
    • Raygun
    • Rollbar
    • Segment
    • Sentry
    • Shopify
    • Sumo Logic
    • TrackJS
    • Zendesk
Powered by GitBook
On this page
  • Overview
  • Step 1: Adding Zipy Session URL to Intercom User Profile.
  • Step 2: Displaying Zipy Session URL in Intercom Conversations
  • Example Use Case
  1. Integration

Intercom

Enhance Intercom support with Zipy session URLs for faster issue resolution and improved customer experience.

PreviousHubspotNextMixpanel

Last updated 1 year ago

Overview

The following steps will help you integrate Zipy session url with Intercom. This will help your support teams to understand user problems within tickets with Zipy session url so they can see what the users were doing when they reported a given issue in Intercom. This will speed up time to resolution by your support team significantly without doing multiple back and forth with the customer. The same Zipy session url can be shared with development teams to report issues.

Step 1: Adding Zipy Session URL to Intercom User Profile.

To begin, follow the steps below:

  1. Open your Intercom-enabled application.

  2. Add the following code snippet to your application:

const zipySessionUrl = window.zipy.getCurrentSessionURL();

Intercom('update', {
  zipy_session_url: zipySessionUrl,
});

By executing this code, the Zipy session URL will be associated with the corresponding user/lead profile in Intercom.

Step 2: Displaying Zipy Session URL in Intercom Conversations

Once the Zipy session URL is added to the user profile, it will appear in the 'USER DATA' or 'LEAD DATA' (if it's a lead) section during a conversation within Intercom.

By following these steps, you will successfully integrate Zipy with Intercom, providing you with valuable session information to enhance customer support and improve user experience.

Example Use Case

Sending Zipy Session URL to Intercom during a Chat Interaction.

  1. Ensure that both Intercom and Zipy are installed in your application.

  2. Implement the following code in your frontend application where Intercom Chat is enabled.

Intercom('onShow', async function() {
  const zipySessionUrl = await getCurrentZipySessionURL();

  Intercom('update', {
    zipy_session_url: zipySessionUrl,
  });
});

In this scenario, when the user/lead opens the Intercom Chat, the Zipy session URL will be retrieved and sent to Intercom as one of the parameters. This session url can be accessed within Intercom visitor chat information as part of user/lead data.

For more information on Intercom('onShow'), please refer to this .

link