- TLC Home Home
- Discussions Discussions
- Documentation Documentation
- Knowledge Base Knowledge Base
- Education Education
- Blog Blog
- Support Desk Support Desk
05-09-2016 09:40 AM
05-10-2016 11:18 AM - edited 08-03-2016 02:33 PM
After further testing the option I purposed earlier does not give the desired results. I am pulling the post down. See Adrian's comments below.
05-10-2016 12:11 PM
05-10-2016 01:03 PM
@tglaittli As someone that is new to Tealium, I would encourage you to leverage your Tealium Deployment team. You can point them at this post and they will be able to add this as part of your initial deployment. The mappings are pretty much drag and drop and the code sample provided can hopefully be copy/pasted into a DOM Ready Extension.
05-10-2016 02:54 PM
Hello @tglaittli. Let me see if I can find your account manager. Stay tuned...
05-10-2016 03:01 PM
Okay, found them! @Anonymous and @steve_thurner should be reaching out to your shortly @tglaittli. Let us know if you have any other questions.
05-12-2016 05:20 AM
Just a heads up on error tracking. Most likely you will just see the generic:
"Script Error", "line 0"
As the utag files do not contain the cross origin header that would allow us to capture more details.
06-17-2016 08:49 AM
06-28-2016 04:06 AM
At present I do not believe we have any plans to add this header to the CDN files.
I would recommend raising this request through your account manager.
If you really wanted this information, at present, you would have to host the files on your own network, at which point the cross origin issue is removed. But also so is the benifits of the mCDN.
Copyright All Rights Reserved © 2008-2023