Fullstory Integration
A vs B sends your experiment data to Fullstory through the Fullstory library that is already running on your page. There is no org ID to paste in. If window.FS works, either the newer callable version or the older .event method, we talk to it.
A variation is one specific version being tested: the control, or one of the challengers. Once Fullstory is on, you can filter session recordings down to the visitors who saw one variation. That is the fastest way to understand why it won or lost.
Setup
Go to Project Settings > Integrations
Open your project, click Settings, then open the Integrations tab.
Turn on Fullstory
Find the Fullstory card and switch it on.
Choose anything else you want sent
Under Also send, tick conversions, purchases, or recommendation events. Experiment views are always sent.
Save
Click Save. Your changes reach your live site within about a minute.
- The on/off switch, top right of the card.
- The Also send checklist for conversions, purchases, and recommendation events.
What is sent
When a visitor is shown a variation:
// `FS` is the global the FullStory snippet installs on the page.declare const FS: (api: string, payload: Record<string, unknown>) => void;FS('trackEvent', { name: 'AvsB Experiment Viewed', properties: { experiment_id: '482', experiment_name: 'Homepage hero', variation_id: '1913', variation_name: 'Variant B', event_id: '3f9a2b1c-7d4e-4a58-9c02-5e6d1f8b3a47' }});| Event | Default name | Extra properties |
|---|---|---|
| Experiment view | AvsB Experiment Viewed | revenue or value when the event carries one |
| Conversion | avsb_goal | goal_key, plus revenue or value when you sent one |
| Purchase | avsb_purchase | revenue, currency, transaction_id |
| Recommendation seen | avsb_rec_impression | the recommendation details, such as recipe and items |
| Recommendation clicked | avsb_rec_click | the recommendation details, such as recipe, item, and position |
Empty fields are left out rather than sent as blanks.
The call above is the Fullstory version 2 API. Sites still on version 1 receive FS.event('AvsB Experiment Viewed', { ... }) with exactly the same event name and the same properties, so nothing else on this page changes for them.
Renaming events
Every name in the table can be changed on the card. Leave a box empty to keep the standard name shown inside it.
Check it works
On the Integrations tab, use Send a test event. It opens your site in a new tab and sends one clearly labelled test event, avsb_test_event, to every tool you have switched on. It appears on that session's timeline in Fullstory.
Your project needs at least one live experiment for this to work, since the test event is sent against the first one.
Viewing experiment data in Fullstory
- Filter recordings: in Sessions search, filter by the event
AvsB Experiment Viewedand add a property filter forvariation_name. You now have only the sessions from that variation. - Funnels: build a funnel that starts with the experiment view and includes your conversion steps, then split by
variation_name. - Session timeline: the event appears on each recording at the moment the visitor was put into the experiment.
Watching five to ten recordings from each variation is usually worth more than any extra chart. Your results tell you what happened; the recordings tell you why.