Product Ideas

Our submission guidelines and status definitions before getting started
The community for a solution or existing idea before posting
By kudoing and commenting on ideas you support
A new idea to suggest a product enhancement or new feature
Submit New Idea

Provide a means to auto-publish a tag version to an environment based on conditional states for existing tags.

If we have a tag that requires a future update, it would be great if we could publish the tag to PROD with a condition that date/time >= <time:date>.  This would allow the existing tag to live as long as the date has not yet been reached but will automatically be swapped with the updated tag at the appropriate time (much like the load rule).

Currently the only option (that I'm aware of) is to duplicate the tag, modify the new tag and then hot swap the two at the appropriate time either manually or by setting a live/die load rule on the new/old tag.

Status: Acknowledged

Okay got it @PhillipMarquez. I shall move this request to Acknowledged. 

Audiencestream OMNICHANNEL: Show connection status

Status: Acknowledged
Submitted by dsavvy83 a week ago - last edited a week ago Submitted by Community Manager

Having issues with testing the link has been made, there is absolutely no feedback to tell me something has happened and it is all going well. 
It will be great to add some kind of information on SFTP or FTP connections to check connection has been made and data ingested.

Also would be great to direct SFTP account to a folder and not just the root,

It will be great if this can be done pretty soonish, thanks

Status: Acknowledged

@dsavvy83 Thanks for this idea. I adjusted the title for clarity.

Background: We are working on improving the stability of custom javascript we are deploying through Tealium. We have many of the extensions in various npm packages to allow us to unit test the scripts,transpile, run a webpack build and then copy / paste the output into Tealium.

This process is working great so far with the exception of templates. We are only managing the Multi-Opt out template this way due to the heavy customizations we have made but Tealium templates use values like ##UTTAGSOPTOUT##. I know these types of values get swapped out as Tealium does its compile process but since these values are not valid for JS variable names node/unit testing frameworks/linters/webpack (pretty much all dev tools outside of Tealium) break when encountering these values.

It would be great if these values were strings like '##UTTAGSOPTOUT##' and then the compile process could replace the string, as string replacement is a very common approach in this type of situation.

Status: Acknowledged

 Hello @rhanes. Excellent idea. I have moved it to Acknowledged

Quite often we need to change tag templates to be able to run them with function.

Except that we don't really touch tag templates. It would be great to be able to add support for


directly from configuration menu (see attachment)2018-02-08 13_42_11-Tealium iQ - Tag Management.png

Status: Acknowledged

Hello @daniel7. Thank you for the idea. It looks like you have quite a few fans of your idea. I have moved this to Acknowledged

Git/Github integration

Status: Being Considered
Submitted by oaustegard on ‎01-18-2018 12:16 PM - last edited on ‎01-18-2018 04:25 PM Submitted by Community Manager

As a product owner, I enjoy the flexibility that Tealium provides, but do not like that the development and deployment proces bypasses all of our Software Development Best Practices. To aid in this I would like to be able to integrate Tealium directly with Github so that code is backed up, pull requests can be made, code can be reviewed, and tests written and executed, as with other JavaScript deployed on our web pages.

Status: Being Considered

@oaustegard This is a good idea. It's amazing to see how advanced the integration needs have become for the iQ release process.

We had a major incident today and it was simply because someone accidentally had moved an Extension down in the operation of order. When preparing the next Production publish, I reviewed the changes and since I did not see anything relevant, I published.

The next day we had major data problems (won't go into the details).

I could blame the agency developer who did it, but I think it is Tealium's fault because what good is the Version Control if it does not document ALL changes to the code? And moving a piece of code from place A to B is definitely a major change, so it just HAS to show up in the Version History. 

We had similar problems in the past, but this one was so big that I have to bring this up here.

So moving the ORDER of Extensions (or Tags) should show up in the Version Changes overview and be a part of the "Merge Changes" feature.

Another big help would be a Version History per Extension like in Adobe Dynamic Tag Management. It would be so much easier to go into an Extension and view at least the last 10 changes to it than to browse through the Version names in the Version Tab which are truncated to near illegibility (truncation is for lazy designers).

Status: Acknowledged

Thank you for the idea @loldenburg. I have moved this to Acknowledged

Duplicate extension between profiles

Status: Being Considered
Submitted by rune_a on ‎01-11-2018 03:22 AM - last edited on ‎01-17-2018 10:12 AM Submitted by Community Manager

A simple option to duplicate an extension to another profile(s).

This is not possible today  - and that is a strange limitation.
To prevent failures, the extension can just be disabled by default when duplicated to other profiles.

extension dublicate.png

Status: Being Considered

@rune_a Thanks for this idea.

Enhance event specifications to add a valid/invalid attribute to events

Status: Being Considered
Submitted by martin_vinter on ‎02-20-2018 12:05 AM - last edited 3 weeks ago Submitted by Community Manager

I've been experimenting with event specifications in AudienceStream and I already love it.

It flags pageviews and events that does not have the required variables in the event stream. Valids are green, invalids are red. Simple enough and yet it saves me from hours of tedious testing.

However, it requires me to sit and stare at the event stream. There is no attribute that marks an event as invalid, and therefore, I can't store invalid events anywhere or use them to trigger connectors/audiences. That makes it diffecult to catch events and pages that have little traffic such as rare error messages, pages that are usually hidden and so on.

So the idea is this: whenever I make an event specification it should come with a new attribute in AS that would express if the event is valid, invalid or unmatched to an event specification. In that way I could trigger a connector or a stream and store all the events that aren't kosher. It could also prevent connector errors that really are not caused by faults in AS but in the Datalayer.

As Nathan Flemming from Tealium put it when I asked about it:

"Unfortunately that's not possible but I have to say that's a fantastic idea."



Status: Being Considered

@martin_vinter I concur. Moving this idea to "Being Considered".

Better UI for Mapping variables in separate Tab

Status: Being Considered
Submitted by rune_a ‎01-11-2018 03:16 AM - edited ‎01-18-2018 03:57 AM

Today the actual UI for mapping datalayer to tag in TiQ seems as one of the weakest features. It's in a small modal, with no sorting options etc.


Optimal this was in a tab, with the option to show multiple tags at the same time, sort on columns, batch edit etc. This would provide a much better overview than today.

(Quick mock based on exsisting UI)


It can also be included in the Data Layer tab, where it already shown if a parameter is mapped to a tag, but it does not show the details. 

Status: Being Considered

Love this idea @rune_a. And it looks like I am not the only one. I have moved this idea to Being Considered

Profile Overview Tab in TiQ

Status: Being Considered
Submitted by rune_a on ‎01-11-2018 03:09 AM

TIQ is built around tabs (myIQ, Data Layer, Load Rules etc)

But profiles are only to be selected from a tiny dropdown list, with no added meta-data.

For me a optimal feature would be a "Profiles" tab, with columns of meta-data, as also shown under "myIQ". And option to group profiles by type, business unit etc. Columns can be many but should include tags, variables, extension, users, last publish (dev,qa,prod)

Case: We have +40 profiles today (with many still missing), and are planning to add +20 App profiles in the near future. We will probably end up with 75 to 100 profiles. We really need a easy overview with stat on usage, last publish etc. 

Based on current UI i have made a quick mockup. The UI element is already there in the other tabs.


Status: Being Considered

@rune_a You're on a roll. Keep the great ideas coming!

Lower Case Arrays

Status: Acknowledged
Submitted by bill_tripple on ‎02-09-2018 05:06 PM - last edited on ‎02-12-2018 06:53 AM Submitted by Community Manager

The lower case extension should work on both Strings or Arrays.  For example if I want to lowercase product attributes during product purchases.

The lowercase extention only works with single strings which seems a bit limiting.

Status: Acknowledged

Hello @bill_tripple. Great idea. Thank you for this. I have moved this idea to Acknowledged

OOOoooo I like the extra comment @rune_a. Perhaps another idea is in order? HHHHhhhhmmmmmm......

Proper text editor for Javascript extensions

Status: In Development
Submitted by bjoern_koth on ‎01-09-2018 03:04 AM - last edited on ‎01-09-2018 12:40 PM Submitted by Community Manager

The title says it. The text editor is more or less useless.

13 lines of code visible, no resizing of the editor window

Some sort of distraction free text editor that spans most of the visual area would be great.

Status: In Development

Hello @bjoern_koth. Thank you for submitting this idea. It is already in development. We will notify you when this idea is delivered. 

When you view the details of a UDO variable on the Data Layer tab, it tells you which built-in extensions make use of that variable.

It presumably wouldn't be too difficult to search the code of each JS extension for instances of "_b.variablename_" and "_b['variablename']" where those underscores are replaced with regex expressions for "characters that can't form part of a JS variable name", and you would pick up (presumably) >99% of cases where those UDO variables are referenced from within those code extensions.

So the suggestion is simply to extend the UI within the Data Layer tab to include details of any JS extensions that make use of a given variable alongside the other extension types.

Status: Acknowledged

 Hi @UnknownJ. I like it! I've moved this to Acknowledged

It would be great if we could create folders to group like tags, load rules, etc.

Folders should also accept labels.

Deleting a folder would delete all items inside. This would be useful for cleaning up after a complex campaign has expired.

Status: Acknowledged

Great idea @ben_a! I wonder if there should also be subfolders allowed? I have moved this idea to Acknowledged

Make it possible to clone an action on a connector

Status: Acknowledged
Submitted by martin_vinter on ‎01-25-2018 07:29 AM - last edited on ‎01-25-2018 10:11 AM Submitted by Community Manager

A connector can have multible actions, and often I use almost the exact same settings for each action on the same connector, while only modifying a single detail.

To my dismay, it is not possible to clone an action, so I have to build it over every time. They are quite complicated to make, and if I get a single detaion wrong, it doesn't work and it may take ages to figure out what's wrong.

unless I clone the entire connector and live with the clutter that will produce over time. 

Could you please consider adding the option of cloning an action?

These are the settings I have to get exactly right every time I build a new action for my adform connector - not fun at all:




Status: Acknowledged

Love this idea @martin_vinter. Keep them coming! I have moved your idea to Acknowledged.

Make a "library-update-pause" function on profile level.

Status: Acknowledged
Submitted by rune_a on ‎02-07-2018 01:23 PM

I would like a option to put a profile in "library update pause" mode, so it does not received the lates library changes.
The chnages should be listed as "pending" with details, but i should have the option to save or publish whitout including them. 

This would be helpfull when we want to publish a PROD version, based on a tested QA publish, but not want to include changes pushed by library after the QA publish.

This address a issues also discussed in this product idea:


Status: Acknowledged

Great ideas @rune_a and @UnknownJ. A pick and choose list of what elements from the library to apply sounds amazing. I have moved this idea to Acknowledged

Alerts, email notification and Slack integration

Status: Being Considered
Submitted by ivanmoya ‎01-15-2018 03:39 AM - edited ‎01-23-2018 03:56 AM

Hi all,

In our company many users have access to Tealium, and we many publications in PROD enviroment, example for advertising campaigns, we would like to know if there is any alarm manager, email notification or integration with Slack.

We have several profiles, and each profile a Tealium Owner profile, it would be nice to be notified to check that there is no failure in PROD

Our idea is get notification when any coworker publish in PROD enviroment, for example with Slack Integration shoulb be very cool.

Attach photoshop example (sorry my montage) :)


Maybe now is possible, i Dont know.

For example we have an integration of JIRA with Slack and it is very productive.

Best Regards

Status: Being Considered

@ivanmoya Thanks for this idea. I think real-time Slack notifications would be very cool!

multi-branch versioning

Status: Being Considered
Submitted by PhillipMarquez on ‎01-11-2018 09:46 AM - last edited on ‎01-12-2018 07:16 AM Submitted by Community Manager

For TiQ:

Allow for multiple users to edit and save their work without impacting the work that others are doing as well as the current live versions for DEV/QA/PROD.

Google Tag Manager has a version of this which is very well done.  In short, a new workspace is created which is open for any editor to modify, but are not added to the main branch/trunk/workspace until published.  If a workspace is published, the other workspaces are prompted to update their workspace to bring them in line with what is live.  The only gripe is that only 3 workspaces are allowed (including main), which is usually enough for a small, but moderately active team, but can be a limting factor when there is a lot going on.  What makes this so good though is that its implementation is simple, intuitive, and easy to understand what is live, what is being worked on and merges without any fuss or complications.  It's so easy, a simple demonstration is enough to get someone on board with the concept and they never look back.

An added benefit is that this addresses the issue of having two people attempting to do edits in a profile at the same time.

Status: Being Considered

@PhillipMarquez Thank you for the idea and all the thoughtful comments afterwards. I have moved this idea to Being Considered

Add multiple OR values in same Extension Condition field

Status: Acknowledged
Submitted by rune_a on ‎02-07-2018 03:19 PM - last edited on ‎02-13-2018 04:36 PM Submitted by Community Manager

I would like a option to include multible values in a condition text string, and then they should be considered OR.

Then i don't need to repeat my condition statement for each value, it should match on.

Example below is from TIQ compared to Webtrends. The two functions do the same.



Status: Acknowledged

Hello @rune_a. Great idea. I have moved this to Acknowledged

Fix utag.DB related errors

Status: Acknowledged
Submitted by pmeyerdk Contributor ‎02-06-2018 03:06 AM - edited ‎02-08-2018 04:28 AM


I really like using utag.db, but very often see errors like the following coming from Tealium iQ code:


Could we get that implemented a bit nicer, to not have errors saying utag.DB isn't there, coming from Tealium produced code.
In the above example, I would be more than happy with a check for utag and DB before using it.

I do know, that I can't myself use utag.DB in for instance pre-loader extensions, but for that purpose I know I can create my own function for outputting information in the console, in a similar maner, or just use console.debug directly.

From time to time I have to explain less technical colleagues, why the above error pops up, and would love to get that improved.

Thanks in advance :-)

Best regards,

Status: Acknowledged

Thank you for updating this idea @pmeyerdk. I have now moved this Acknowledged

Welcome to Product Ideas
We want to hear your ideas for improving the Tealium platform. Get started with Product Ideas: read the submission guidelines, search before posting, then vote and comment on ideas you like.

Top Kudoed Authors