Tealium Learning Center

Hi @sujani_koya,   I believe that Rakuten leverages "rm_trans" as an object for all of the data they are tracking from the confirmation page. You should be able to open up the console and type in rm_trans to view that object and see if the price parameter is being passed as you expect. Two additional steps that you could take would be:   1.) look in the network of your developer tools and filter for your unique Rakuten client ID to see what data is being passed in that network pixel request   2.) in your console, on the confirmation page, open up utag_data to view the variable you have used in the mapping within TiQ to confirm that it is populating as expected   If there are additional questions or concerns, feel free to reach out to your account manager to open up a support ticket or contact your Rakuten representatives to confirm that all data appears to be configured as expected.   Hope that helps, Chris     ... View more

@sujani_koya   I believe we have resolved this via your ticket submitted to your AM, but for your reference a custom mapping would need to be configured within the actual tag template in order for the ranMID to be passed over to the custom Rakuten object.  ... View more

@momen,   You can overwrite the location parameter for the Google call by mapping a variable to the "location" destination in your Google Analytics tag mapping toolbox. This variable should be dynamically updated with the value in your utag.link or utag.view call for all subsequent (not initial pageview) events for your REACT setup. Also, you will want to make sure that you have the "clear vars" setting within the tag's configurations set to "on" to make sure that all variables set with the "SET.xxxx" method from Google are cleared out.    Hope that helps!   Chris ... View more

@sailakumari_pay For custom dimensions on product events such as "detail" or "purchase" you can select the 'premium dimension' field for custom dimension above 21 (from 21-200). In order to change the actual custom dimension numeric parameter, you can simply click on the mapping field once selected (see screen shot) and change the value to "##" (35 in my example).  Hope that helps! Chris   ... View more

@jarno_rossi What version of utag.js are you running? On some of the later versions (4.4 + ) the "b" object is going to be a copy of the data that you are firing for a specific event at that moment, meaning if you fire a utag.view() or a utag.link() call, the "b" object will only include the parameters that you pass in with that call and not the original variables from your data layer. This means that you would need to add in additional logic to include the b.Abort variable from a previous event on the page or re-setting it with the new call.   On older versions of utag.js (4.39 and earlier) the "b" object would include all parameters sent with a utag.view/link() call as well as any other original variables from your utag_data (data layer).    Hope that helps!   Chris ... View more

@jarno_rossi, most extensions (such as the set data values extension) have the ability to set a variable to text, another variable, or Javascript. You can leverage this "javascript" feature to use algebra for adding, multiplying, etc., for the value you are looking for.  ... View more

@Srinivasan,   There are a couple of things that you can do to help clean up or organize your profile:   1.) Prevent any user from publishing while another user is making changes. This ensures that you do no have 1 user overwriting the work of another current user.   2.) Leverage labels. This will help to prevent certain users from editing a tag that is not in their "group"   3.) Keep all three of your environments completely separate. This means that you would do all intitial staging working in the "dev" profile. Then, once everything is ready and validated by some overseeing user, you would move them into the QA environment. After that point, all changes are pushed to PROD. The easiest way to do this would be to keep a detailed list internally of what items are being worked on and nobody pushes up to a higher environment until all other parties are ready.    4.) Only allow certain users the ability to publish to certain environments (i.e. you have 3-4 'super' users that validate all changes before pushing to prod, etc.)   5.) Utilize libraries. This would allow you to have one profile that inherits changes from different libraries where certain teams can do their work. You could have an "analytics" library, a "marketing" library... etc.   These are just a few ideas that you can bounce around internally, but they have worked for other clients in the past. ... View more

@mitchellt @shailesh_gaikwa   To fire multiple Custom Audience ID's, you can pass through the ID's as a comma separated list in the custom audience pixel ID mapping on a per-event basis or in the standard configuration if you want them both to fire across all instances. The following article from the learning community discusses these mappings, as well as other configurations, that you can leverage to make your tag more robust and dynamic:   https://community.tealiumiq.com/t5/Tags/Facebook-Tag-Basic-Configuration-and-Mapping/ta-p/10413 ... View more

Shailesh,   When there are two Facebook tags loading on the same page there is an issue with a collision of the same objects being utilized by the Facebook library. This leads to an overwrite of some of the necessary parameters that one of the two tags may be leveraging at that time and, especially on events, will cause issues and often stops the events from even happening.  ... View more

michaelb   This will work correctly for suppressing the initial pageview; however, keep in mind that this will suppress the initial pageview for all tags loading in with utag.js, not just the Google Analytics tag.  ... View more

There are some instances where the publishing engine does not push out all of the changes if you only made an update to the tag template itself. This is an issue currently being worked on internally with our engineering team. My recommendation would be to add then delete and extension or mapping so that a larger change was detected and then republish out. This should help the version to sync with your modified changes.  ... View more

@tom_butkevich,   It is still not available; however, engineering is working hard on getting this out as soon as possible and it should be available in the very near future.    ... View more

Hello @joecbrown. In order to accomplish this you would need to leverage cookie or sessionstorage for each page. When the page initially loads in, you would want to write some custom JS that would verify if your interval is actually running at that point. If it isn't, you would then look at the data that had been persisted in the local storage, utilize that data for the incrementing storage, and then begin your interval again.  ... View more

@jan_van_damme,   Yes, you can utilize a Javascript extension scoped to your DC tag with the following script:   u.ev = {'view' : 1, 'link' : 1} The extensions portion of the tag will execute after u.ev has been created, so this will allow you to manipulate the object and specify the type of event (view or link) that the tag can load on.   You can also create 1 DC Floodlight tag, update the u.ev parameters, and then utilize a lookup table if you have many tags firing in accordance with that. Either way works.   Hope that helps you :)   Chris ... View more

Miguel,   Glad you have found what was going on. Keep in mind that for the custom container tag, it is important to not simply paste in the code provided by your vendor, but to go through the template and place in the necessary code where it applies (i.e. the 'url' for the tag in the 'base_url' portion of u.data, etc.). Good luck! ... View more