This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Follow us on Twitter for more information on our products. The unimportance of productnames. Don’t waste too much time on picking a perfect name for your product. We usually decide upon a productname by seeing what the product does. Everybody knows what a productname should be.
There are two kinds I enjoy: one is highly creative, like company or productnaming. The guys that created Ruby On Rails take that point even further in their recent book, REWORK. Everyone should have a professor with that degree of interest in their writing. Please tell us about your favorite projects.
So, for tracking product-specific things in Tealium iQ, you would, for instance, have one Data Layer Variable with product IDs and one with productnames, much like tracking in Adobe Analytics —but certainly not like defining one JSON object per product that contains all its data, like in Google Tag Manager.
So, for tracking product-specific things in Tealium iQ, you would, for instance, have one Data Layer Variable with product IDs and one with productnames, much like tracking in Adobe Analytics —but certainly not like defining one JSON object per product that contains all its data, like in Google Tag Manager.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content