What is the best way to set dynamic report suites for SC App Measurement Tag?

[james_hartley]

We are currently setting our dynamic report suites for App Measurement Tag by use of extensions for each staging environment. DEV, TEST, PREPROD, PROD. We have 1 extension for each environment that follows the following logic (scoped to all tags). Set reportsuite = to TEXT -- ReportSuteName When domain contains (ignore case) abcdev.com then we map report suite to s_account and so on for each environment. So, we are noticing the following when we are calling multiple tags on page loads: At times, 1 tag (usually the 1st tag to load) will only send data to the default report suite within the tag settings as opposed to the report suited being set within our logic. We are considering adding code to a pre-loader extension to set our report suites to solve for this. Any ideas?

[ty_gavin · Accepted solution]

Looks like a template bug. It has the "s" in there.. We should be able to fix and push this out tonight. // This s.account=b[c]; // Should be u.o.account=b[c];

[james_hartley]

Thanks Ty!

[james_hartley]

Hey Ty, should I put a support ticket in for this?

[ty_gavin]

Did you delete your SC App Measurement tag template? And you are still seeing an issue? If yes, then probably best to submit a support ticket. Also, as an FYI.. We plan to update the App Measurement library code to the latest version this week. You will see another dropdown option in the tag config.

[james_hartley]

Hey Ty, We are still having this issue and is specific to our implementation I think. it appears that one of our calls is happening prior to DOM ready which is causing some issues. I emailed Melissa directly on this. I am still not seeing a dropdown in the tag config - was the change you mentioning implemented? Thanks

[ty_gavin]

When you click "Edit" to edit the tag config, you will see the "1.21" option for the "Code Version"

[james_hartley]

Yes I saw it, FF was acting goofy. I will give this a shot and see what happens.

[james_hartley]

We were able to resolve this today with Jared. Thanks for the help!