FullStory
FullStory
See your site through your users' eyes. FullStory records and reproduces real user experiences on your site helping you support customers, boost conversions, and debug faster. FullStory replays your customer's journey removing the guesswork from reproducing bugs, showing customer struggles instantly with every ticket filed, and turning underperforming landing pages, abandoned carts, and bounce rates into learning opportunities.
  • Personalisierung
Demo anfordern
Join a live demonstration of Tealium's native support for FullStory to see how Tealium makes it easier to implement and enrich this part of your digital stack.
Supported Integration Types
FullStory can be integrated in the following ways:
  • Business Application Desktop applications, such as business intelligence or reporting tools, can also easily connect to Tealium services such as DataAccess.
  • Device-Based Delivery These connectors send data to the desired vendor or service directly from the client or device where the data is originating.
  • AudienceStream These connectors are hosted integrations within the Tealium platform utilizing AudienceStream. They receive data from the originating client or device, and send that data on to the desired vendor or service.
  • EventStream These connectors are hosted integrations within the Tealium platform utilizing EventStream. They receive data from the originating client or device, and send that data on to the desired vendor or service.
  • Installation Library Deploy Tealium to virtually any platform (web, connected device, IoT), language (java, ruby, perl), or content management service. Send any data to your desired end point vendor or marketing solutions.
  • Developer API Need deeper integration with a Tealium service? We offer a number of APIs providing richer configurability of your Tealium deployment.
  • Tealium Tool Tealium Tools is the playground for developers to integration with Tealium.
Supported Device Types
Connectors may be optimized to receive specific event attributes for select platforms. For example, a mobile phone would likely send a 'screen_name' event attribute, representing the name of the screen being viewed by the end user.
  • Webbrowser These connectors expect to receive standard event attributes originating from a web browser, such as current_url, referring_url, page_name, page_category, and others.
  • Mobile Mobile Applications have a variety of conventional event attributes such as 'screen_width', 'screen_orientation', etc.
  • Your Server Tealium Collect can be deployed to any service or solution utilizing your favorite programming languages. This is the most 'generic' deployment.
  • Verbundene Geräte Connected Devices are those that don't quite fit the mobile mold, such as connected set-top boxes (OTT), wearables, etc.
Features
This integration offers these features