Currently in Tag Configuration Design for CoreMetrics, there is an option for Test Domains which implies that whatever domains you mention in this field would go to Test Client Id and rest would go to production. Consider scenario:
- If a new test domain comes up and if developers have no idea on the Tealium settings since the guy looking after Tealium is more of an Analytics guy.. quite unfortunate condition!.. .This means all the data of the new test domain will go to Production Client Account!! Literally I'm scared with this setting.
Rather it should have been an option for Production Domain (since it is known and would be only one in my case) and anything other than that should go to Test Client Id.
Let me know if it make sense. Thanks in advance.
Thanks for the idea, and I can understand what you're saying.
One way to solve for this would be to create a Lookup Table Extension that outputs the clientID. You call do a check the domain, and output various values based on the domain value. In the 'Default Output' field you would put the Test Client ID. This way if there isn't a match in the Lookup Table (i.e. any new dev sites) then the Test Client ID will get set.
Make sure all production domains are specified in the Lookup Table. However, not all dev domains need to be explicitly set because the default output will pick all of those up when there isn't a match in the table.
Personally I like this method better anyway because if you have a long list of domains, this is easier to manage and visualize.
Then you would map the output variable back to the CoreMetrics tag as the clientID. The ClientID can be found in the Config Tab within the Mapping Toolbox.
Hope this helps.
Tealium Extensions are vendor neutral. So you are correct, there is not an option to set the CoreMetrics Client ID directly from the Lookup Table Extension. You've got to create a variable, something like "cm_client_id", and set that as the Output Destination.
Then in the Mapping Toolbox for the CoreMetrics Tag you will select "cm_client_id" and map that to ClientID.
Is it going to over-ride the Tag Configuration settings? I.e. I've defined Client ID/ Test Client Id and Test Domains in Tag configuration. Should I keep those values as is or that needs a modification?
This will overwrite those settings. However, if you have a Test Collection Domain that is different then your Production Collection Domain then you will need to overwrite this as well.
You can create a Set Data Values Extension and set it up like:
Set: cm_testcollection_domain To: Text ""
Conidtion: if cm_client_id does not equal ""
Then map "cm_testcollection_domain" back to the tag as "DataCollectionDomain." This will overwrite that value as well when on a Dev site.