Product Ideas

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

Currently the Visitor Lookup only allows you to delete one visitor at a time which takes several seconds. Our use case is to delete visitors in the thousands. The current feature is not a usable when you have to delete multiple visitors.

Product idea: would be to extend that feature to batch delete multiple visitors in one request potentially via a CSV upload. 

 

 

Status: Acknowledged

It would be nice to be able to see within AudienceStream attributes which audiences they are being utilized in. 

This would help with clean up efforts when attributes are outdated and no longer being used in active audiences. 

It would save time by not having to into each audience and clicking though the attributes that are being used and try to trace back to each attribute one at a time. 

Status: Acknowledged

Add Conditions section in the Javascript Code type extension scoped to PreLoader.

We have a lot of PreLoader extensions which are app/page specific so it would be great to have the condition section for the Javacript code type extensions which are scoped to PreLoaders

Currently the Lookup Table extension doesnt have the PreLoader and DOM Ready scopes and can be only scoped to specific TAGs or All TAGs. We have certain scenarios where we need to use this extension at PreLoader and DOM Ready event.

Security Feature Request : Subresource Integrity(SRI), Content Security Policy (CSP)

Status: Acknowledged
Submitted by baraths84 ‎10-02-2018 08:58 PM - edited ‎10-02-2018 08:58 PM

Hi Tealium Team,

Currently tealium does not support important security feature called - Subresource Integrity (SRI) ,its a security feature that enables browsers to verify that files they fetch (for example, from a CDN) are delivered without unexpected manipulation. It works by allowing you to provide a cryptographic hash that a fetched file must match.

+ Content Security Policy (with SRI)

Though Tealium provides Checksum through its revesion API, which is not equivalent and does not help mitigate realtime.

Due to modern security attacks like #magecart on ecommerce websites. Its important to see this feature suporrted through Tealium Tag Management(IQ)

References :

https://caniuse.com/#search=SubResource%20Integrity

https://www.riskiq.com/blog/labs/magecart-ticketmaster-breach/

https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity

https://www.symantec.com/blogs/threat-intelligence/formjacking-attacks-retailers

Thank you

Barath

 

Status: Acknowledged

@baraths84 Thanks for this idea. 

Hello,

We noticed that the ID's created by the Google cookie matching service tag are device ID's. So one user can have multiple ID's, instead of one. Because of that, we can't use these ID's for cross-device stitching and cross-device retargeting for our Google ads.

To tackle this issue we would like to be able to send multiple Google ID's to Google via Audience Stream. In Audience Stream we're able to capture all known Google ID's and create an array of these ID's. If we could send this array to Google our problem would be solved, and we could create cross-device audiences.

Status: Acknowledged

Product Feedback Request: Data Supply Chain in UDH

Status: In Early Access (Beta)
Submitted by 2 weeks ago - last edited 2 weeks ago

One of the most exciting updates we have been working on is something we call our Data Supply Chain View in the UDH. This dashboard serves as a comprehensive, live action view into your entire data flow. From this view you can take a deeper dive into areas of interest using the various filter options, or get a high level snapshot of how all data is flowing through the system. 

Your data is available to viewed by individual products (EventStream, AudienceStream, DataAccess) or all together.

EventStream:

  • The data resources available are: Data Sources, Events Received, Events Inspected, Enrichments Applied, Active Feeds, Actions triggered, and active Connectors
    • This data flow can be further inspected by: Sources, Feeds, Destinations

AudienceStream:

  • The data resources available are: Data Sources, Events Received, Events Inspected, Visit Count, Active Audiences, Actions Triggered, Active Connectors
    • This data flow can be further inspected by: Sources, Audiences, Destinations (Connectors)

Data Access:

  • The data resources available are: Data Sources, Events Received, Events Inspected, EventStore Feeds, Events Set to the specified destination. Further filtering is available to specify: EventStore, EventDB,, AudienceStore, AudienceDB
    • This data flow can be further inspected by: Sources, Event Feeds, Destinations

 This is just very small summary of the power of the Data Supply Chain view within UDH. We are looking for customers that are interested in piloting the Data Supply Chain and providing feedback. If you are interested in Early Access, please contact your Account Manager.

For general feedback please feel free to leave a comment below.

DataSuppyChain.png

DSC2.png

DCS3.png

Product Feedback Request: Collapsible Trace

Status: In Early Access (Beta)
Submitted by 2 weeks ago - last edited Friday

Another very nice enhancement we have made is regarding our Trace feature. Currently, when performing a Trace the Trace window must stay in focus in order for Trace to continue running. With the recent change Trace can now be left to run in the background as you continue to use the UDH. The Trace arrow in the navigation will turn green when you have an active Trace running and Trace is minimized. 

If you are interested in Early Access to the collapsible Trace feature please contact your Account Manager.

Trace.png

Sort Labels Alphabetically

Status: Under Review
Submitted by Tim-StarTribune on ‎07-25-2018 12:49 PM - last edited on ‎07-26-2018 10:24 AM Submitted by kathleen_jo

Hello! A simple idea I have is to have labels sorted alphabetically. We have probably over 300 extensions and it is a real pain whenever we have to tag a new extension with the correct label. 

Thanks,

Tim

Status: Under Review

@Tim-StarTribune Happy to report that this is now Under Review.

Quite often we need to change tag templates to be able to run them with utag.link() function.

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

  u.ev={'view':1,'link':1};

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

Status: Being Considered

Hello @daniel7. Congratulations, your idea has been moved to Being Considered. Thank you for the idea and keep them coming!

Hi Tealium

Currently when profiles are inherited following library updates, the extention order is not maintained in teh child profiles. 

This means the user has to go through each child profile and re-order those extentions (annoying enough to do once, imagine x20+ - ahh the joy of multi-site) 

Can you fix this so that the extention order is maintained when profile is inherited. 

kr

 

Status: Being Considered

@GavinAttard Thanks for this idea. We expect this to be addressed in the upcoming UI changes to iQ. Stay tuned!

Publish Integration with Git/Github

Status: In Development
Submitted by oaustegard on ‎01-18-2018 12:16 PM - last edited on ‎07-24-2018 01:12 PM Submitted by kathleen_jo

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: In Development

You'll be happy to know that the team is working on this.

Make Conditions a "thing"

Status: Acknowledged
Submitted by UnknownJ Occasional Contributor on ‎07-20-2018 12:58 PM

At a lower level than formal load rules, it should be possible to build conditions, generally simple combinations of a variable and a value, and give them friendly names for re-use.

This would then allow less tech-savvy users to build load rules out of a set of pre-configured re-usable building blocks, as well as enable quick re-use of conditions across multiple extensions etc.

So within my own organisation, I might have a condition "Lloyds Brand", which could be defined as:

b.Brand == "Lloyds" || (b.Brand === undefined && b.url.indexOf("lloyds") >= 0)

Then any extensions that need to be scoped to that brand alone can just re-use that condition, which in the backend would be stored as a reference to the condition rather than as the code itself, meaning a single change to the definition of that condition would be reflected in any load rules or extension conditions that referenced it.

For Load Rules, this could then be a way of getting to a cleaner implementation of and/or conditions. The fact that the default behaviour of multiple load rules is an AND operation means that if I wanted to scope a tag to five out of my twenty brands, I have to have an explicit load rule that articulates those, I can't just have five brand load rules and OR them together. But re-usable conditions that can be evaluated to booleans and then glued together using any number of logic operations would make it easier to build simple load rules, but also possible to build complex load rules using logic gates etc. if you wanted..

This would also make it easier to build a true GUI for load rules, with users dragging in pre-configured components and building decision trees. Extra points if you can build a decision tree that describes multiple load rules - each terminating point in the tree could be described as an individual load rule, so in its most simple case, an "This is a Test Site" condition in a one-step decision tree could output a "Test Site" load rule, and a "Live Site" load rule. Then you could nest further conditions under the Live Site to create further divisions within that, giving you say "Test Site", "Live Site", "Live Site Authenticated" and "Live Site Unauthenticated" as load rules that are all described by a single decision tree.

In principle, it's not unlike the concept of building segments/filters in analytics tools.. extra points if you can use conditions within conditions, so creating compound conditions, but obviously the pain of handling infinite loops may not be to your taste..

Status: Acknowledged

Ah okay got it @UnknownJ! Love the attached decision tree graphic as well. I have moved this to Acknowledged and will vote for it as well. 

currently for connectors i can :

a) use a simple connector Action, and send ALL data to the connector. or,
b) use advanced Action, and be very specific and create my payload structure through a template

I need to combine the above, I need to :

a) send ALL attributes (I dont want to spend days mapping each one individually). AND
b) I need to add custom attributes to the payload.

use case: in Audience Stream, I want to send full payload to my connector. I also want to send the Source ("which Audience caused this payload"), and 'WHEN' ("this payload was triggered by a joined_audience action").

the above two could be added in a smart way, but if we can add custom attribute mappings to the connector action (when sending ALL data), then we could also just hardcode these two values as attributes into my payload.

(the same should also then be added to eventstream, so we can pass the filtered-stream-name as an attribute, when sending All attributes in a payload to connector)

Status: Acknowledged

New enrichment to get the specific value in a Tally by dynamic key

Status: Acknowledged
Submitted by william1 ‎06-29-2018 06:29 AM - edited ‎07-02-2018 01:35 AM

New data enrichment for the number attribute which will set the number to the specific (dynamic key) value in the Tally. 

For example:

Tally: Clothes

Tally KeyTally Value
"Shoes"7
"Shirts"3
"Pants"10

 

"Tally Clothes (favourite)" = "Pants"

Set number "x" to the tally value with a dynamic key of  "Tally Clothes (favourite)".

x = 10

This will be useful for lead scoring and many other use cases. 

Status: Acknowledged

Hello @william1. Love it. Thank you for the idea. I have moved this to Acknowledged

Make variable ID's searchable in AudienceStream

Status: Acknowledged
Submitted by martin_vinter on ‎09-28-2018 01:33 AM

When using datalayer enrichment to run onsite targeting, from time to time, it generates questions from web-editors such as "what is badge 5245?" or "could you please change property 5487?" because that is how AS-outputs look to a web-editor that work with them through an onsite targeting tool such as Optimizely.

Badge and string ID's are impossible to find in the interface for AS, unless if you look for them manually. Searching for ID's returns no matches, and the same applies to browser searches. Potentially, you have to look through every single badge by hand to find the one in question. It can take quite some time.

My suggestion: Change the searchfunction so that a search for an ID from the UDO-inspector matches the AS-variable that has that ID.

 

Status: Acknowledged

@martin_vinter Thanks for this. It should be easier to find an attribute by ID. Sounds like there's a decent work-around for now from @calebjaquith's suggestion. Still, if this gets enough votes we will take a closer look.

Duplicate extension between profiles

Status: Accepted
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: Accepted

Hello @rune_a. OMG you are on a roll this week. Another card being worked on. Congratulations! We've moved this to Accepted. Keep the ideas coming!

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.

mapping-modal.png

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)

mapping-tab.png

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

Connector Errors CSV Output

Status: Acknowledged
Submitted by Bazhway on ‎07-02-2018 01:50 AM

Under each connector, you can view the last 10 errors.

It would be great if you could get this as a CSV output like you can for EventStore and AudienceStore in the Data Access section with time periods.

It's important for us to track this in case key suppression data isn't being sent to Vendors in time due to a failed call.

Status: Acknowledged

Hello @Bazhway. Thank you for the idea. I have moved it to Acknowledged. I can see a report of some kind here. HHHHhhmm......

Use event spec as condition in defining event feed

Status: Acknowledged
Submitted by cmarkle on ‎09-25-2018 11:59 AM

It would be nice to use an event specification in defining an event feed.

 

Example:

IS VALID {{custom event spec}}

AND {{insert field}} STARTS WITH {{insert string}}

...

Status: Acknowledged

@cmarkle Agreed, this would really help. Thanks for the idea.

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