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

Make Conditions a "thing"

Status: New
Submitted by UnknownJ Occasional Contributor Friday

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..

It would be great if the Load Rules UID is also displayed in the TAG tab section just how the TAG's UID is displayed in the Load Rules tab section. Also if you can add a link to go to the load rules directly from the TAG tab just like how it has been enabled in the Load Rules section.

Status: Being Considered

Hello @jay_ashar. It looks like we might be able to roll this in with other changes to Load Rules happening now. I am moving this to Being Considered for now. Thank you for the idea!

Trace time change

Status: Acknowledged
Submitted by IrisV Tuesday - last edited Wednesday Submitted by Community Manager

In my Tealium setup I have some rules that will only trigger after a session end (so 30 minutes after visit end) or after for example 15 days. These are difficult to check using trace as you have to wait this amount of time in real-time. 

Could an option be added to fast forward trace time with x hours/days, to make these checks easier?

Status: Acknowledged

Hello @IrisV. Great idea! I think @jaredhislop might be interested in something like this as well.

@jaredhislop that was your cue to vote for this idea. #hinthint #winkwink LOL

I have moved this to Acknowledged. Again, please do feel free to try and gain support for your idea by asking your colleagues to vote and comment, @IrisV

I need to be able to test campaigns/initiatives. When the visitor is qualified for more than one thing in the same medium/placement, I would want to test them up against each other to figure out which one performs the best. In my setup, the campaigns can occur in any combination.

The only ways I could figure out to get AudienceStream to select one at random were clunky at best. It gets complicated because any one visitor can be qualified for 0-10-ish campaigns in any combination. I could build a random selection logic around a fixed number of campaigns that are always the same. Making it dynamic makes it a lot more complicated.

If I could just add all the campaigns to a set of strings or a tally, and then enrich a string with a random value of that set of strings, then that would do the trick. Alternatively, if I could select a specific item of a tally/set of strings, then I could do so with a random number as the selector. That would be the second best sollution.

If you happen to know of a way to achieve this through the existing features then please drop a comment.

Status: Acknowledged

Thank you @martin_vinter and @mark_reddin for the explanations. Very informative. Sounds like this would make a great product idea indeed. I have moved this to Acknowledged

Please do get your colleagues to vote on this idea, Martin, if you feel strongly about it. The more votes and comments the more chances it has to be added to our development cycle! 

Cheers!

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

Status: Acknowledged
Submitted by william1 3 weeks ago - last edited 3 weeks ago

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

Connector Errors CSV Output

Status: Acknowledged
Submitted by Bazhway 3 weeks ago

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......

Stitching with changing visitor IDs

Status: Acknowledged
Submitted by TimWaijers on ‎06-14-2018 12:22 AM

The current implementation of visitor stitching relies on setting a unique identifier on an attribute for a visitor that never changes. So this is a 1 to 1 relation of a visitor with a unique identifier.

Sometimes a visitor has multiple different values for the same identifier. This would be a 1 to n relation of a visitor with a specific type of identifiers (phone numbers, email addresses, order ids, basket ids, session ids).

Use cases
1. Multiple baskets filled without being a customer yet and the sale is completed through a channel that can't know another unique identifier for that basket, other than the basket ID (such as an abandoned email, sms, social, etc.)
2. Multiple email addresses for the same person.
3. Deduplication of customer IDs within a CRM.

Status: Acknowledged

I love this idea @TimWaijers! 1 to n stitching would be a great addition to AudienceStream. And it looks like you have quite a few fans of this idea already! Congratulations. I have moved this idea to Acknowledged

Unlocking the potential of the timeline attribute

Status: Acknowledged
Submitted by TimWaijers on ‎06-14-2018 12:31 AM

The promise of the timeline attribute is a very powerful. Store a set of attributes on a specific moment. For example; store all the baskets, orders, purchased etc for a visitor. However when applying rules to timelines you find out that there's actually only one thing you can do; check if it assigned or not. Then when you do want to use it in a connector (eg. a webhook with trimou templates) you find out that all the attributes you've stored in an entry are only retrievable through their IDs, instead of their names.

To unlock the timeline attribute fully I think the following would be benificial:
Rules:
- Check if timeline has entry between dates or on specific timeline.
- Get (first,latest,all) timeline entries that have an attribute that matches a rule from the types that are applicable to that attribute type.
- Remove timeline entries that have an attribute that matches a rule from the types that are applicable to that attribute type.
- Check if timeline has entry that have an attribute that matches a rule from the types that are applicable to that attribute type.

Connectors:
- Use the names of an entry's attribute not the IDs
- Be able to interleave the data from an entry's attributes into hierarchical JSON data, like you can with regular attributes.
(eg. purchases.entry.id)

Status: Acknowledged

 Great idea @TimWaijers. I can already imagine the use cases for this feature request. I have moved this to Acknowledged

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

Consent Management - language handling should be based on locales, not on browser language

Status: Acknowledged
Submitted by Kronk ‎05-23-2018 05:41 AM - edited ‎05-23-2018 06:18 AM

Only using the browser language to determine which language version the prompt should show is not sufficient for clients that use one language in more than one country. For example we use German in Germany (locale de_DE) and Austria (locale de_AT) but visitors of both countries would see the same prompt with the same privacy policy URL (custom parameter) but they'd have to be different/country-specific. Otherwise we are going to send Austrians to the German privacy policy page and vice versa.

Status: Acknowledged

Hello @Kronk. Thank you for the GDPR enhancement idea. I have moved this to Acknowledged.

Git/Github integration

Status: Under Review
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: Under Review

Hello @oaustegard. Thank you for this idea. I wanted you to know that this idea is now Under Review. We will let you know what the next steps are. Congratulations!

More rules for attribute: Array of Numbers

Status: Acknowledged
Submitted by TimWaijers on ‎06-14-2018 12:40 AM

On an array of numbers the following rules are allowed: is assigned and is not assigned. I would like to see the addition of the following rules: contains number less than, contains number less than or equal to, contains number greater than, contains number greater than or equal to, contains number equal to.

Use case:
For a set of ages check if there is an age between 0 and 18 (child), for this use case we currently have to create a rule with 19 separate OR statements. (let alone the different types adults 18-30, 41-50 etc.)

Status: Acknowledged

This would be an amazing time saver @TimWaijers! I like it! Good stuff. Keep the ideas coming! I have moved this idea to Acknowledged

Create account/profile level attributes with preset values

Status: Acknowledged
Submitted by TimWaijers ‎06-14-2018 12:26 AM - edited ‎06-14-2018 12:42 AM

When using specific calculations or similar rules there might be generic values that change every season. Whenever that change happens you manually need to find all the entries for that value and update it. This is error prone and tedious. If it was possible to create profile or account level attributes, you'd then be able to reference those thoughout the implementation and change them from a single point.

Status: Acknowledged

I like it @TimWaijers! We've also been asked about creating a central data layer to be used across libraries and profiles.

Yours sounds more like this but for AudienceStream and EventStream. This would be a huge time saver, I have moved this to Acknowledged

Idea Description : A checkbox at the top of the page in TAGs, LoadRules, Extensions to automatically select/deselect all checkboxes 

Reason: In our WFC profile we have 1000s of extensions that we have to toggle on/off for testing purposes. so it would be nice to have this checkbox at the top of the table to select/deselect all the extensions.

Status: Acknowledged

Sorry for this taking so long @jay_ashar. Let me move this Acknowledged.

Idea Description : It would be nice to have an option in the LoadRules and Extensions section to allow users to add loadrules or extensions with OR conditions within AND condition which would generate code such as below:

if(app_id === 'test' && (product_code==='AA' || product_code==='BB' ))

Currently this is not an option and we end up configuring conditions like below:

if((app_id === 'test' && product_code==='AA') || (app_id === 'test' && product_code==='BB' ))

Status: Acknowledged

Got it @jay_ashar. Moving this to Acknowledged. 

Currently there are a handful of Device Variables which allow for creating rules and mappings: https://community.tealiumiq.com/t5/JavaScript-utag-js/Built-In-Data-Layer-Variables-from-utag-js/ta-...

I would like to propose a more comprehensive list of variables treated as device variables and available for use in rules and mappings

Server Variables

  • server time zone
  • server current time GMT
  • server current time UTC

 

Domain Variables

  • domain host
  • domain hostname
  • domain protocol
  • domain port
  • domain pathname
  • domain query string
  • domain origin

 

Document Variables

  • document title
  • document language
  • document country
  • document referrer
  • document url
  • document domain
  • document URI
  • document mode
  • document element
  • document doctype
  • document head
  • document body
  • document forms
  • document anchors
  • document applets
  • document activeElement

 

Browser Variables

  • browser product
  • browser platform
  • browser app code name
  • browser app name
  • browser app version
  • browser cookie enabled flag
  • browser javascript enabled flag
  • browser user agent
  • browser time zone
  • browser current time GMT
  • browser current time UTC
  • browser current time local
  • browser width
  • browser height
  • browser language
  • browser online
  • browser name
  • browser version
  • geolocation.latitude
  • geolocation.longitude

 

 

 

Status: Acknowledged

Hello @DustinKirk. My apologies for not getting to this idea sooner! I have moved this idea to Acknowledged. I love the idea. 

Cannot tell the difference between the different variable types (query string, dom, path, etc) in AS

Status: Acknowledged
Submitted by landin_gee on ‎06-12-2018 04:28 PM - last edited on ‎06-13-2018 10:33 AM Submitted by Community Manager

There are quite a few variables I use that have the same name for querystring, path, dom, etc. When trying to create loadrules in AS, the dropdown or icon does not indicate what type of variable it is unless I have the rule and physically click on the variable to go to the variable properties. This is time consuming and can cause rules to not function properly.

Status: Acknowledged

 Hi @landin_gee. Great point. 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.

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

Problem:

- User 1 logs in to AS, starts making changes on V1

- User 2 logs in 10 minutes later, starts making changes on V1

- User 1 publishes its changes with all its hard work, V2

- User 2 publishes changes, but these are changes on V1, so when user 2 publishes V3, it will overwrite everything from V2 from user 1

A simple merging system would be nice, and that only starts complaining when 2 versions have conflicting changes.

Currently we workaround this by having a chatgroup in which somebody says they are going in and out of AS, so you know when you can and can't use it, bit medieval...

Status: Acknowledged

Hello @Sander. Love it. We have a merge feature in iQ Tag Management but nothing for AudienceStream. I have moved this idea to 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