​
Testing Your Attribution Setup

After implementing the Reach attribution snippet, it’s important to verify your setup through a series of tests. Since attribution involves multiple components working together, we’ve structured the testing process into clear stages.

​
Stage 1: Verify Script Implementation

First, confirm that the script is properly installed on your pages:
  1. Open your website in Chrome Developer Tools (press F12 or right-click and select “Inspect”)
  2. Go to the Network tab and filter for “analytics.js” or “embedreach.com”
  3. Refresh the page and verify the script loads successfully with a 200 status code
  4. Check the Console tab for any errors related to the Reach script
Successful outcome: The script loads without errors in the network panel and console.

​
Stage 2: Verify Configuration Parameters

Next, confirm your PARTNER_HASH and TENANT_EXTERNAL_ID are correctly implemented:
  1. Check that the script URL in your implementation contains the correct values: 
    <script src="https://public.embedreach.com/scripts/:PARTNER_HASH/:TENANT_EXTERNAL_ID/analytics.js"></script>
  2. Verify your PARTNER_HASH matches the value provided by Reach
  3. Confirm that your TENANT_EXTERNAL_ID matches the business ID in your platform
Important note: The tenant must already be created in your system with the correct external ID that matches what’s in the script.

​
Stage 3: Test Attribution Flow

Attribution testing can only be completed after Reach has finished the instrumentation process for your specific client. This typically occurs during the business onboarding phase and may take 1-3 business days after submitting client information.
Once Reach confirms instrumentation is complete, test the full attribution flow:
  1. Create a test marketing link with UTM parameters: 
    https://yourbusiness.com/landing?utm_source=test&utm_medium=email&utm_campaign=test
  2. Open an incognito/private browser window and click on your test link
  3. Complete an identification action (form submission, account creation, etc.)
  4. Check the Reach dashboard after 5-10 minutes to verify the attribution event was captured

​
Debug Tools

​
Debug Mode

Add reach_debug=true as a URL parameter to enable detailed console logging: 
https://yourbusiness.com/landing?reach_debug=true
With debug mode enabled, you’ll see script initialization and configuration events logged to the console in real-time.

​
Cross-Domain Testing

If you’re using Reach across multiple domains:
  1. Verify the script is properly installed on both domains (Stage 1)
  2. Confirm both scripts use the same TENANT_EXTERNAL_ID (Stage 2)
  3. After instrumentation is complete, test the full flow across domains (Stage 3)

​
Troubleshooting Common Issues

IssuePossible Solution
Script not loadingCheck your CSP settings and script URL
Attribution not workingConfirm that Reach has completed instrumentation for your client
Cross-domain issuesVerify the script is on all relevant domains with matching tenant IDs
Form submissions not trackedWait for Reach to complete form selector setup during onboarding
If you’ve verified all stages and still encounter issues, please contact support@embedreach.com with:
  1. Your PARTNER_HASH and TENANT_EXTERNAL_ID
  2. URLs where the script is implemented
  3. Any console errors observed
  4. Description of the expected vs. actual behavior