Tealium Learning Center

Hi @Jaikrish  This is both an iQ question and an AS question. iQ - the lookup extension is designed for cases where the input to lookup on is a single item.  It is not designed to loop through an array of items and lookup for each of them.  So you'd need to write that JS yourself. Here's a starter - you'll need to add some checking to that to make sure the input is indeed an Array   //looks up for each item in the source array //and outputs into the destination data variable specified //configure here var source = b.product_id; var nameOfDestinationVariable = 'product_category'; var lookup = [ {'1': 'men'}, {'2': 'men'}, {'3': 'women'}, {'4': 'women'} ]; //don't change anything below here var destination = []; if (typeof source == 'undefined') return; for (var h = 0; h < source.length; h++) { var matched = false; for (var i = 0; i < lookup.length; i++) { for (var f in lookup[i]) { if (source[h] == f) { destination.push(lookup[i][f]); matched = true; } } if (matched) break; } if (!matched) destination.push(''); } b[nameOfDestinationVariable] = destination; If you scope a JS extension like that to the collect tag, you will get what you need.   I also notice this other TLC post, which seems very similar - https://community.tealiumiq.com/t5/Tealium-iQ-Tag-Management/Getting-multiple-value-in-product-category-to-segregate-the/m-p/29875#M9016 In AS, you need to do a couple of things; 1. Add an event variable (array of strings) to hold the product_category if not already there. 2. Add an event variable (array of numbers) to hold the product_quantity if not already there  3. Add a Tally (visit or visit scoped, it doesn't matter) to hold the current order temporarily.  Set this using the enrichment "Set Tally by corresponding arrays".  In there, select the product_category as the first input to the enrichment and product_quantity to the second. 4. Add a second Tally, visitor scoped.  Add an enrichment to "Increment Tally by Tally" based on the temporary tally in 3 above.  However, use a rule here to only do this when it is an order confirmation event. ... View more

Hi Jay My understanding of what you are asking for here is; In your Data Layer on your order confirmation page, you have something like this ... "product_id":["id1","id2","id3"], "product_quantity":["1","2","1"], ... You wish to translate the product ids to product categories using an iQ extension, and in AudienceStream you wish to have a visitor lifetime tally of the number of times the visitor has purchased each product category. Is my understanding correct? ... View more

@pafe For Visitor and Visit level Strings, they are either "Assigned" (meaning the String is present and has a value) or "Not Assigned" (meaning they don't exist in the Visitor Profile).  Empty Strings are not persisted in the Visitor Profile. For Event Level Strings in Server UDH, it's slightly different.  You already know about Strings from iQ (where you have the "empty" rules as well as the "assigned" ones).  But for Event level strings declared inside the Server UDH, they are "Assigned" if you pass in a value to that String, even "".  Otherwise they are "Not Assigned". Mark   ... View more

Hi @pafe  We have a function in AudienceStream just for that, it is called cooldown.  You don't need to build this with attribute and audience logic. https://community.tealiumiq.com/t5/Universal-Data-Hub/Action-Frequency-Capping-amp-Prioritization/ta-p/596 You can either put a group of connector actions in a cooldown group so that all are suppressed until the cooldown is over, or you can just have a single connector action in a cooldown group.  If you have more than one connector action in a cooldown group, you can also have a priority order to them, so that if two or more of them would trigger at the same time, you can prevent that if you wish. You can have more than one cooldown group as well (so you could have one group for a cooldown of day 30 days and another for a cooldown of say 2 days) A point to note (and it matches your requirements here, but just to be clear) is that once a visitor is in cooldown for a particular group, any connector actions that trigger in that group are suppressed and will not trigger at all, even once the time is over.  The time for that cooldown group needs to pass before connector actions in that group can trigger again. ... View more

Hi @test21509  In the case I talked about, where you are using an AudienceStore connector at the end of the visit, it should be very close, but may not be identical. You could instead change the built in Visitor Date Attribute "Last visit" to be enabled for AudienceDB, if it is not already. ... View more

Hi @test21509  There isn't such a field in the JSON by default. Bear in mind that the JSON file timestamp in S3, as well as the filename, do tell you when the AudienceStore file was written.  This will not be the same as when each record in the file was written, because AudienceStore fills an internal buffer before writing the buffer to a file.  Or else if 1 hour has passed since the last file was written, the buffer is flushed to file anyway.  So depending on the amount of traffic to your AudienceStore connector, the file timestamp will be at most 1 hour older than all the records it contains.  This may be close enough for what you are looking for here. If not, then you'll need to check if there is already a suitable date attribute being included in the connector from the Visitor Profile.  For example, if your AudienceStore connector was set up to send All Attribute at the end of a visit, then the built in date attribute "Last visit" would be suitable for you here, because that is set at the end of each visit, and this is the same time as the connector fires. If the above does not apply, for example if you are not using an "All Attributes" connector action, you may still already be including in the connector a suitable date that is the same date/time as the connector fires.  If not, you will likely need to set one up in AudienceStream and/or include it in the connector. ... View more

Hi @pafe  Yes.  In the screenshots below, I have an omnichannel definition that has a date and a number column in it. I can then use the date and the number when I am storing an event in the timeline. Although you can in principle add many different types of attributes when storing an entry in a timeline, there is only a use for Numbers and Tallies.  This is because these are the only attributes that you are able to aggregate from the timeline afterwards.  See https://community.tealiumiq.com/t5/Universal-Data-Hub/AudienceStream-Visit-and-Visitor-Attributes-and-Enrichments/ta-p/23244 ... View more

Hi @artywah  Ah, that's why I asked if you could offload the logic into iQ. For pure UDH, you do have some options. Assuming that you don't want to change your logic at all, and without the enhancements discussed above, there are some ways, for example; You'll see that with this approach, it is bounded.  You need to create the $100 bins manually, and the approach will eventually stop working because you can only create a finite number of them.  I created 3 in the example above. The above approach is designed to trigger immediately on a threshold.  If you want to wait for the end of the visit to do so instead, then make the final boolean visit scoped, and remove the set false enrichment from it. I will go now and create an internal product idea for you for the necessary enrichments, but you should also create your own public facing one. ... View more

Hi @artywah  UDH does not currently have the mathematical operators of Floor/Celing, Integer Division and Modulus/Remainder, which would be needed here to do this in pure UDH.  I encourage you to please submit a product idea to add those enrichments on the Number Attribute. So since we can use iQ here, I'd suggest the following approach; 1. Make sure Data Layer Enrichment (DLE) is swtiched on for the collect tag, at least on the order confirmation page and the first page of a users session as well as when they log in.  You can selectively control this if you don't want to have it run on every page, but be sure that the visitors lifetime order value is coming back via DLE at the correct point. 2. Add a JS extension scoped to the collect tag, conditional on the order confirmation page, with this kind of code; //get the current order lifetime value and work out how many integer multiples of 100 it is var previous = b && b['va.metrics.5019'] ? b['va.metrics.5019'] : 0; var previous100 = Math.floor(previous/100); //add on the current order value and again work out integer multiples of 100 it is var now = previous + (b.order_total || 0); var now100 = Math.floor(now/100); //work out how many integer multiple boundaries we have crossed b.as_100_crossed = (now100 - previous100).toString(); You will need to replace 5019 with the ID of your visitor lifeitme order total number in AS.  You may also need to replace order_total with whatever the variable name is in your data layer for the current order value. Now in UDH, you can add an event level number called "as_100_crossed" and this gives you for the current order, how many times the visitor has crossed the $100 threshold on this order value. Make sure that either in your iQ publish settings that code minification is turned on, or else remove the comments yourself from the above code. ... View more

Hi @artywah  Can I ask a couple of questions to help you? 1. What do you want to happen if the user places an order for say $250? 2. What do you want to happen if the user places several orders in the same visit? 3. For your setup, would you be able to offload some of the logic to Tealium iQ (client-side)? 4. Is there a timeframe on the offer?  If the user spent $95 six months ago and is now spending $10, do you still want to trigger the offer? ... View more

@patrickdaniesso There is a caveat at the bottom of this answer for AudienceStream that I'd like you to read if you are presently, or may be in the future, using AudienceStream from these collect tags.  Presently, mappings for the collect tag are not supported In addition, although you can alter the data that is sent via the collect tag by using JS extensions scoped to it and manipulating the 'b' object, the configuration for the collect tag does not look at the 'b' object to determine the server to send to. There are ways to do this via JS extensions scoped to the collect tag, but it depends on which version of the collect tag you are using.  So I would reach out to support@tealium.com if you must use this approach. There is another approach, which is to use more than one copy of the collect tag, and use a load rule to determine which one should fire. AudienceStream If you are planning to send these collect tags to AudienceStream, then you will run into an issue.  The issue is that AudienceStream is designed around the assumption that an anonymous visitor identfier is not shared across more than one AudienceStream profile.  That would not be the case here.  The same anonymous visitor identifier might be sent to a different AudienceStream endpoint depending on your conditions. You can put in place an extension scoped to all collect tags in the iQ profile to avoid this issue, but be sure to put this extension in place before you put these collect tags live.  This is true no matter which approach (load rules or another method above) you use. The extension works by altering the outgoing value of the anonymous identifer to make it different for each endpoint. Again, the specifics of the extension depend on your specific setup, so reach out to support@tealium.com for help with it. ... View more

@AndrewFenn You are correct.  The above requirement and pattern were for the case where the visitor is returning to the site or there is some other event (omnichannel or collect API) that "wakes up" the visitor profile and recalculates everything. Depending on what you are doing, there are two things to consider; 1. A filter in Audience Sizing based on the Date you've stored in Visitor Profiles versus the date now will work correctly.  So you could use Sizing to find visitors whose Date is more than X days ago. 2. Delayed connectors may also suit what you are doing. ... View more

Hi @kamgir When you say "connection is successful", do you mean that you followed the article below, including tracing the connection, and you can see the connector being fired successfully? https://community.tealiumiq.com/t5/Universal-Data-Hub/Marketo-Connector-Setup-Guide/ta-p/21359 If yes, or if you are not sure, I suggest reaching out to support@tealium.com so that they can have a look at your setup. Mark ... View more

Hi @william1 A Tally is pretty much that. Mark ... View more

Hi @amitjain0304 1. Make sure you are signed into tealium correctly.  Sign into Tealium iQ or Tealium Learning Community first. 2. Check that the account and profile name in the UDH url are correct 3. If the above doesn't work, you should indeed contact your account manager and/or support@tealium.com ... View more

@yehohanan What is the current logic for triggering the webhook?  Is it simply every visitor at the end of every visit?  Would it make sense in your case to only send the webhook if at least one of the data variables you are sending has changed in the current visit? ... View more

Hi @tsmith93036 There are a few ingredients to what you require, but it can all be done in a relatively straightforward way. The first ingredient is to understand how "Data Layer Enrichment" (DLE) means that the AudienceStream Visitor Profile is brought back into the data layer. Read all of that article because there are a couple of subtleties there. The second ingredient is to think about what you mean by "only display for specific users". This sounds like an Audience, although with DLE, you could use any Visitor Attribute, such as a badge, as the condition to trigger the Modal Offer. If the logic to determine who these "specific users" are is Audience based, then you could build this logic in AudienceStream. Alternatively, it may be that you have a list of users externally that you wish to target. In this case, Omnichannel or the Collect API would be the usual ways to get this list into AudienceStream. The next ingredient is the modal offer extension itself, with a condition based on a. The user being logged in (presumably you can determine this in the data layer) b. The user being one of the specific users (with DLE, you can also determine this from the data layer) c. That the user has not already clicked on the modal (see below) You said that you didn't want to show the modal again once it has been clicked on. The simplest way to do this will be to add a click handler to the HTML inside the modal to call a JS method where you can set a cookie for the visitor lifetime to "remember" that they have already seen the modal and not to show it again For example, inside your modal's HTML, the link / creative might be inside this;   <a target="_blank" href="http://theurl.com" onClick="utag.myModalClicked()"><img src="http://myimage.com" /></a>     You can declare the code to react to this in a JS DOM Ready Extension, as follows; utag.myModalClicked = function(){ utag.loader.SC("utag_main", {"myModalClicked": "true"}); utag.extn.mdlW.dismiss(); }; And then your condition above that controls if the modal is shown or not can have a condition that says that utag_main_myModalClicked is not defined. ... View more

@IrisV This feature does not exist directly, but it is possible to configure UDH dashboards to show trends in some of the attribute types over time.  Other than that, your suggestion would make a good product idea as the previous responder said. ... View more

Hi @IrisV The bash trace file is designed to be run from a command line in order to reply the events that were captured in the trace, so that you can test changes to UDH configuration without having to redo all the input actions. So it cannot be uploaded into the UDH UI, but it can be run from the command line. When you say "cooldown", do you mean cooldown or delayed actions? If cooldown, then yes, the bash script could be used to see if an action where the user was in cooldown now triggers when the user is no longer in cooldown. For delays, no.  You cannot see delayed actions happening this way. ... View more

Hey @jaredhislop ! A clarification on your question Do weeks have to run from say Sun-Sat, i.e. are they calendar weeks you are after here, or are they just 7 day weeks working backwards from the current date? Because I think I can give you a recipe for the latter using pure UDH, but the former is more complex and will require some Tealium iQ help. I will also wait until Monday to give some of our Tealium Experts a chance to give their answers, but the clarification will help them too. ... View more