Skip to main content

​
Overview

When needed: If implementing Measure (analytics) or Acquire (ad management) Phase 8 implements the JavaScript tracking snippet that enables attribution—connecting anonymous website visitors to known customers and ultimately to revenue. For all technical details of implementing tracking, please see Introduction to Attribution and Tracking.

​
What the Tracking Snippet Does

The tracking snippet creates a complete attribution chain from initial visitor to converted customer:

​
1. Visitor Identification

When someone lands on a page with the snippet, Reach generates a unique anonymous identifier for that session.

​
2. Source Tracking

The snippet captures where visitors came from:
  • UTM parameters
  • Referrer URLs
  • Ad clicks (Google Ads, Meta)
  • Organic search
  • Social media
  • Direct traffic

​
3. Cross-Page Tracking

As visitors navigate between pages (marketing site → your booking form), the snippet maintains their identity and source attribution.

​
4. Identity Resolution

When a visitor provides their email or phone number, the snippet links that personally identifiable information to their anonymous session and original traffic source.

​
5. Conversion Attribution

Later, when you send transaction data to Reach with that same email/phone, Reach connects the revenue back to the original marketing source.

​
Why Partners Need to Implement It

Your booking forms are where the critical “identity resolution” moment happens—when an anonymous visitor becomes a known lead. Without the snippet on your forms:
  • Reach can track that someone came from an ad
  • But cannot connect that visitor to the transaction data you send later
  • Attribution breaks—you can’t show which ads drove revenue
The snippet must be in your application because that’s where your customers’ end users convert into leads.

​
Implementation Steps

​
Step 1: Add Tracking Snippet to Your Forms

Add the Reach tracking snippet to pages you host where visitors identify themselves. This is any marketing landing page, booking form, checkout form, quote form, or other type of page that you host for your clients.

​
Step 2: Implement createIdentification Calls

When a visitor submits a form with their email or phone, call createIdentification.

​
Step 3: Provision Snippets for Your Customers

Your customers may have their own external marketing websites. Provide them with pre-populated tracking snippets during their onboarding. This will look something like 
<https://public.embedreach.com/scripts/123456789/acmemoving/analytics.js>

​
Step 4: Feature Flag for Acquire vs Measure

Add a feature flag to give Acquire to customers paying for it and Measure to customers only paying for Measure. It is up to you to detemine which of your customers has access to which.
Acquire includes all Measure functionality plus ad campaign management. Measure is analytics-only.

​
Your Customers’ Responsibilities

​
For Acquire/Measure Customers

1. Add tracking snippet to external marketing websites If they have their own landing pages or websites not owned by your platform, they need to add the tracking snippet. 2. For Acquire: Grant access to ad accounts
  • Google Ads account access
  • Meta Business account access
  • Google Tag Manager (if using)
This is not an implementation step you need to handle. This is done when businesses activate the product by OAuthing within Reach’s embedded UI.

​
Reach Helps With

  • Verifying tracking is working correctly (manual check via Slack)
  • Additional form tooling for customers who have their own sites and forms
  • Troubleshooting attribution issues
  • Sets up and runs ads for customers using Acquire

​
Advanced: UTM Parameter Handling

The snippet automatically captures UTM parameters from URLs: 
https://yourbookingform.com?utm_source=google&utm_medium=cpc&utm_campaign=spring_sale
These are automatically associated with the visitor session and carried through to attribution.

​
Troubleshooting

Check:
  • Script URL is correct
  • No Content Security Policy blocking
  • No ad blockers interfering
  • Browser console for errors
Check:
  • createIdentification is being called
  • Email or phone is provided
  • Network request succeeds (200 OK)
  • tenantId is correct
Check:
  • Snippet is on ALL pages in user journey
  • createIdentification called with same email/phone as transaction data
  • Transaction data is being synced to Reach
  • Customer IDs match between identification and transaction

​
Phase 8 Checklist

Tracking snippet added to your booking/lead forms
createIdentification() implemented on form submissions
Snippet provisioning system built for customers
Feature flag implemented for Acquire vs Measure
Testing completed (snippet loads, identifications record)
Reach team notified to verify tracking
Attribution tested end-to-end

​
Integration Complete!

Congratulations! You’ve completed all 8 phases of Reach integration.

Integration Overview

Review the complete integration guide