Configure Spectacle Server-side Tracking

This guide explains how to set up Spectacle Server-side Tracking in Google Tag Manager (GTM) and TAGGRS, using either the template configuration or a manual setup. Follow these step-by-step instructions to capture GDPR-compliant, first-party data, track key events, and improve marketing attribution accuracy.

The Spectacle Server-side Tracking Tag is built to capture reliable, first-party data across all browsers with ease.
By processing events in your TAGGRS server container, tracking stays accurate even when browsers block cookies, apply Apple’s ITP, or ignore scripts. This ensures a complete view of your audience, accurate attribution for Safari users, and clearer insights to optimize campaign ROI.

Setup note
Spectacle’s GTM integration is designed for a server-only implementation. Avoid mixing client-side Spectacle scripts with a server container, as hybrid setups aren’t supported. All configuration should be done in TAGGRS’s server container, ensuring a single source of truth for each event, no double-counting, and a clean data flow from your site into Spectacle.

Template configuration (Option 1)

The simplest way to get started is by using the pre-built GTM template provided by Spectacle and available on GitHub.

1. Download the template

Get the JSON file from the SpectacleHQ GitHub repository.

2. Import into TAGGRS

In your TAGGRS account, open your GTM server container and import the JSON file using the Templates or Import feature in the TAGGRS UI.

Expert insight
Make sure you’re importing into a server container, as web containers will not accept it.

3. Set variables and publish

After importing, open the template in your container. Enter your Spectacle workspace ID (found in your Spectacle dashboard) along with any other required fields.
Save and publish the container.

where to find the Spectacle ID to set up server-side tracking by using the GTM template

The template comes with built-in configurations for pageviews, identify calls, and track calls. You’ll need to run the base template to capture pageviews, and add separate identify calls for form submissions or important events.

How to set up custom events in your Spectacle server-side tracking tag with TAGGRS

How to set up another trigger in your Spectacle server-side tracking tag

Once published, your data will start flowing into Spectacle immediately.

Manual setup (Option 2)

If you prefer to configure everything yourself, follow these steps:

1. Create a server container

In TAGGRS, add a new Google Tag Manager server container if you don’t already have one.

2. Match triggers in the server container

Set up triggers in TAGGRS to capture the same events (e.g. pageviews, form submissions, signups) as your web client.

3. Configure a Spectacle tag

Add a new tag in the server container to send data to Spectacle.

Use a Pageview tag to track all pageviews.
Use an Identify call on login buttons, registration buttons, or any form submissions.
For intent-driven actions (such as pricing page visits or clicks on "call me back"), use a Track event.

That’s it for manual setup. Your GTM server container is now connected to receive events from your website and forward them to Spectacle’s API.

Event tracking

When defining events, focus on the touchpoints that drive conversions. Common examples include:

Pricing page view

A visit to your pricing or product plans page, often a strong intent signal.

Demo request submit

A visitor submits a "Book a demo" or contact form. Count this as a conversion event.

Sign-up or trial start

A user completes your sign-up form or trial registration, marking a new lead or customer acquisition.

Sending events server-side

Sending these events server-side ensures they fire even if the browser blocks scripts. In practice, you can:

Fire a tag on all pageviews, then filter it in TAGGRS to act only on key URLs (e.g., /pricing or /signup).
Add tags for form-success events, such as demo requests or sign-ups.

By capturing pricing and sign-up events in your server container, you provide Spectacle with the complete journey data needed for accurate server-side tracking. This way, your attribution model won’t miss a single lead or paying customer.

Test and validate

Before going live, validate your setup:

Use GTM’s Preview mode: Enable preview/debug for both your web and server containers. In the web preview, navigate through your site and watch the tags fire. Then check the server preview to confirm the same events pass through the container. Ensure pageviews and form submissions are triggering the correct tags.
Check TAGGRS logs: In the TAGGRS dashboard, go to Server GTM Logs. Event requests should display the correct event types (e.g., “PageView”, “Submit”), confirming the data is flowing properly.

Expert insight
If you see a 400/404 status in the logs or missing event names, double-check your tag configurations and endpoints. The logs are invaluable for spotting typos or misfires.

Once you’ve confirmed the flow end-to-end, publish your GTM containers. After going live, head over to Spectacle’s Attribution Reports. You should soon see pricing page visits, demo submissions, and sign-ups appearing in your data.

Well done, you now have reliable, first-party tracking set up with Spectacle. Go forth and optimize your campaigns with confidence, knowing your data is bulletproof.

Happy tagging!

Useful resources

TABLE OF CONTENTS

Template configuration Manual configuration Event tracking Sending event server-side Test and validate Useful resources