GA tags for Testing/Production environments

[neil_gogate]

We're using Coremetrics and GA through Tealium and CM allows us to define the test/dev through the tag, but it doesn't look like GA does. If we have 1 account to capture all the prod data in GA, do we have to set up a separate tag to capture test data or is there a way to make sure that all test/dev data is going to the separate dev account through the original tag?

[dan_george]

Hi Neil, Great question. The best way to handle this is with one tag instance that makes use of a lookup table. - create a new Data Source called "google_account" - add a new Lookup table extension - scope to Google Analytics - Lookup Value In: select "domain" - Destination: select "google_account" - keep the other options as the default - Lookup Match: enter a test domain e.g. www.tealium.com (no protocol or slashes) - Output: enter the test Google account number - move to the Tags tab - "Edit" the Mapped Data Sources - choose "google_account" from the drop-down - click the "Select Destination" button - when the Mapping Toolbox modal appears, select "Account (Override Default)" - Save/Apply/Publish all changes This will run the lookup table each time the Google tag runs and dynamically override the setting in the default tag configurations.

[neil_gogate]

Thanks Dan, if we have multiple test environments, can we simply put in a semicolon in the lookup match so that it captures information from all those domains? Conversely, might it be easier to create something that looks for just the production domain and then sends everything else to the test/dev account?

[Clint]

with multiple test environments, you can either add a new condition per environment in the lookup table or use the regex condition (instead of 'equals' in Dan's example).

[rick_sampson]

Would it basically work the same way if you wanted to do this for SiteCatalyst/Adobe Analytics?

[dan_george]

Hi Rick, you'll want to change the "Use Dynamic Account" drop-down to "Yes". Then you'll want to add your domains to "Dynamic Acct List" using a semi colon separated list of report suites and domains, i.e.: reportsuite1=dev.site.com,stage.site.com;reportsuite2=site.com For more details on Dynamic Acct List, please read: http://omniture.custhelp.com/app/answers/detail/a_id/1440 For more details on configuring the SiteCatalyst tag in Tealium, please read: https://community.tealiumiq.com/posts/548398

[rick_sampson]

I am using SiteCatalyst App Measurement for JS, not the legacy H tag. Dynamic Accounts is not one of the current options for that template, correct? So would the Lookup Table approach be the best alternative?

[jared_hislop]

Hey Rick, Yes, the lookup table would be the best approach using the AppMeasurement tag. Then you would map the output variable back to s_account in the tag mappings. One note about the lookup table would be to include the default output. Typically this could be the dev report suite. That way you only have to define your production domains in the lookup table and all other traffic, not on a production domain, will get defaulted to dev report suite.