Staging and production datastreams

You will now want to go through the same steps again two more times: once for your staging environment and once for your production environment. Following are a couple of notes as you set up these additional two datastreams.

The staging datastream

  • When naming the datastream (and when adding the description), you can/should have the same name with the difference of adding “staging” instead of “development.”
  • Add the Adobe Analytics service, as you did before, and set the report suite to the same development report suite.
  • If you’d like a cleaner environment for looking at staging numbers in your Adobe Analytics reports, you can create a new report suite just for staging, and then make sure that you are pointing to that report suite in this datastream’s Analytics service.

The production datastream

  • When naming the datastream (and when adding the description), you can/should have the same name with the difference of adding “production” instead of “development.”
  • When choosing the report suite to map the data to, instead of choosing the development report suite or even a new report suite, you can map this datastream to your current production report suite being fed by the AppMeasurement implementation. That way, after you have completed the migration and have tested it and are happy with the numbers, you can remove the old AppMeasurement code, send the Tags libraries through to production, and you will be feeding the new production data into the same production report suite, so that you will have continuity between old and new implementations.
Previous page2. Create a validation report suite
Next page4. Add the Web SDK extension