Tealium Learning Center

Yes, it is possible to implement GA4 Tracking Server Side using EventStream only. However, the GA4 tag in TiQ is still recommended to be implemented as well. The GA4 tag in TiQ allows you to collect additional data that is not available through EventStream, such as page views, custom events, and user engagement data. This data can be used to improve your understanding of your users and their behavior, and to create more targeted marketing campaigns. ... View more

Sure, I can help you with that. Tealium and AEM can be integrated in a few different ways. One way is to use the Tealium AEM Tag Manager. The Tealium AEM Tag Manager is a JavaScript library that makes it easy to add Tealium tags to your AEM pages. Another way to integrate Tealium and AEM is to use the Tealium Collector SDK. The Tealium Collector SDK is a Java library that can be used to collect data from your AEM pages. The data collected by the Tealium Collector SDK can then be sent to Tealium's cloud platform for processing and analysis. Finally, you can also integrate Tealium and AEM by using the Tealium API. The Tealium API allows you to programmatically add Tealium tags to your AEM pages and send data to Tealium's cloud platform. Here are the steps on how to integrate Tealium and AEM using the Tealium AEM Tag Manager: Install the Tealium AEM Tag Manager library on your AEM pages. Configure the Tealium AEM Tag Manager library with your Tealium configuration. Add Tealium tags to your AEM pages using the Tealium AEM Tag Manager library. Here are the steps on how to integrate Tealium and AEM using the Tealium Collector SDK: Add the Tealium Collector SDK to your AEM pages. Configure the Tealium Collector SDK with your Tealium configuration. Start collecting data from your AEM pages using the Tealium Collector SDK. Here are the steps on how to integrate Tealium and AEM using the Tealium API: Generate a Tealium API key. Use the Tealium API to add Tealium tags to your AEM pages. Use the Tealium API to send data to Tealium's cloud platform. I hope this helps! Let me know if you have any other questions. Regards Shiivam Joshi Devsatva ... View more

Hi Davide, Yes, you are correct. If you are using the Tealium SDK and utag.js on the same hybrid app, then every webview will generate two entries in Adobe Analytics: one as a web page and one as an app page. This is because the Tealium SDK and utag.js are both tracking the webview, and they are both sending the data to Adobe Analytics. There is a way to stop the web one from being sent to Adobe Analytics. You can do this by setting the allowAppTracking property to false in the utag.js configuration. Here is an example of how to do this: utag.config.allowAppTracking = false; This will prevent the webview from being tracked by utag.js, and it will not be sent to Adobe Analytics. However, it is important to note that this will also prevent the webview from being tracked by the Tealium SDK. This means that you will not be able to track any events that occur in the webview, such as clicks or page views. If you are not tracking any events in the webview, then you can safely set the allowAppTracking property to false. However, if you are tracking events in the webview, then you will need to decide whether you want to track the webview as a web page or as an app page. I hope this helps! Let me know if you have any other questions. Regards Shivam Joshi Devsatva ... View more

Hello Davide, Implementing the Tealium mobile SDK in a React Native app, along with integrating Adobe Analytics, can be done effectively. Let's go over the usage of the Adobe Experience Cloud ID Service tag (visitorAPI) and how it works within a mobile app. The Adobe Experience Cloud ID Service tag (visitorAPI) is used to manage the Experience Cloud ID (ECID) for tracking and identifying visitors across different devices and touchpoints. It helps maintain consistency in user identification and data stitching. In a mobile app, the ECID is typically generated and managed by the Tealium mobile SDK. To implement Adobe Analytics in a React Native app with Tealium, here are the general steps: Install the Tealium mobile SDK in your React Native app by following the documentation and integration guides provided by Tealium. Set up the Adobe Analytics integration in Tealium IQ: In your Tealium IQ account, configure the Adobe Analytics tag and define the necessary mappings and settings to track and send data to Adobe Analytics. Ensure that the required Adobe Analytics libraries and configurations are properly set up within the Tealium IQ tag. Initialize the Tealium SDK and configure Adobe Analytics: In your React Native app, initialize the Tealium SDK by providing the appropriate configuration, including your Tealium account details and any custom settings. Within the Tealium configuration, make sure to include the necessary settings for Adobe Analytics integration, such as the report suites, tracking variables, and any additional configuration required for your analytics implementation. Data Layer and Event Tracking: Define your app's data layer, which represents the data structure and variables you want to track and send to Adobe Analytics. Utilize the Tealium mobile SDK's functions and methods to track events, screen views, and other user interactions, passing the relevant data from your app's data layer to Tealium. Regarding the ECID (Experience Cloud ID), it is generated and managed by the Tealium mobile SDK. You don't need to pass it explicitly from the app's data layer to the visitorAPI tag. The Tealium SDK takes care of managing the ECID and sending it to Adobe Analytics when tracking events. The documentation link you provided seems to be cut off, so I couldn't view the specific details. However, Tealium's official documentation should provide you with the necessary information on implementing Adobe Analytics in a mobile app, including best practices and guidelines. I recommend exploring the Tealium documentation for Adobe Analytics integration in mobile apps. Additionally, you can refer to the Adobe Analytics documentation for general guidance on mobile app tracking and best practices. Adobe provides detailed resources and guides specifically tailored to implementing Analytics in mobile apps, which can help you understand the recommended approaches and techniques. If you encounter any specific issues during the implementation or have further questions,Let me know. Regards Shivam Joshi Devsatva ... View more

val config = TealiumConfig() config.flushIntervalMillis = 10000 Tealium.initialize(config) Try This ... View more

Hello Raghav, Integrating Tealium AudienceStream with AEM (Adobe Experience Manager) for running a Mobile In-App Messaging campaign is possible and can be achieved through a combination of Tealium's mobile SDK and the integration capabilities provided by AEM. While I can provide you with some general guidance, it's important to note that the specific implementation details may vary depending on your organization's setup and requirements. Here are the general steps to integrate Tealium AudienceStream with AEM for Mobile In-App Messaging: Tealium Setup: Set up an AudienceStream account in Tealium, if you haven't already. Install the Tealium mobile SDK in your mobile app. The SDKs provided by Tealium support various mobile platforms like iOS and Android. You can find the SDK documentation and integration guides on the Tealium website. AEM Setup: In AEM, configure your Mobile In-App Messaging campaign using the built-in features of AEM's CMS. Depending on your specific requirements, you may need to customize the AEM integration to work seamlessly with Tealium AudienceStream. This can involve using AEM's APIs or custom code to send data to AudienceStream or retrieve data from it. Data Integration: Ensure that the necessary data points and events are captured and sent to AudienceStream from your mobile app. This can include user interactions, app events, and other relevant data. Utilize Tealium's mobile SDK to send this data to AudienceStream. The SDK documentation should provide details on how to send custom events and data to AudienceStream. AudienceStream Configuration: Set up the necessary AudienceStream configurations to handle the data sent from the mobile app. Create relevant audience segments and define rules in AudienceStream to identify and target specific user segments for your Mobile In-App Messaging campaign. Personalization and Messaging: Leverage the audience segments created in AudienceStream to personalize and trigger targeted in-app messages within AEM. Use AEM's capabilities to create and deliver personalized messages to specific users based on the audience segments defined in AudienceStream. It's important to note that the specific implementation steps may vary depending on your organization's setup, the version of AEM you are using, and any additional integrations you may have in place. ... View more

The Tealium iQ Platform is now called the IQ Tealium Management ... View more

Hi! I apologize for the inconvenience. The batchEvents function was deprecated in Tealium Collect 2.5.0. You can now use the flushInterval function to control the frequency at which events are sent to Tealium. Here is the updated code: import com.tealium.collect.TealiumConfig fun main(args: Array<String>) { // Create a TealiumConfig object val config = TealiumConfig() // Set the flush interval to 15 seconds config.flushInterval = 15000 // Initialize Tealium Collect val tealium = Tealium(config) // Track an event tealium.track("event1") } This code will set the flush interval to 15 seconds. This means that events will be sent to Tealium every 15 seconds. I hope this helps! Let me know if you have any other questions. ... View more

Hi! Yes, you can set different retention periods for different audiences in Tealium. To do this, you need to use the Audience Retention settings in the Tealium iQ Platform. Here are the steps on how to set different retention periods for different audiences in Tealium: In the Tealium iQ Platform, open your profile. In the "Audiences" section, click on the "Audience Retention" tab. In the "Audience Retention" section, you will see a list of all of your audiences. For each audience, you can set the retention period in days. Once you have set the retention periods for all of your audiences, click on the "Save" button. Here are some additional things to keep in mind: The default retention period for all audiences is 395 days. You can set the retention period for an audience to be any value between 1 day and 395 days. If you do not set a retention period for an audience, the default retention period of 395 days will be used. I hope this helps! Let me know if you have any other questions. ... View more

Here is the code: Kotlin import com.tealium.collect.TealiumConfig fun main(args: Array<String>) { // Create a TealiumConfig object val config = TealiumConfig() // Disable batch events config.batchEvents = false // Initialize Tealium Collect val tealium = Tealium(config) // Track an event tealium.track("event1") } This code will disable batch events for Tealium Collect. This means that events will be sent to Tealium immediately, instead of being batched together and sent later. ... View more

Hi Kat, Yes, it is possible for a different Tealium Profile to assign attributes to a visitor profile that resides in another Tealium Profile. This is done by using the cross-profile visitor stitching feature in Tealium. Cross-profile visitor stitching allows you to associate visitor profiles from different Tealium Profiles. This means that you can track a visitor across multiple websites or applications, even if they are governed by different Tealium Profiles. To use cross-profile visitor stitching, you need to configure the visitor ID attribute in each Tealium Profile. The visitor ID attribute is a unique identifier that is assigned to each visitor. Once you have configured the visitor ID attribute, you can use the cross-profile visitor stitching feature to associate visitor profiles from different Tealium Profiles. Once you have associated visitor profiles, you can access and use the attributes that are stored in the visitor profiles from any Tealium Profile. In your example, the visitor profile would be created in Tealium Profile A. When the visitor visits the web page governed by Tealium Profile B, the visitor ID attribute would be passed from Tealium Profile A to Tealium Profile B. The visitor ID attribute would then be used to associate the visitor profile in Tealium Profile A with the visitor profile in Tealium Profile B. Once the visitor profiles are associated, the attribute that was set in Tealium Profile B would be accessible from Tealium Profile A. Here are the steps on how to configure cross-profile visitor stitching in Tealium: In the Tealium iQ Platform, open your profile. In the "Settings" section, click on the "Visitor Stitching" tab. In the "Cross-Profile Visitor Stitching" section, enable the "Enable Cross-Profile Visitor Stitching" setting. In the "Visitor ID Attribute" field, enter the name of the visitor ID attribute. Save the profile. Once you have configured cross-profile visitor stitching, you can use the cross-profile visitor stitching feature to associate visitor profiles from different Tealium Profiles. I hope this helps! Let me know if you have any other questions. ... View more

In the "else" statement, you can write the following code: Code snippet utag.sender[ga4_tag_id].enabled = false;   This code will disable the GA4 tag from firing. Here is an explanation of the code: The utag.sender[ga4_tag_id] object represents the GA4 tag. The enabled property of the utag.sender[ga4_tag_id] object controls whether the tag is enabled. Setting the enabled property to false will disable the tag from firing. Here is the complete code: Code snippet var ga4_tag_id = 4; if(b['visitor_customer_id'] && utag.sender[ga4_tag_id]){ u.data.base_url = "new_url" } else{ utag.sender[ga4_tag_id].enabled = false; } I hope this helps! Let me know if you have any other questions. ... View more

Sure, I can help you with that. To register an event on Tealium that will be sent to both the UA and GA4 properties whenever a form is successfully directed to the thank-you page, you can follow these steps: In the Tealium iQ Platform, create a new event. In the event configuration, set the event name to "Form Submitted". Set the event type to "Custom". In the event parameters, add the following parameters: event_name: The name of the event. event_timestamp: The timestamp of the event. form_id: The ID of the form that was submitted. thank_you_page_url: The URL of the thank-you page. In the event configuration, set the "Send to" settings to "Both UA and GA4". Save the event. Once you have saved the event, you will need to add the event tag to your website. You can find the event tag in the Tealium iQ Platform. Once the event tag is added to your website, whenever a form is successfully submitted, the event will be sent to both the UA and GA4 properties. Here is an example of the event tag that you can use: Code snippet <script> tealium.track("Form Submitted", { event_name: "Form Submitted", event_timestamp: new Date().getTime(), form_id: "123456", thank_you_page_url: "https://www.example.com/thank-you", }); </script>   I hope this helps! Let me know if you have any other questions. ... View more

There are a few possible reasons why the Activity Map might not be populating on your SPA pages. One possibility is that the Tealium JavaScript library is not being loaded correctly on these pages. Another possibility is that the Activity Map configuration is not correct for SPA pages. To troubleshoot this issue, you can try the following steps: Verify that the Tealium JavaScript library is being loaded correctly on your SPA pages. You can do this by checking the browser's developer tools to see if the library is being loaded and if there are any errors. Verify that the Activity Map configuration is correct for SPA pages. You can find the Activity Map configuration in the Tealium iQ Platform. If you are still having problems, you can contact Tealium support for help. Here are some specific things to check: Make sure that the Tealium JavaScript library is loaded in the header of your SPA pages. Make sure that the Activity Map configuration is set to "SPA". Check the browser's developer tools to see if there are any errors in the Tealium JavaScript library. Contact Tealium support for help if you are still having problems. I hope this helps! Let me know if you have any other questions. ... View more

There is no internal service in Tealium that can be enabled to trigger an alert if no data has been imported for the past 24 hours. However, there are a few third-party tools that can be used for this purpose. One option is to use a cloud-based monitoring tool such as Datadog or New Relic. These tools can be configured to track the number of rows imported into Tealium each day. If the number of rows drops below a certain threshold, an alert can be triggered. Another option is to use a custom script. You can write a script that checks the Tealium data import logs for the past 24 hours. If no new rows have been imported, the script can send an email alert to the team. Here are some specific tools that you can use: Datadog: Datadog is a cloud-based monitoring tool that can be used to track a variety of metrics, including the number of rows imported into Tealium. You can configure Datadog to send alerts if the number of rows drops below a certain threshold.   New Relic: New Relic is another cloud-based monitoring tool that can be used to track the number of rows imported into Tealium. You can configure New Relic to send alerts if the number of rows drops below a certain threshold.   Custom script: You can write a custom script that checks the Tealium data import logs for the past 24 hours. If no new rows have been imported, the script can send an email alert to the team. I hope this helps! Let me know if you have any other questions. ... View more

Hi Dennis, I appreciate your curiosity and proactive approach to problem-solving. This type of thinking is fundamental to ensuring seamless operation and achieving scale in any technology-driven environment. Audience Engagement Monitoring: Understanding your users is at the heart of delivering valuable experiences. For this, analytical tools like Google Analytics, Mixpanel, or Amplitude can help. These platforms can give you a clear snapshot of user activity, and you can set up alerts when a drop in engagement is noticed. More technically, on the server-side, consider robust tools like Datadog, Prometheus, or New Relic. Error Detection in Connectors: Connectors, being the glue between different components, play a critical role in your ecosystem. Depending on the nature of these connectors, you have a variety of monitoring tools available. For database connections, you may want to look at SolarWinds Database Performance Monitor or Redgate SQL Monitor. For API connections or web servers, Datadog, Prometheus, New Relic, or perhaps Azure Monitor if you're using Azure services, could be considered. JavaScript Function Error Tracking: In terms of capturing JavaScript function errors, it's important to differentiate between client-side and server-side. For the former, you may want to consider Sentry, Rollbar, or LogRocket - tools specifically built to track and report such errors. For server-side JavaScript (Node.js), similar tools can be used, along with application performance monitoring solutions like New Relic or Datadog. If existing solutions don't quite meet your specific needs, building a custom solution using the HTTP API of a monitoring system like Prometheus might be a way forward. Additionally, Grafana can be of great help for visualizing data and setting up custom alerts. Remember, it's important to choose the right tool for your specific environment, be it cloud-based or on-premises. Thanks and Let me know if you need more help on this. Regards Shivam Devsatva ... View more

Check your utag.sync.js script file. Make sure that the file is included in your website's header and that the path to the file is correct. ... View more

The error you're seeing, "Multiple requests were attempting to modify the same resource at once. Retry the request", is indicating a concurrency issue. Google Ads API is designed to allow one operation at a time on a specific resource. If two or more requests are trying to modify the same resource simultaneously, it leads to a conflict, and the Google Ads API will throw an error message, which is what you're seeing. This could potentially occur if you have multiple actions in your Google Ads Customer Match connector that are attempting to update the same audience list at the same time. Or, if you have other processes outside of Tealium (like scripts or other applications) that are also trying to modify the same Google Ads resource at the same time as Tealium. Here are few suggestions on how to address the issue: Ensure unique resources for each action: Try to isolate which resource (for example, a specific audience list) is causing the issue and see if it's being modified by more than one action or process. If possible, create unique resources for each action to avoid any conflict. Synchronize the actions: If multiple actions must modify the same resource, try to synchronize them so they don't occur at the same time. You might be able to do this by scheduling the actions at different times or by adjusting their triggering events so they don't overlap. Retry logic: Implement a retry logic in case of failures. This is not a direct solution to the problem but might help in scenarios where the error is not consistent and happens sporadically. ... View more

  Yes, there are a few ways to monitor the connectors data like total, success, error for all connectors in Power BI using an API or other solution. One way is to use the Power BI REST API. The Power BI REST API allows you to programmatically access and manage Power BI resources, including connectors. You can use the Power BI REST API to get the total, success, and error counts for all connectors. To use the Power BI REST API, you will need to: Register an Azure Active Directory (Azure AD) application. Obtain a client secret for your Azure AD application. Use the client secret to authenticate to the Power BI REST API. Use the Power BI REST API to get the total, success, and error counts for all connectors. Here is an example of how to use the Power BI REST API to get the total, success, and error counts for all connectors: Code snippet import requests # Get the client secret for your Azure AD application. client_secret = "your_client_secret" # Create a request object. headers = { "Authorization": "Bearer " + client_secret, } url = "https://api.powerbi.com/v1.0/myorg/connectors" # Make a GET request to the Power BI REST API. response = requests.get(url, headers=headers) # Get the total, success, and error counts from the response. total_count = response.json()["total"] success_count = response.json()["success"] error_count = response.json()["error"] # Print the total, success, and error counts. print("Total:", total_count) print("Success:", success_count) print("Error:", error_count) Another way to monitor the connectors data like total, success, error for all connectors in Power BI is to use a third-party monitoring solution. There are a number of third-party monitoring solutions that can be used to monitor Power BI, including: Microsoft Azure Monitor AppDynamics New Relic Dynatrace These third-party monitoring solutions can be used to collect data from Power BI, including data on the connectors. This data can then be used to monitor the connectors for errors and other issues. Monitoring the connectors data like total, success, error for all connectors in Power BI is important for ensuring that the connectors are working properly and that data is being imported and exported successfully. By monitoring the connectors data, you can identify and resolve any issues with the connectors as soon as possible. ... View more

The issue you're encountering, "utag is not defined," often occurs when you're trying to use the utag object before it has been fully loaded and initialized. This is a timing issue. Your code attempts to access the utag object immediately after the script tag to load utag.js has been inserted into the page. However, the script is loaded asynchronously, meaning it may not be fully loaded and executed by the time your code runs. Try adjusting your code to ensure that the utag object is defined before you try to use it. You could accomplish this by adding an event listener for the load event of the script tag. When the load event fires, it signifies that the script has been fully loaded and executed, so utag should now be defined. Here's a sample code snippet:" (function(a,b,c,d){ a='//tags.tiqcdn.com/utag/aa/amadeus/'+ detect platform()+ '/utag.js'; b=document; c='script'; d=b.createElement(c); d.src=a; d.type="text/java"+c; d.async=true; a=b.getElementsByTagName(c)[0]; a.parentNode.insertBefore(d,a); // Add event listener for the load event of the script d.addEventListener('load', function() { // Block the default view call window.utag_cfg_ovrd = window.utag_cfg_ovrd || {}; window.utag_cfg_ovrd.noview= true; console.log("Set the noview to true!"); if (utag) { utag.view(utag_data); console.log("utag.view call fired!"); } }); })(); Please note that this code still assumes that detect platform() and utag_data are properly defined elsewhere in your code. If they are not, you may still encounter errors. Remember to test this code thoroughly in a development environment before deploying to production. ... View more

Yes, you can use UTAG.JS to generate/access the tealium_visitor_id. UTAG.JS is a JavaScript library that allows you to interact with Tealium's data warehouse. To use UTAG.JS, you will need to include the library in your website's header. Once you have included the library, you can use the following code to generate/access the tealium_visitor_id: var tealium = new Utag.js(); var visitorId = tealium.getVisitorId(); This approach has a low level of effort required as it will form part of the payload configuration. Here are the steps on how to use UTAG.JS to generate/access the tealium_visitor_id: Include the UTAG.JS library in your website's header. Create a new Utag.js object. Call the getVisitorId() method on the Utag.js object. The getVisitorId() method will return the tealium_visitor_id. Here is an example of how to use UTAG.JS to generate/access the tealium_visitor_id: <script src="https://cdn.tealium.com/tag/utag.js"></script> <script> var tealium = new Utag.js(); var visitorId = tealium.getVisitorId(); </script> This code will generate/access the tealium_visitor_id and store it in the variable visitorId. You can then use the visitorId variable to access the tealium_visitor_id in your code. ... View more

There are a few ways to fetch the tealium_visitor_id. Method 1: Use the Tealium API. The Tealium API allows you to access data from Tealium's data warehouse. To use the API, you will need to create an API key. Once you have an API key, you can use the following API call to fetch the tealium_visitor_id: https://api.tealium.com/v1/visitors/get?visitorId=<visitorId> Method 2: Use the Tealium JavaScript SDK. The Tealium JavaScript SDK allows you to access Tealium's data warehouse from your website. To use the SDK, you will need to include the Tealium JavaScript library in your website's header. Once you have included the library, you can use the following code to fetch the tealium_visitor_id: var tealium = new Tealium(); var visitorId = tealium.getVisitorId(); Method 3: Use the Tealium Tag Manager. The Tealium Tag Manager allows you to manage Tealium's data warehouse from a graphical user interface. To use the Tag Manager, you will need to create a Tag Manager account. Once you have created an account, you can use the Tag Manager to create a tag that will fetch the tealium_visitor_id. Other IDs that Tealium supplies In addition to the tealium_visitor_id, Tealium also supplies a number of other IDs. These IDs include: cookie_id: The cookie_id is a unique identifier that is stored in the visitor's browser. device_id: The device_id is a unique identifier that is assigned to the visitor's device. ip_address: The ip_address is the visitor's IP address. user_agent: The user_agent is the visitor's browser's user agent string. These IDs can be used to track visitors across multiple devices and browsers. They can also be used to segment visitors and target them with different marketing campaigns. ... View more