Skip to main content
Connect Invoca and your FullStory account to send call events and Signals to FullStory sessions, for marketers and analysts who manage Invoca integrations.

​
Overview

Connecting Invoca interactions and Signals (call outcomes) to FullStory sessions shows where calls fit in a customer’s journey, so you can find friction points on your site. Setup has three steps:
  1. Get an API (application programming interface) Key from FullStory.
  2. Set up the integration tile and Actions in Invoca.
  3. Update your Invoca Tag to capture the FullStory Session ID.
This article covers Steps 1 and 2. Step 3, event validation, and common questions are in the companion article FullStory: Tag Setup, Validation, and FAQs.

​
Before you begin

  • You have access to your FullStory account.
  • The FullStory tile is enabled for your Invoca account. If the tile says Learn More, contact Invoca to enable access.

​
Step 1: Get your FullStory API Key

Collect your API Key from your FullStory account:
  1. In FullStory, go to Integrations > Settings > API Keys.
  2. Create a new key with Standard permissions.
  3. Save the key. You paste it into Invoca in the next step.

​
Step 2: Set up the integration in Invoca

With your API Key ready, connect your accounts in Invoca and create an Action for each event type you want to report.

​
Connect your FullStory account

  1. In the Invoca sidebar, click Integrations, then click Manage Integrations.
  2. Click the FullStory tile.
  3. Enter a friendly name to identify your FullStory account setup.
  4. Paste your FullStory API Key in the corresponding field.

​
Create an Action for each event type

An Action sets which interactions or Signals Invoca reports to FullStory.
  1. Select the Send Events Action Type.
  2. Enter a friendly name for the Action, for example, “FullStory - All Calls”.
  3. In the Triggered By drop-down menu, choose All Calls or a specific Signal.
  4. Enter an Event Name that corresponds to the Triggered By event you chose. This name appears as the event name in your FullStory reports.
  5. (Optional) Add parameters to send as event properties alongside the default data. Enter the parameter name in the left box. For a hard-coded value, enter the text string in the right box. For a dynamic value, choose a substitution token from the < > picker.
  6. Click Save.
To report another transaction type, repeat these steps.
Last modified on November 3, 2026