Setup (Unify)

Environments and API Keys

You can create as many environments as you need — one per deployment stage. For correlation to work, your marketing site and product app must both use the API key from the same environment.

The rule: for end-to-end correlation, your marketing and product analytics must use the same API key. Different keys = different environments = no correlation.

Your environments, your keys

Create as many as you need. Each one gets its own unique API key.

Production
API key
a1b2c3d4e5f6g7h8…d4e5f6g7h8…
Staging
API key
x7y8z9w6v5u4t3s2…
Development
API key
p4q5r6m3n2l1k0j9…m3n2l1k0j9…

Three separate environments — three separate keys. Events from each stay isolated.

How correlation works

Your ThriveStack environment is where the data lands. Each stream that reaches it is tracked — correlation only activates when both streams are present.

Wrong API key on product analytics — telemetry not flowing in
your-marketing.com
Key a1b2c3…
app.your-product.com
Key p4q5r6… wrong env
→
→
ThriveStack — Production
Marketing Analytics receiving
Product Analytics no events
Correlation not possible
Same API key on both — both streams flowing in
your-marketing.com
Key a1b2c3…
app.your-product.com
Key a1b2c3…
→
→
ThriveStack — Production
Marketing Analytics receiving
Product Analytics receiving
Correlation active

The environment exists in ThriveStack — but if the wrong API key is used in your product app, its events never reach it.

What breaks silently

Visitor-to-user attribution is lost — ThriveStack can't connect an anonymous site visit to the account that eventually signed up.
The full account journey is incomplete — UTM parameters, marketing touchpoints, and time-to-signup are missing from every account record.
No error is thrown — events from both sides arrive in ThriveStack, they just can't be correlated.