website logo
Navigate through spaces
⌘K
OVERVIEW
ORDER MANAGEMENT (OMS)
SHIPPING - SETUP
Shipping Methods
Shipping Zones
Shipping Method Setup Examples
TAXES - Setup
Tax Automation with Stripe Tax
Tax Automation with Avalara
CONTENT MANAGEMENT (CMS)
DATA
CUSTOMER LIFETIME REVENUE
Customer Lifetime Revenue Explanation
Customer Lifetime Revenue and Purchase Likelihood
Recency Frequency and Monetary
CLR and RFM Data Table Glossary
RFM and CLR in the Hub
LOOKER
Modifying a Dashboard
Timestamp differences between Looker, OMS and Shopify
How to create custom calculations in Looker
Looker and Shopify data models
Custom fields
How to 'Save and Schedule' reports
Creating Custom Reports or Look
Looks vs Dashboards
Login Looker FAQ
Looker Glossary
SEGMENT EVENT TRACKING
What are event tracking
Adding Tracking
What is the Tracking Plan?
The Chord Tracking Plan
The Shopify Tracking Plan
Event Tracking FAQ
EVENT UPDATES PAGE
Email Subscription Payment Event Update
Product Feed Setup
Getting Segment to Production
Consent Management
Installing in Next.js
Installing in Gatsby
Integrations
👩‍💻Developer Tools
Using Chord with Shopify
Docs powered by archbee 

Getting Segment to Production

3min



Introduction

As an autonomy customer, by default, Chord provides you with Sources for your Front-end and Back-end Staging environments... During the testing phase, it is recommended that your Destinations point to the Staging Environments.

Once you are ready to move to Production, Destinations should link to the Production Source.

Let's take a look below.



Your Productions environments will be set up by your agency when you are ready to move to Production.

Verifying Keys

Each Store has its own Write Key, a unique identifier that points to and funnels data to the right source.

When you are moving out of the testing phase and going Live, your Production environment will have its own Write Key, which must be added to your front and back end.



Document image




Back-end



Navigate to your Production environment in Segment and click Connections --> Sources.

Search for your newly added <YourStoreName> Back-End (Production).



Sources Production
Sources Production




Click on Settings ---> API key





Write Key
Write Key




Copy the Write Key and navigate to your Production OMS

Go to Settings --> Store --> Environment Variables





Environment Variables
Environment Variables




Paste the key in SEGMENT_WRITE_KEY and click Save



If SEGMENT_WRITE_KEY Variable is not listed, scroll down and add it and click the + to save



Front-end



Navigate to your Production environment in Segment and click Connections --> Sources

Search for your newly added <YourStoreName> Front-End (Production)



Snippet
Snippet




Copy and Paste the snippet to the <head> tag in the HTML file





Verifying Destinations connections

If you have Destinations that are connected to your Staging Source, and want to connect them to your newly added Prod environment, navigate to your Sources.



Connection - Sources
Connection - Sources




Click on your Front or Back-end Production source and click Add Destination

Select your App and click Configure <App Name>

You will be able to copy the existing setup to your Production Env





Copy existing settings
Copy existing settings


We suggest that the Destination name * refers to your Production Environment: Ex:

Google Analytics (Production)

Click Save

Your settings have been saved, you just need to enable the Destination



Settings have been copied over
Settings have been copied over


We recommend that you disable the Staging connection to avoid conflicts in data/analysis





if you have any questions or need help, please reach out to us at help@chord.co



Updated 17 Apr 2023
Did this page help you?
Yes
No
PREVIOUS
Product Feed Setup
NEXT
Consent Management
Docs powered by archbee 
TABLE OF CONTENTS
Introduction
Verifying Keys
Verifying Destinations connections