Tealium Learning Center

Hi @loldenburg Assuming all of this is coming from a single device, with no cookie clearing or anything, in your case, after session 3, here will be the state of the visitor profile; Email (Visitor ID) = oldemail@x.com Login ID (Visitor ID) = 123456789 Gender (Visitor Attribute) = male This is what happens step by step; 1. Before even event 1, there is an anonymous visitor profile with no Visitor ID key set, let's call it A, and then Email, Login and Gender are enriched to A on your event 1. Since two stiching keys are enriched on the same event, two visitor stitches happen immediately one after the other, and you'd see that in trace. The order in which they happen is not important in this case, and in any case I don't know if it's a deterministic order or not. But let's say first anonymous profile A gets replaced by oldemail@x.com and then in turn oldemail@x.com gets replaced by 123456789. At this stage, the profile is 123456789. It still has the anonymous visitor ID of A, but also has visitor IDs of oldemail@x.com and 123456789 set as separate Visitor ID attributes, as well as Gender set to male. Also, the original visitor profiles are still in the system, but point to and are replaced by the "master" profile, so A -> oldemail@x.com -> 123456789. 2. On your event 2, nothing changes. Even though the email address has changed, as documented in the link below, once a Visitor ID attribute has been set for an existing Visitor Profile, it never changes value. https://community.tealiumiq.com/t5/Universal-Data-Hub/Understanding-Visitor-Stitching/ta-p/91 3. On your event 3, nothing changes either. The new email address is still in the data layer. It hasn't been set in AS, but as long as the user's anonymous visitor ID cookie is still A, AS will still see this as a single master profile and so there is no change in profile. You mention omnichannel - you can join the omnichannel data on either email or login, but if email, you will need to use the old email address. You can include both the old and new email in the omnichannel feed to be sure. You also mention a link in your Original Post. This link is describing behaviour that is different than what I outline above, and the reason is because in that case, there were two separate devices in play, with two different anonymous visitor IDs. I have updated that article to make this clearer. ... View more

Hi @loldenburg On question 3, I meant can the login and visitor ID arrive into UDH on the same event? ... View more

Hi @loldenburg, Could you give more information about the type of migration you are doing?  How is the data getting in to the UDH and where is it coming from? The answer here is - it depends. It depends on a couple of things; 1. Are these regular web sessions from a single browser running TiQ with a collect tag, or is the user clearing cookies or using Incognito or anything like that, or are these "sessions" actually coming from the Collect API or elsewhere? 2. Do the sessions actually end / time out before the next session happens? 3. Are the two visitor IDs being set on different events, or on the same event? Thanks Mark ... View more

Hi @zhaque The issue here is that trying to do AES on the client exposes the secret key in the JavaScript for any reasonably proficient developer (or hacker) to see. As @steve_lake suggestions, the Crypto extension may be a better choice here.  Although that is also done client-side, the difference is that it is one-way encryption.  Depending on what you are trying to do, the idea might work like this; You have a set of email addresses that you Hash offline and put in a database server side (both the email address and the hash) You then hash the datalayer email address client-side and in your server side code, you look up the match for that hash.  That way, the tag never sees the actual email address. This is how several service providers such as Facebook work - you pass a list of email addresses to them in private, and in public, you only ever pass the hash of the email address to them. If you wish to use that approach, the choice of hashing algorithm is important - SHA256 is a standard one.  You should also read up about "Salting" for possible extra security. If, on the other hand, you cannot operate like this, because for example you do not have a master list of email addresses, then you do indeed need two-way encryption.  This cannot be accomplished purely client-side, because the secret key is exposed.  So, you'd either have to arrange for the email address to be present in the datalayer already encrypted, or you'd have to use a server-side service to accept the unencrypted email and return the encrypted value, while keeping the key secret. ... View more

@jmillan If you haven't already, I'd suggest here emailing support@tealium.com, specifying which account and profile is showing this, so that they can check it out for you in detail. ... View more

Hi @greg_hollingswo. The Tealium Collect tag is like any other tag in that its data can be manipulated indepently of other tags.   The way I have done what you are asking for is to have a JavaScript extension scoped to the collect tag, and do this   delete b['PII_data_1']; delete b['PII_data_2']; ...   Since the extension is scoped to the Collect tag, b is a reference to the copy of the data layer that's just for that tag.   Mark ... View more

Hi @amarkic you can use Facebook custom events with the Facebook pixel tag, see "Custom Events" on this page;   https://community.tealiumiq.com/t5/Tags/Facebook-Pixel-Setup-Guide-for-iQ-Tag-Management/ta-p/10413 ... View more

Hi @iwan_uswak There isn't today a way to do what you are asking.  I will log a feature request.   If the number of possible keys you are looking for is bounded, you could do something like this today;   And the same for B, and then the answer;           ... View more

@Michael_Kim_shc   I know it's been a little while since you asked, so sorry for the delay in responding   I believe the requirement is    Assign badge when it first happens. Remove 5 days later If happens during the 5 days, ignore If happens after the 5 days, start again (assign again)   Using the following pattern will do this.  We have tested this.   ... View more

Hi @Michael_Kim_shc, If you give a user ("A") just rights in one profile, that user cannot create a user ("B") with any more rights than they themselves have. Here's creating the user ("A") And here's what happens when the user A tries to create a user B with permissions on all profiles; The permissions are grayed out.  If the user A tried to create a user with permissions on the "blank" profile, to which A does have permissions, then they would be able to do it. The JavaScript permission relates to the ability to create / edit JavaScript code extensions.  It should really be a profile level permission, but presently it is an Account level permission.  However, as explained above, that's not directly related to your question. Mark ... View more

Hi @kuzmin_sergey As @steve_lakementioned, the server side part of this you could do using our vdata pixel This is described here https://community.tealiumiq.com/t5/AudienceStream/How-to-import-data-into-AudienceStream-using-the-Visitor-Data/ta-p/14438   There are examples there of how to formulate the pixel using several technologies, using either POST or GET. There isn't a Node.js example, but the principle is the same - you are constructing a http pixel request with the data being represented as query parameters or POST data.   There are a couple of things specific to your server side implementation. I am assuming below you are using the GET approach, see the above article for the differences if you want to use POST.   1. You can pass tealium_trace_id as a query parameter. For your case, you should always do this if the cookie trace_id is present on the incoming request. You should use the value of the cookie as the value of the query parameter, if that trace_id cookie is present. This will allow you to use the trace utility within Tealium tools and see the server side event in the trace.   2. The tealium_vid query parameter should contain the AudienceStream visitor id. a. If the AudienceStream visitor id already exists, then you can extract it from the utag_main cookie - it is 0156551b8b19000c5defc4035f2e05078004007000bd0 in this example; utag_main=v_id:0156551b8b19000c5defc4035f2e05078004007000bd0$_sn:1$_ss:1$_st:1470330160892$ses_id:1470328360892%3Bexp-session$_pn:1%3Bexp-session   b. If this is the visitor's first page impression, or they have cleared their cookies, the visitor id will not exist yet. In that case, if you still want to also fire your server side pixel to AudienceStream, you need to make sure your visitor id is the same one that the AudienceStream tag will use on the page, but you need to generate it on the server. What I'd suggest here to generate it is generating a md5 hash of a concatenation of the current timestamp, the IP address and the user-agent, as well as a random number.   To get the AudienceStream (collect) tag to use this same value, you can set a cookie from your server, calling it say "server_vid", to this value. If you then add a pre-loader JavaScript extension in Tealium iQ, the collect tag will use this value. The code for this extension is below.   Give this a try and come back to me with any questions. Mark   (function() { window.utag_data = window.utag_data || {}; var getCookie = function(cname) { var name = cname + "="; var ca = document.cookie.split(';'); for (var i = 0; i < ca.length; i++) { var c = ca[i]; while (c.charAt(0) == ' ') { c = c.substring(1); } if (c.indexOf(name) === 0) { return c.substring(name.length, c.length); } } return ""; }; var server_vid = getCookie('server_vid'); if (server_vid) { window.utag_data["cp.utag_main_v_id"] = server_vid; } })();   ... View more

Hi @CP   Let's look at a worked example.   Imagine in our body we had this   <input type='button' id='b1' value='b1'/> <input type='button' id='b2' value='b2'/>   And we set up two onHandler extensions, one for each button, like this;     What this handler does is say "When the DOM loads, attach an event handler to anything on the page with a jQuery selector of "#b1".  This means anything with an id of "b1".  When this HTML element on the page is clicked (because we chose click in the "Trigger On" drop down), call Tealium's link event (because we chose "link" in the Tracking Event drop down), and pass the following data layer to that link event;  { source : b1, data : d1 }   It's important to realise that the link event will not be called until the matching HTML element is clicked, not just because the DOM is ready.   I will come back to the condition at the end of this post, as it will confuse matters now.   The other handler is the same, except that it has a selector of #b2 and passes b2 and d2 instead in the link event call.   Now imagine I set up two tags.  Again, I will only show the first one, as the second one is analagous;     The load rule for this tag says that it will only load if "source" is "b1".  This might be from either the data layer on the page when the page initially loads, or it might be from the link event like we just added in the DOM ready extension.  However, just because it may have been present in the data layer on the page doesn't mean it will be present again in the link event unless we took steps to add it there, as I explain further below.  This is good, as it means the two are isolated.   The data mapping for this tag says to pass some data.  Again, this might be from either the page data layer or from the link event.   If we add a second analagous tag, then overall what we see on the page is that when button b1 is clicked, the tag for b1 is loaded, if it's not already loaded, and it's fired.  The same for button b2 and tag b2.  If the button is clicked again, the tag is already loaded, but it's fired again.       There are a couple of notes;   1. The above assumes later utag versions.  See the link I previously posted.  Nowadays, tags will be loaded if needed by the onHandler event (e.g. the link call).  Also, nowadays, during the link call, the tag will only have access to the data that you pass in the link call, and not to the main data layer on the page.  However, if you need the latter as well, you can add extensions to the tag to get that.   2. Your other question was about   u.ev = {"view" : 1};   Not all tags out of the box respond to both link and view events.  If your tag's code template has a link like the above, it means that it will ignore a link event and only respond to a view event.  Our example above would not have worked for this kind of tag, since we were using a link event in the DOM ready extension.  u.ev is an array of events that the tag supports.  It will look like this for a tag that supports both view and link;   u.ev = {"view" : 1, "link" : 1};   If we wanted to make this work for a tag that only supported a view event, we might choose to change the DOM ready extension to call a view event instead, or we might choose to edit the tag template and add support for the link event.  The former would be easier, but bear in mind that you might end up firing other tags that you didn't mean to.   3. The condition   Just to show that it's possible, I added a condition above.  This example condition means "only run this DOM ready event that attaches the event handler, if the q1 URL query parameter is present with a value of 1".  In other words, you can suppress the DOM ready extension itself if it doesn't match some condition, similar to load rules on a tag.  This allows you more control still, but you don't have to use a condition.   ... View more

Hi there @CP, "Given that each jQuery extension implemented is not tagged specifically to a tag+load road combination (all are scoped to DOM-Ready), any of thes submit buttons in P1, P2, P3, P4, ...... will fire ALL the jQuery onHandler."   Not quite.   When the onHandler event fires, Tealium will only fire the tags whose load rules match the data being passed in the onHandler event.   So it's kind of the other way round.   So, you can control which tags are fired by controlling the data being passed in the onHandler event, and maybe changing the load rules for the tags if needed.   You should check out the current situation by monitoring which tags are currently firing before you make any changes. With DoubleClick, you can look for the Advertiser ID in the outgoing network requests in Chrome Dev Tools, for example. You might need to tick the check box for "Preserve Log" if the event unloads the current page.   Note that there have been a couple of changes to the way Tealium deals with link and view calls on the page, that the onHandler extensions raise. It used to be that tags that had not been initially loaded on the page would not be loaded even if their load rules would otherwise match. This was changed in more recent versions of utag. See here https://community.tealiumiq.com/t5/uTag/utag-link-and-utag-view/ta-p/11888   There is one other consideration. Not all tags are programmed to respond to both view and link events. You can see which events a given tag will respond to by looking in the tag template for a line like this.   u.ev = {"view" : 1};   This particular example means that the tag only responds to view calls and will ignore link ones.   Finally, with respect to your question about moving to the "best practice" way of having a single DoubleClick tag. This is a valid approach, but you may decide after reading the above that it isn't needed. Hopefully if you do decide to migrate to that approach, the above information will still help you understand how it would work with a single tag.   Mark ... View more

Hi again   Here's some links   http://docs.telerik.com/fiddler/Configure-Fiddler/Tasks/ConfigureForiOS https://www.charlesproxy.com/documentation/faqs/using-charles-from-an-iphone/   Also, it's worth mentioning that putting in Alerts to debug JavaScript is possibly not the most efficient way to track down issues.  If you have a Mac, you can step through and debug JavaScript that is running inside Safari on the iPhone.   http://appletoolbox.com/2014/05/use-web-inspector-debug-mobile-safari/     ... View more