Strikingly Analytics Integrations: Setup Guide

Strikingly provides methods to integrate analytics platforms, tag managers, and marketing pixels through custom code injection. This section covers the most common integrations and Strikingly-specific implementation details.

Available Integrations

Analytics Platforms

Google Analytics 4

• Custom code injection method
• Limited to basic page view tracking by default
• Custom event tracking requires additional code
• Works on all Strikingly plans with custom code access

Tag Management

Google Tag Manager

• Custom code injection in site settings
• Provides flexibility for managing multiple tags
• Recommended approach for complex tracking needs
• Requires some technical knowledge

Marketing Pixels

Meta Pixel

• Custom code injection method
• Base pixel for page views
• Event tracking requires manual implementation
• Enhanced measurement with custom events

Strikingly-Specific Integration Considerations

Custom Code Injection

Strikingly's primary method for adding tracking codes is through the custom code feature:

Locations:

• Site-wide header code: Loads on every page (recommended for tracking)
• Site-wide footer code: Loads at bottom of every page
• Page-specific code: Limited availability, use with caution
• Section HTML: Can inject code in custom HTML sections

Accessing Custom Code:

1. Log in to your Strikingly dashboard
2. Select your site
3. Click Settings → Advanced
4. Find Custom Code section
5. Add your code to Header Code or Footer Code

One-Page Site Architecture

Strikingly specializes in one-page websites, which affects tracking:

Implications:

• Most sites have a single URL (homepage)
• Section scrolling doesn't trigger page views
• Custom events needed for section visibility tracking
• Anchor navigation doesn't create traditional page views

Best Practices:

• Use virtual page views for section tracking
• Implement scroll-based event tracking
• Track button clicks and form submissions
• Monitor section engagement separately

Plan Limitations

Different Strikingly plans have varying custom code access:

Free Plan:

• No custom code injection
• Cannot add analytics or tracking pixels
• Limited to Strikingly's built-in features

Limited/Pro Plans:

• Full custom code access in header/footer
• Can add analytics, GTM, and pixels
• Recommended minimum for tracking implementation

VIP Plan:

• All custom code features
• Priority support for implementation issues
• Better performance for code-heavy sites

Mobile Responsiveness

Strikingly sites are automatically responsive:

Tracking Considerations:

• Same tracking code works on all devices
• Test mobile interactions separately
• Consider mobile-specific events (swipe, touch)
• Mobile traffic often higher on Strikingly sites

Performance Impact

Strikingly sites are optimized for speed, but custom code can impact performance:

Performance Tips:

• Use async/defer attributes for scripts
• Minimize number of tracking pixels
• Consolidate through GTM when possible
• Monitor Largest Contentful Paint (LCP)
• Avoid heavy JavaScript in custom sections

Integration Best Practices

1. Use Google Tag Manager as Central Hub

Instead of adding multiple pixels directly:

• Install GTM once in Strikingly's header code
• Add all tracking pixels through GTM
• Easier to manage without editing site settings
• Better performance (single container load)
• No need to republish site for tracking changes

2. Test Thoroughly Before Publishing

Testing Checklist:

• Add code to test site first
• Verify in browser console (no errors)
• Test with GTM Preview mode (if using GTM)
• Check GA4 Realtime or DebugView
• Test on mobile devices
• Verify all section interactions
• Publish and verify again

3. Track Section Engagement

Since Strikingly sites are often one-page:

// Example: Track section visibility
document.addEventListener('DOMContentLoaded', function() {
  const sections = document.querySelectorAll('section[id]');

  const observer = new IntersectionObserver(function(entries) {
    entries.forEach(function(entry) {
      if (entry.isIntersecting) {
        // Send virtual page view or custom event
        gtag('event', 'section_view', {
          'section_name': entry.target.id
        });
      }
    });
  }, { threshold: 0.5 });

  sections.forEach(function(section) {
    observer.observe(section);
  });
});

4. Respect User Privacy

While Strikingly doesn't have built-in consent management:

// Example: Simple consent check
if (localStorage.getItem('analyticsConsent') === 'granted') {
  // Initialize tracking
  gtag('config', 'G-XXXXXXXXXX');
} else {
  // Show consent banner
  // Wait for user consent
}

Consider:

• Adding a cookie consent banner
• Using Google Consent Mode
• Complying with GDPR/CCPA requirements
• Documenting data collection in privacy policy

5. Monitor Data Quality

Common issues on Strikingly sites:

• Single-page site showing only homepage views
• Section interactions not tracked
• Form submissions not captured
• Button clicks missing
• Bot/spam traffic

See Events Not Firing for debugging.

Strikingly Template Considerations

Different Strikingly templates may affect tracking:

Standard Templates

• Clean HTML structure
• Easy to identify sections
• Consistent event tracking

Custom HTML Sections

• Full control over code
• Can add inline tracking
• May conflict with site-wide code
• Test carefully

App Store Apps

• Strikingly App Store apps may inject their own code
• Potential conflicts with custom tracking
• Audit App Store apps for tracking impact
• Remove unused apps

Common Strikingly Sections to Track

Track engagement with key Strikingly sections:

Code Injection Best Practices

Header vs Footer Placement

Header Code (Recommended for Tracking):

<!-- Add to Settings → Advanced → Custom Code → Header Code -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXXXXX"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());
  gtag('config', 'G-XXXXXXXXXX');
</script>

Footer Code (For Non-Critical Scripts):

<!-- Add to Settings → Advanced → Custom Code → Footer Code -->
<script>
  // Non-critical tracking or third-party widgets
  // Loads after page content
</script>

Async and Defer Attributes

Always use async or defer to prevent blocking:

<!-- Good: Async loading -->
<script async src="https://example.com/script.js"></script>

<!-- Also good: Deferred loading -->
<script defer src="https://example.com/script.js"></script>

<!-- Bad: Blocking -->
<script src="https://example.com/script.js"></script>

Strikingly E-commerce Tracking

For Strikingly Simple Store:

Available Events:

• Product views
• Add to cart
• Purchase completion

Limitations:

• Less granular than dedicated e-commerce platforms
• Requires manual event implementation
• No native data layer
• Must access thank you page for purchase tracking

See platform-specific integration guides for e-commerce setup details.

Next Steps

Choose your integration to get started:

• Install Google Analytics 4
• Install Google Tag Manager
• Install Meta Pixel

For general integration concepts, see the analytics platforms overview.