Skip to main content

​
Implementation Components

Every Reach implementation has three core integration points, though not all products require all three:

​
1. Frontend UI Embedding

What: The Reach interface that your customers interact with Responsibility: Partner implements Required for: All products Technical Details: Embeddable UI docs You’ll embed Reach’s UI into your application, typically as an iframe (recommended for speed and automatic updates) or React component (for deeper customization). This requires creating a backend endpoint that generates JWT tokens to authenticate users.

​
2. Data Sync

What: Sending customer, transaction, and other data to Reach Responsibility: Partner implements Required for: All products Technical Details: Data Sharing docs At a high level, Reach expects the following:
  • For all industries: Customer lists – sync these to Reach as customers are created/updated.
  • For industries with online transactions: Transaction/order data is the most helpful, shared soon after the transaction occurs. This data should include both the overall price paid and also the goods or services that the transaction is for.
  • For industries with contracts billed over time: Contracts/proposals/agreements will be most helpful, shared after the agreement is finalized. It is OK if these are amended over time.
  • For industries with invoicing: Invoice data is more helpful than when the charge is completed since it best describes the purchase – even if the invoice has not been paid (i.e. if the monetary transaction has not occurred).
Reach creates flexible schema definitions that match your existing data structure—you don’t need to transform data to fit rigid requirements. You can also send Reach other types of data, which will be discussed during the onboarding process, but at a minimum we need a copy of the above data.

​
3. Attribution & Tracking Snippet (Only for Acquire/Measure)

What: JavaScript snippet that tracks customer behavior and form submissions for attribution Responsibility: Partner implements on their own forms; Partner’s customers (Tenants) implement on their external marketing sites (if applicable) Required for: Measure, Acquire Technical Details: Tracking & Attribution docs

​
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, organic search, social media, etc.
  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.

​
Let’s Get Started

Now you’r ready to take the first steps toward embedding Reach and providing your customers with a powerful suite of marketing tools.

Phase 1: Credntials & Setup

Getting your Reach credentials and initial setup