I'm quite new to TMS and I thought it worth sharing my experiences of Tealiumâ s product and service after a few monthsâ use.
Like many products, the interface is quite daunting and not always easy or intuitive to follow. But with increased familiarity Iâ m getting better at knowing what to do.
Crucially, the product has so far delivered everything that's been required of it - an Adobe Analytics implementation covering many sites, languages and currencies plus other vendor tags.
In fact so far there hasn't been a requirement that couldn't be met!
Which brings me on to the purpose of this post ...
... to say a great big "thank you" to Craig and Adrian (UK team) for outstanding support when it comes to customer service and getting the config to a high standard. On behalf of my client I'd like to say we couldn't have expected more.
Thanks so much for the feedback! I'll make sure that Craig and Adrian see this.
If there are specific things that you think could be improved in terms of usability/intuitiveness feel free to let me know (you can go to my profile and message me directly if you prefer).
Jonathan, thank you so much for your feedback - truly appreciated and I'm very happy you have had such a positive experience using Tealium. I will be sure to pass on the appreciation to Adrian and Craig.
Initially my challenge is familiarity and training - so user not interface related.
I don't write JS so need support in these areas - hence Craig and Adrian being invaluable and again user not interface related.
Initial interface confusion is when I need to jump around a data sources, tag, mapping, extension screen etc. May be aspects of the product could have a wizard or links to other components of the tool that I'm likely to have to have to configure next. Familiarity will help me here.
â Savingâ a version is my biggest current concern:
1) If I'm working on a change I want an ability to ensure that my changes cannot be picked up and published by anyone else. Eg, to get my Channel Stacking and related reports to work as intended may take me several hours work over several days and what happens to my work if someone wants to make a separate 2 mins change? The Adobe Tag Manager interface very clear and easy to use in this regard with clear sections to keep versions in dev, staging or prod (perhaps because the product is quite basic).
2) I would expect that every change is auto saved rather than having to do a â save asâ .
And (3) a rollback button would be useful too perhaps.
The web companion wasnâ t clear re which mode Iâ m in, eg dev or prod, but I can see this has been updated this week - great. Related to this, Craig did a neat extension to auto populate the version no and a reference (eg â devâ or â prodâ ) which was mapped to an Adobe Analytics Prop meaning I always know the version and environment status of every server call when using a debugger or the reports. I suggest you make this a standard extension available to everyone.
Finally (for now), the Channel extension could be easier to use; perhaps this is familiarity again. I mentioned my initial ideas to Adrian yesterday but in summary Iâ d like to create the following outputs to replicate / replace what Adobe Consulting would have to do using custom code for the s_code:
1) Stack my channels; eg â PPC > SEO > Emailâ etc
2) Stack keywords; either SEO only, PPC only or either (eg â ppc|keyword-1,seo|keyword2,|ppc,term3â etc
3) Stack time between Channels; eg â 0 > 1 > 5 >0â etc where â 0â indicates the same day
4) Stack channel and time in the same report
5) Have versions of the above that I could configure to reset each day (to see how many channels are used in a single day when there is a conversion), and also set a custom date range etc
6) Look at attribution weighting perhaps sometime in the future
Right now Iâ m tackling (1) above with the extension. My client has many ways that people track a campaignâ s channel and campaign tracking code (the tracking syntax isnâ t consistent across brands and countries for the QSP or the tracking code itself), so setting the Extension rules will probably take me a lot of trial and error. Therefore, I would like to see an ability to drag channel rules higher and lower in the hierarchy rather than recreating them each time I need to make a change to anything but the bottom rule.
Also, I would also like to see an ability to add another level to each condition; similar to how the Adobe Analytics works re Processing Rules etc. Eg, â query string >> contains >> abc >> and value >> contains >> xyzâ .
I hope the above makes some sense.
Loving the product and actively recommending it.
In the exentions page, add line numbers to each entry so you don't get as lost when scrolling up an down a page and moving extensions around.
Also, perhaps each entry needs an ID which remains static.
And finally, add sortation and search funcationality to each column header in this report.
Awesome critiques Jonathan!
I may want to follow up "offline" re: Channel extension. As you know (I'm sure) Channel attribution is complex (there are whole companies that do nothing but) so anything we can do to simplify the usability of the extension while maintaining/extending it's functionality is very interesting to me.