[FE&R] Sending AB Tasty event to FullStory

Visitor ID requirement To make this integration work, you must identify the visitor using the same user ID before calling the Decision API.

What you must do • Identify the visitor in FullStory using: FS.identify(YOUR_USER_ID); • Call the Decision API with this same visitor ID • If the visitor ID isn’t passed, the hit won’t be sent to the third party

Introduction

Learn how to set up a server-side connector between AB Tasty and Fullstory to automatically send experiment and personalisation events from AB Tasty to your Fullstory account. This guide walks you through the configuration steps, authentication setup, and event mapping to ensure accurate and real-time data synchronisation.

Set-up

1

On Fullstory, create 2 custom events

FullStory Dashboard Configuration

• Go to Settings → Data Management → Events

• Create "flagship" event with properties:

  • Flagship_campaign_str (string)

  • Flagship_variation_str (string)

Then Go to Settings → Integrations → API Keys

Generate and copy an API key (admin permissions required)

2

Create a Fullstory Connector on AB Tasty

• Go to AB Tasty > Integration Hub > FE&R integration HUB

To access FE&R integration HUB, your account must have a valid FE&R Integration Hub

• Create a FullStory connector

  • Give your connector a name

  • Paste the previously created Fullstory API key

Visitor ID Requirement

FS.identify(YOUR_USER_ID);

Decision API must be called with this visitorID; otherwise, the hit won’t be sent to the third party

TroubleShoot

On FullStory, hits can be viewed on

• Settings → Data Management → Properties (as seen here)

• Real-time view with "flagship" event types captured by FullStory (as seen here)