Tealium Learning Center

Hi there @aaqib  We were able to address this issue leveraging a slightly different approach. We removed all "exclusion" based conditions from the Load Rule in question, leaving only the rule we had in place for the trigger based on the site domain; i.e. All Site Pages: Domain > contains (ignore case) > www.mysite.com We then took the two pathname exclusions and established these as independent Load Rules. Exclude Homepage: Pathname > equals > / Exclude Thank you page: Pathname > contains (ignore case) > /thank-you Then in the tag itself we selected all 3 Load Rules under the Match All condition. After considering this approach, I am beginning to like it more and more. What I mean by this is, by setting up the exclusions on their own, we're not establishing single use Load Rule whose use case is so specific that it can't be used beyond the initial request that had us establish it in the first place. We've seen this approach snowball into terribly messy set-ups. I do see the rational for first checking if the domain "exists" before evaluating. I had wondered if the issue we were observing was due to timing given we have the very configuration we were attempting to create established and functioning in a different profile. Sometimes it's difficult to see the forest through the trees. Thank you for jumping on with a suggestion. We definitely appreciate the insight. ... View more

@mkrishe , You can use the built-in Lifetime visit count AS attribute for the visit count and page name is not cleared but if you want to track the current visit pages views then create a visit type number attribute with enrichment of increment/decrement by 1 and add a rule as pageview and within rule apply condition as ut.event =view this will increment only on pageviews. this might look like this: For the timestamp you can create a visit date attribute like this: Now you have all the needed information so if you want to trigger when the lifetime visit count is greater than 5 then create an audience with the same definition Now you have to send this audience to webhook so create a webhook with this audience and set the trigger condition as Joined Audience and do the connector configration and then do the connection action(send customized data via HTTPs advanced) mappin g with the information that you want to pass.  I hope this might be helpful to get started. Please let me know if you are facing any issue. Kind Regards, Mohammed Aaqib Uddin   ... View more

Hi @Davide , We usually follow the Below Tealium documentation for the Implementation. https://docs.tealium.com/platforms/javascript/ or https://docs.tealium.com/ Regarding the data layer you can request for a deployer tool and then add all your pages and events that you track. It's upto you what kind information(variables) you want to pass within utag_data(utag.view()) and utag.link(), for more information please visit: calls. https://docs.tealium.com/platforms/javascript/track/ The below Tealium documentation is useful to understand how it works and within the definition section you can few brand's data layer example that gives an idea on how to get start with building your business specific data layer: https://docs.tealium.com/platforms/getting-started-web/data-layer/how-the-data-layer-works-for-websites/ Please let me know if you have any questions. Kind Regards, Mohammed Aaqib Uddin ... View more

Hi, I've been struggling with this because I've done every single step but upon testing with Trace I seem to join the audience as soon as I view the first product: Audience: Set of Strings (visit): Tally (visit; increment tally based on the product name):   ... View more

Hi @mackaylaheller Please make sure that the _cprice attribute has a value when the purchase event happened, also you can add another AND condition to the rule, let's say _cprice is not empty, which make sure that when it's not empty then only it will try to set to the string. In the end, your rule looks like _cprice is assigned AND _cprice is not empty I hope this will set the value to string if it exists. ... View more

Hi @ApurvTanay  You can create the event feeds and there you can specify the condition which matches the specific condition based on their attribute. And then use that event feed within Tealium Eventstream facebook Capi connector. For Example: if you want to send a purchase event you will create an event feed with the attribute that you want to check and only send when those attributes are not empty. I hope this may resolve your issue. For more information: https://community.tealiumiq.com/t5/Customer-Data-Hub/Live-Events-and-Feeds/ta-p/11805#toc-hId--1015759036 ... View more

Hi @north If you implemented the Facebook pixel using Tealium IQ then make sure that you enabled the "Generate Event ID" turned on which will generate a random ID and sent it to the pixel automatically and the same is also passed to Tealium Eventstream as shown below. And in the server-side eventstream, add all the eventid attributes which you want to send to Facebook. For example, if you want to send a pageview event from the server-side then as shown in the above screenshot there is an attribute called "fb_event_id_PageView" is available, make sure that you have added this attribute as eventstream attribute in order to send the ID, likewise for each standard event an Event ID attribute with the name is populated for example: "fb_event_id_ViewContent". Once you can have a separate event feed created for all the events that you want to send to Facebook, next step would be creating a Facebook Conversion action using those event feed. For example, if you want to send pageviews then you'll create an event feed that makes sure that only pageviews events are being included, then you'll create an FB conversion action using this event feed and your event data mapping will look like something like this once you finish your connector configuration and publish the changes then this setup will make sure that the correct eventid is being passed for the pageview. likewise for other events also please make sure to use the event-based event ID attribute in your mapping.     ... View more

Hi @mark_reddin, thanks for the alternative solution, the delayed connector works for me by  setting up the triggering of the action at the end of the visit where the user is in an Audience. I'm using this solution in most of my recent implementations and really like the logic  And sorry for marking this as a solution too late, because I'm been busy/inactive and didn't get a chance. Thanks for the kind support and help, much appreciated.   ... View more

Hi, Refer the below documentation on Connectors. https://docs.tealium.com/partners/connectors/ ... View more

Hi @aaqib,. Thanks for your response. We would prefer to use TiQ to track conversion data. I understand that by default, TiQ captures data in the default variables (see below image): Therefore, is it possible to use the TiQ data to capture form start and form complete conversions if the URLs are different? For example: Form start: www.abc.com/form/1234 Form complete: www.abc.com/form/1234/thankyou If so, then there isn't a need to implement utag_data but just utag.js? Thanks, Max ... View more

Hi @LordLingham, Thanks for your help & support, I'll raise a support ticket for this issue. Kind Regards, Md Aaqib Uddin ... View more