Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Coffee Break: Join us on Wednesday, April 5th at 10am PT to chat with Ben Gaines, Director of Product Management for Adobe Analytics. Ben will be online to answer your Analytics and Adobe Summit questions.
SOLVED

Test-Website Analytics, Do or Don\'t?

Avatar

Level 2

Currently we are running some analytics tests using our test-website domain and we have it all in the same property for Tags/Launch as our main domain. What are others finding to be best practice here? Do you run analytics on your test-site? Do you try out new rules there first? Do you keep this in the same property or a different property (Launch/Tags)?

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Personally I like to have 1 report suite for prod. 1 report suite for dev/stg

This way data cleanliness is one factor as well as incase some thing does break its just stg.

 

The launch rule is universal just the report suite it runs against/populates into is different.

 

good luck

3 Replies

Avatar

Level 2

I guess I should be more specific:

If we have test-domain set up for dev environment, staging-domain, set up for submitted/staging environment, etc, does anyone see the need to set up a separate property that we test rules through, or is that just redundant? 

Avatar

Correct answer by
Community Advisor

Personally I like to have 1 report suite for prod. 1 report suite for dev/stg

This way data cleanliness is one factor as well as incase some thing does break its just stg.

 

The launch rule is universal just the report suite it runs against/populates into is different.

 

good luck