Skip to content

Configuring External Analytics Integrations ​

While Videobot provides built-in metrics for monitoring its performance, integrating with third-party analytics services offers additional benefits such as:

  • Consolidating Videobot data with your existing website analytics
  • Tracking conversions across your entire user journey
  • Enabling A/B testing with specialized tools
  • Creating custom audience segments based on video interactions

Videobot supports integration with virtually any analytics platform through raw events, but also offers streamlined integration with Google's analytics suite. This guide will help you understand the available options and choose the most appropriate solution for your needs.

Understanding the Components ​

Google Tag Manager (GTM) ​

Google Tag Manager is a tag management system that allows you to quickly and easily update tracking codes and related code fragments on your website. With GTM, you can:

  • Deploy analytics tags without modifying your website code
  • Set up triggers to fire specific tags based on Videobot events
  • Create variables to capture Videobot data
  • Configure multiple analytics tools through a single interface

Google Analytics 4 (GA4) ​

Google Analytics 4 is Google's latest analytics offering that helps you measure traffic and engagement across your websites and apps. Videobot's GA4 integration:

  • Tracks user interactions with your Videobots as events in GA4
  • Allows you to measure conversions that originate from Videobot interactions
  • Provides demographic and behavioral data about users who engage with your Videobots
  • Supports advanced analysis through GA4's exploration reports

Choosing the Right Integration Method ​

Videobot offers several integration methods for analytics. Here's a comprehensive comparison to help you select the most appropriate option:

Best for: Websites already using GTM or requiring complex analytics setups.

How it works: Videobot events are pushed to the data layer, which GTM can access and use to trigger tags.

Advantages:

  • Most versatile approach with maximum flexibility
  • Enables integration with multiple analytics platforms simultaneously
  • Changes can be made without modifying website code
  • Supports detailed event tracking with custom parameters

Considerations:

  • Requires GTM knowledge for advanced configurations
  • Slightly more complex initial setup

Setup instructions →

2. GA4 Website Integration (gtag.js) ​

Best for: Websites already using GA4 directly (without GTM) that need simple Videobot tracking.

How it works: Videobot events are sent directly to your existing GA4 installation via the global gtag function.

Advantages:

  • Simpler setup than GTM
  • Works with existing GA4 implementations
  • No need for additional containers or services

Considerations:

  • Less flexible than the GTM approach
  • Requires manual code changes to modify tracking
  • Limited to GA4 only (cannot easily send data to other analytics tools)

Setup Instructions ​

Using this integration is simple. To start sending events, enable the Google Analytics (Website) integration. After verifying that events are being sent correctly, follow the GA4 configuration guide.

3. GA4 Direct Integration (Legacy) ​

Best for: Iframe embeds or situations where website access is limited.

How it works: Videobot connects directly to GA4 using your measurement ID.

Advantages:

  • Works without any website modifications
  • Suitable for iframe embeds
  • Independent of website's analytics setup

Considerations:

  • Consent handling can be cumbersome
  • Data appears separate from website analytics
  • Not recommended for new implementations

4. Google Tag Manager Embedded Integration ​

Best for: Injecting tags or running custom tags within the hosted Videobot, especially when linking to a Videobot directly instead of embedding on an external website.

How it works: Videobot creates a GTM container within itself, which can be used to implement custom tracking.

Advantages:

  • Customizable tracking and consent handling
  • Access to the Videobot context in a way not possible by other means
  • Works without a containing parent website

Considerations:

  • Not recommended for widget or slider embeds
  • Requires a separate GTM container
  • Should be reserved for special cases

5. Custom Integration via postMessage API ​

Best for: Integration with custom analytics systems or when using iframes

How it works: Videobot sends events via the postMessage API, which your website can capture and process.

Advantages:

  • Maximum flexibility for custom analytics implementations
  • Works with any analytics platform
  • Full control over event handling

Considerations:

  • Requires custom JavaScript development
  • No pre-built integrations

Setup instructions →

Implementation Recommendations ​

For most users, we recommend the following approach:

  1. If you already use Google Tag Manager on your site: Choose the GTM website integration for maximum flexibility and ease of management.

  2. If you use GA4 directly (gtag.js) without GTM: Use the GA4 website integration for a straightforward setup.

  3. If you need to integrate with multiple analytics platforms: Implement GTM (even if you don't currently use it) for the most versatile solution.

  4. If you're linking to Videobots directly: Use the GTM embedded integration to inject custom tracking and consent tags.

  5. If you're using iframes to embed a Videobot: Use the custom integration with postMessage to listen to events and forward them.