Tealium Learning Center

Tealium is proud to introduce our newest product, Tealium Predict, a fully-managed product that simplifies machine learning. Predict is a built-in machine learning technology product used with Tealium AudienceStream CDP. With this release, Tealium takes the complicated discipline of machine learning and distills it down to specific functions. In just a few clicks, Predict can create a model with a new output attribute that is immediately made actionable in AudienceStream. How it Works Using Predict, you can create, optimize, and deploy data models that make meaningful predictions about your visitor behavior. Deployed models are managed by Tealium in real-time using a predictive attribute that is made available to you after your model is trained and deployed. Coupled with Tealium AudienceStream, Tealium Predict activates trustworthy machine learning insights across your entire implementation by helping you create more intelligent audiences Video Demo Enjoy the following video overview about how to create a model and interpret results using Tealium Predict. Get Started To learn more and get started, see the Tealium Predict User Guide. ... View more

The previously announced Load Order Manager experiment has several improvements planned in preparation for its general release.  You can be notified of the updates by following this post -- just click Follow at the top of the page.  In this article: Table of Contents Placeholder Overview Since the launch of the Load Order Manager experiment we have received feedback from many users and will be incorporating those suggestions into upcoming releases. The Load Order Manager is an essential part of tag management that will benefit all users so we encourage you to enable the experiment and try it out.  You will notice new features getting released over the coming weeks, so we’d love to hear your feedback or know of any issues you might come across. For detailed information about using Load Order Manager, see Load Order Manager (BETA). Planned Improvements The following updates are planned for the Load Order Manager: Display the Load Order Manager in a slide-out instead of a modal window to provide a larger workspace. Ability to collapse scope groups. Ability to hide inactive tags and extensions. Ability to sort tags or extensions on the list view. Ability filter tags or extensions on the list view. Ability to edit extension scope directly from the list view. Ability to add tags to tag-scoped extensions directly from the list view. Various bug fixes. Releases 2020-07-02 Display the Load Order Manager in a slide-out instead of a modal window. Feedback Yes! To provide feedback, go to Load Order Manager Feedback. All feedback will be reviewed and considered for the final release.   ... View more

This article describes the Tealium Predict product and how it is used to create, train, and deploy machine learning models and use these models to make predictions about visitor behavior. In this article: Table of Contents Placeholder How it Works Tealium takes a complicated discipline (Machine Learning) and distills it down to specific functions. Tealium Predict is a built-in machine learning technology product used with the Tealium Customer Data Platform (CDP), AudienceStream. This article describes how to use Tealium Predict to build and deploy meaningful machine learning models to make predictions about visitor behavior. Tealium Predict is a fully-managed feature that simplifies machine learning. Coupled with AudienceStream, Tealium Predict activates trustworthy machine learning insights across your entire tech stack through the creation of more intelligent audiences. Using Predict, you can create, optimize, and deploy data models that make meaningful predictions about your visitor behavior. Deployed models are managed by Tealium in real-time using a predictive attribute that is made available to you after your model is trained and deployed. In just a few clicks, Predict can create a model with a new output attribute that is immediately made actionable in AudienceStream. Key Benefits Using Predict, you can automatically draw conclusions about what customers are likely to do in the future and design tailored programs that directly address their needs. Key benefits of Predict include: Simplification Tealium simplifies the implementation of Machine Learning for you without the need for a Data Scientist or dedicated team. Personalization You can rely on the Tealium Customer Data Hub to pinpoint meaningful visitor personalization data. Reduce Time Spent on Machine Learning Projects that Involve User Data With Tealium AudienceStream, data collection and data activation are natively integrated with machine learning intelligence, which greatly reduces the common challenges of data preparation and activation for machine learning initiatives. Leverage Machine Learning Intelligence Across your Entire Implementation You can automatically activate predictive insights in any of Tealium’s over 1,200 integrations. Score Customers with Predictive Potential The Predict model scores visitors with the likelihood to return or complete a specific behavior. You can then leverage the scores to generate audiences for further proactive action, such as re-engagement campaigns. Machine Learning Experience Levels If you are new to machine learning and want to get started, Tealium Predict allows you to create a model, deploy it, and immediately activate the value in Tealium AudienceStream without writing a single line of code. If you have existing machine learning projects, Predict will allow you to quickly inject the value of the existing machine learning models into your marketing and analytics implementation to creating an immediately improved data flow cycle. Learn More About the Technology To learn more about Machine Learning technology, see Machine Learning Concepts and Technology. Get Started To get started, click a topic to the left and move through each step as needed. ... View more

Learn how event logging works for Tealium Consent Management. In this article: Requirements Tealium DataAccess (EventStore or EventDB) How It Works The event logging feature captures changes in user consent and works with all of the Tealium Consent Management offerings. When Tealium Consent Management is deployed to your site and event logged is enabled, each time a visitor grants or revokes consent using the consent prompt, adjusts consent preferences, or changes the "Do Not Sell" option, the new consent state is logged using an HTTP request. For customers of Tealium DataAccess, these events are stored in EventDB and EventStore. For customers with their own data collection endpoint, a custom URL can be used to receive the events. The event logging option is offered to help you comply with   Recital 42   of the GDPR, which requires that proof of consent be available for auditing purposes. Event Logging Settings  The following settings are available: Log Consent Changes - set to Yes to enable event logging (applies to all consent management offerings). Event Log URL - the event collection endpoint used to log consent changes. Only edit this setting if you have your own data collection endpoint. Default:  https://collect.tealiumiq.com/event Event Log Profile - the profile to which logged events should be sent. The value set here is passed to the Event Log URL as the parameter tealium_profile="PROFILE" . Related Topics Tealium Consent Management Consent Change Event Specifications Tealium HTTP API ... View more

This release includes the all-new feature,  CCPA Consent Manager for Tealium iQ Tag Management. The CCPA Consent Manager enables you  to add a privacy banner and popup to your site in support of compliance for the California Consumer Protection Act (CCPA). Other updates in this release include improvements to tag categorization and event logging for all consent management features.  In this announcement: Table of Contents Placeholder CCPA Consent Manager The new CCPA Consent Manager for Tealium iQ Tag Management is now available to help you stay compliant with the California Consumer Protection Act. With just a few easy steps you can add a privacy banner and popup to your site without any additional coding. What is CCPA? The California Consumer Privacy Act (CCPA) is legislation that secures new privacy rights for California consumers. This sweeping legislation creates significant new requirements for identifying, tracking, and deleting consumer privacy information. All companies subject to CCPA must adhere to the new regulations or face fines and other legal reprimands. The date to begin enforcement for CCPA compliance is July 1st, 2020. How Tealium Can Help If your company is subject to CCPA you are responsible for ensuring that you provide a "Do Not Sell My Information" link on your website or mobile app and to give your users the option to opt-out of the sale of personal information. Tealium iQ Tag Management offers consent management tools to help you comply with these requirements. The CCPA Consent Manager offers the following components in support of CCPA: Banner and Popup Configure both a banner and popup to cover the full "Do Not Sell" experience. The banner displays the necessary message to the user at the bottom of the screen and includes a link that pops up the "Do Not Sell" prompt and a link to your policy about the sale of personal information. Popup Configure a dedicated "Do Not Sell" popup for for use with your existing privacy banner. The popup provides a link to your "Do Not Sell My Information" disclosure page and a toggle for the user to opt-in or opt-out of the sale of information. Features Multi-Language Support Customizable Content: Message, Do Not Sell link, Call to Action Button, etc. Fully Customizable Presentation: HTML, JavaScript, and CSS Global Settings (for multiple profiles) Preview Mode Tags Affected by Do Not Sell The CCPA Consent Manager improves to the way that tags are categorized to allow more flexibility over which tags are governed.  In the CCPA Consent Manager tags are governed by by their UID, which means that two instances of the same tag can appear in different categories. This allows tags to be categorized based on their specific behavior (for example, whether they sell personal information), instead of based on their general purpose. Release Notes Added the CCPA Consent Manager, with banner and popup workflow. Tags can be categorized as “Do not sell personal information”. Updated the consent cookie to include an opt-out option of “DNS” (do not sell). Updated the consent change event specifications  to include the CCPA policy and a "do not sell" tag list attribute. Event Logging now applies to all consent management workflows. Tag categories can be renamed within GDPR Consent Preferences. Changed the default consent cookie expiration to 12 months for GDPR. The Tealium Collect tag is now categorized under "Big Data". Added ability to select a profile for event data logging. Links CCPA Consent Manager Setup Guide Learn how to activate, configure, and customize the CCPA Consent Manager banner and popup for your site. Tealium CCPA Webinar Series Learn more about CCPA and it’s newly introduced consumer rights from this Tealium Master Class. Tealium Consent Management See the full offering of consent management features. Frequently Asked Questions We already have a cookie banner, how do we integrate the popup for the CCPA Consent Manager? The CCPA Consent Manager is designed to work with an existing cookie banner. With the popup configured, a JavaScript function that triggers the pop-up is made available in your Universal Tag (utag.js). To integrate the CCPA popup with your banner, add a link with an "on click" action to call the JavaScript function. Learn more: CCPA Consent Manager: JavaScript Functions How does Tealium use cookies? See the article How Tealium Uses Cookies. We are already GDPR compliant. Does that mean we are also CCPA compliant? No. Being GDPR compliant does not mean that you are CCPA compliant. You need to make changes to your privacy policy, include a “Do Not Sell My Personal Information” link on your home page and footer, establish methods for requests for access, change, and erasure of data, establish a method for verification of the identity of the person making a data-related request, and establish a method for obtaining prior consent by minors before selling their personal data. ... View more

Tealium offers pre-built plugins for several popular CMS platforms. A Tealium CMS plugin installs the Tealium Universal Tag (utag.js) and Universal Data Object (utag_data) on every page of the site with just a few clicks and configuration settings. In this article: How It Works A CMS plugin implements the following parts of a successful Tealium installation: Code Placement - Correct placement of the Universal Tag (utag.js) on all pages of the site. Data Layer - Dynamically and accurately generate a data layer object using built-in CMS page meta data. Configuration Options - Provide configuration settings such as account name, profile name, and environment. Explore the Tealium Wordpress Plugin Setup Guide for an example. Data Layer Bundles A data layer bundle in Tealium iQ Tag Management is the list of corresponding variables generated by the CMS plugin. For example, an e-commerce CMS will automatically populate product and order variables in the data layer. A Tealium user can quickly add these variables to their account configuration by adding the related bundle. Learn more about CMS data layer bundles. List of Tealium CMS Plugins A Tealium plugin is available for the following CMS vendors: CMS Links Adobe CQ Github Adobe Experience Manager Github Drupal Drupal Module Episerver Github Hybris Github IBM Websphere Github Magento 1.x Github Magento 2.x Github, Magento Marketplace Salesforce Commerce Cloud (Demandware) Github Shopify Github Sitecore Github Unity Github Wordpress Github, WP Plugin Page   ... View more

A new version of the Facebook Pixel tag is now more tightly integrated with the Facebook Server-Side Events connector. The upgraded tag has several improvements to the client-side configuration options, including an option to integrate with the Facebook Server-Side API for Web. The tag is available now in the Tealium Tag Marketplace and the connector has been released from experiments and is now available in the Tealium Connector Marketplace. What's New The following improvements make it easier than ever to add the Facebook Pixel tag to your account: Simpler Configuration The most common tag configuration options are now set by default, making the setup as simple as entering your pixel ID. Tealium Collect Integration The new tag is optimized to work with the Tealium Collect tag to ensure consistent server-side data delivery. Server-Side Events The new tag integrates with the most recent capabilities in server-side tracking. Customers of Tealium EventStream can now integrate the Facebook Pixel tag with the Facebook Server-Side Events connector for better tracking coverage. How It Works The new Facebook Pixel tag is optimized for the most common use cases to make it as easy as possible set up. For example, p urchase tracking occurs automatically when an order ID is detected in the data layer.  The tag now has only three configuration options, but the mapping toolbox is available for advanced use cases.  To support the server-side integration, the tag can now generate unique event IDs for each event tracked. These event IDs can be mapped in the connector to synchronize the web events and server-side events. This feature requires an active Tealium Collect tag. The tag emits new event attributes using the following naming convention: fb_event_id_<Facebook Event> For example: fb_event_id_Purchase or fb_event_id_PageView Benefits of the Server-Side API Improved Data Quality Browsers can be susceptible to issues like poor network connectivity, ad-blockers or user error. This can result in loss of signals or passing of inaccurate signals to advertising partners like Facebook. Server-side data is authenticated, more accurate and has stronger checks to ensure data is in a usable format for Facebook's systems. Unlock Additional Signals  While Facebook pixel is a powerful tool to harness web signals, many interactions and transactions occur outside of your website or app. You likely have an untapped repository of conversion data available on your servers, such as qualified leads, recurring payments and subscription sign-ups. The API enables you to share these signals and unlock them for use in Facebook's solutions. Prepare for Industry Changes As the regulatory and privacy landscape evolves, data-driven marketers are exploring alternatives to browser-based tools. Implementing Facebook's Server-side API today helps enable consistent marketing performance regardless of industry changes. Related Documentation Tealium Customer Data Hub Facebook Server-Side Events Connector Facebook Pixel Facebook Pixel (Legacy) Facebook About Server-Side API for Web About Deduplication for Facebook Pixel and Server-Side API for Web Events  ... View more

This article describes how to set up the Facebook Pixel tag in your Tealium iQ Tag Management account. For information about the legacy Facebook Pixel, see Facebook Pixel Setup Guide (Legacy). In this article: Table of Contents Placeholder How it Works Tag Overview Purchase tracking occurs automatically when an order ID is populated. You may enter a comma-separated list of Pixel IDs in the Pixel ID field. To make Facebook Pixel Event IDs available as server-side attributes, set Generate Event ID to true and use the latest version of the Tealium Collect tag. The template automatically attempts to calculate the num_items value if a product quantity array is present. Use mapping to: Toggle trackSingle (true by default) Toggle disablePushState (false by default) Dynamically set the tag configurations Override the E-Commerce extension values Supports these E-Commerce extension parameters: Order ID Sub Total Currency List of Product IDs List of Product Categories List of Product Prices List of Product Quantities List of Product Names Server-Side API for Web To support the Facebook Server-Side API for Web, the tag generates a unique event ID for each event tracked and send it to Tealium EventStream for use in the Facebook Server-Side Events connector. The event ID may be mapped in the connector to synchronize the web-based on server-based integrations. This feature requires an active Tealium Collect tag. The tag emits new event attributes using the following naming convention: fb_event_id_<Facebook Event> For example: fb_event_id_Purchase or fb_event_id_PageView See the Facebook Server-Side Events Connector Setup Guide. Tag Configuration First, go to the Tealium Tag Marketplace and add the Facebook Pixel tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Pixel ID Your Facebook Pixel ID. The Pixel ID appears as a long series of numbers in the code snippet. You may enter multiple Pixel IDs using a comma-separated list, without spaces. Example: fbq("init", "12345678901234"); Advanced Matching Enable and pass data to the Facebook Advanced Matching service. Example: fbq("init", "12345678901234", {em:"6dd8b7d7..."}); Generate Event ID Automatically generate an event ID for every Facebook tracking event. Event ID attributes follow the naming convention: fb_event_id_<Facebook Event> Example: fb_event_id_Purchase : "028b2ade7478..." Event Mapping Facebook Pixel events are configured through data mappings by selecting a variable that maps to an event and entering a trigger.  The trigger initiates the event when the variable is equal to a specific value, as demonstrated in the following use case. Use Case: Purchase Event To set up a purchase event: Select  tealium_event from the variable dropdown and click Select a Destination. In the Category section, select Events. Set the When mapped variable equals field to  Purchase , which is the value tealium_event must equal to trigger a purchase. In the Trigger event dropdown, select Purchase , which is the event that is triggered when tealium_event equals purchase. If additional data needs to be sent with the purchase event that is not already covered by the built-in E-Commerce extension mappings, use Custom Parameters to map additional purchase data. The following example passes the product brand with the purchase event: Select   product_brand  from the variable dropdown and click Select a Destination. In the Category section, select Event specific Parameters. Set the Destination field to  the name brand for the Custom Parameter. In the For event dropdown, select the event Purchase which the Custom Parameter collects with. Test the mappings by using the Facebook Pixel Helper or your browser’s Developer Tools.   Use the Network Panel and filtering for Facebook to display all the network requests containing Facebook as a keyword. Confirm the purchase event was successful by looking at the name of the request. Open the request and scroll down to the Query String Parameters to see the values of the the data mappings that were configured: purchase , product_id , and product_brand  . Data Mappings Data mappings follow a hierarchy in which specific mappings, such as Event-Specific Parameters, take precedence over more general mappings. For example, if you map a variable to the Currency destination in the Standard Tracking Parameters tab and to the Currency destination for the ViewContent event, the ViewContent mapping takes precedence over the general mapping, but only for the ViewContent event. For all other events, the Standard Tracking mapping is used. Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see Data Mappings. The available categories are: Tag Configurations Destination Variable Type Description Pixel ID pixel_id [String] Your Facebook Pixel ID. The Pixel ID appears as a long series of numbers in the code snippet. You may enter multiple Pixel IDs using a comma-separated list, without spaces. Example: fbq("init", "12345678901234"); Toggle Automatic PageView auto_page_view Boolean [true/false] Toggle to enable or disable automatic PageView tracking. Toggles whether or not to automatically trigger a PageView event with a page load. Default value is true. Toggle Advanced Matching advanced_matching Boolean [true/false] Toggle to enable or disable the collection of Advanced Matching data. Toggles whether or not to capture and send advanced matching data. Default value is true. Generate Event IDs generate_event_id Boolean [true/false] Toggle to enable or disable the generation of Event IDs for each Facebook tracking event. Toggles whether or not a unique Event ID is generated for each Facebook tracking event. Requires the most recent version of the utag.js file in order to generate the IDs. Default value is false. Automatically Calculate Number of Items calc_items Boolean [true/false] Toggle to control whether or not to automatically determine the number of items for an event. Uses the data mapped to Product Quantities to determine the number. Toggles whether or not to automatically calculate the number of items in a Facebook tracking event based on the number of items in the product_quantity array. Default value is true. Toggle trackSingle Usage track_single Boolean [true/false] Enable or disable the use of trackSingle for Facebook tracking events. Toggles whether or not to use trackSingle for Facebook Pixel tracking calls. Default value is true. If set to false, the value track is used for all Facebook tracking calls. Toggle disablePushState Usage disablePushState Boolean [true/false] Toggles the disablePushState setting. Toggle to enable or disable the disablePushState option which controls whether or not to prevent the triggering of multiple PageViews on the same page (for Single Page Apps). Default value is false. E-Commerce Since the Facebook Pixel tag is e-commerce enabled, it automatically uses the default E-Commerce Extension mappings. Manually mapping in this category is not needed unless you want to override any extension mappings or your desired e-commerce variable is not offered in the extension. Destination Variable Description E-Commerce Extension Variable Order ID order_id Unique identifier assigned to the final order. Overrides _corder . _corder Sub Total sub_total Sub total amount of the final order. Overrides _csubtotal . _csubtotal Currency order_currency Currency used in the payment. Overrides _ccurrency . _ccurrency List of Product IDs product_id Unique identifier of each product in the product array. Overrides _cprod . _cprod List of Product Names product_name Name of each product in the product array. Overrides _cprodname . _cprodname List of Product Quantities product_quantity Quantity of products in the product array. Overrides _cquan . _cquan List of Categories product_category Category of each product in the product array. Overrides _ccat . _ccat List of Prices product_unit_price Unit price of each product in the product array. Overrides _cprice . _cprice Standard Tracking Parameters Destination Variable Type Description Currency currency [String] The currency for the value of the event. Content Category content_category [Array,String] Category of the page/product. Content Name content_name [Array,String] Name of the page/product Content IDs content_ids [Array] The product IDs or SKUs associated with the event Content Type content_type [String] The product type associated with the content IDs, which matches the types given in your Facebook product feed. In most cases this is either product or product_group . Dynamic Ads have other legitimate values for each business vertical. Contents contents [Array,JSON Object] An array of JSON objects that contains the quantity and the content IDs. Predicted Lifetime Value predicted_ltv [String] Predicted lifetime value of a subscriber as defined by the advertiser. Expressed as an exact value Search String search_string [String] Used with the Search event. The string entered by the visitor for the search. Status status [String] Used with the completeRegistration event. The status of the registration. Number of Items num_items [Number] The number of items for the event. The number of items is automatically calculated based on the values in the data mapped for quantity. Disable the automatic calculation by setting calc_items ( u.data.calc_items ) to false, using data mapping or an extension. Value value [String] The value of a user performing this event to the business. Content Type Set the content_type parameter by mapping to it directly in either the Standard Tracking Parameters tab, or the Event-specific Parameter mappings. The Content Type tab allows you to conditionally set the content_type parameter to any of the following supported values: destination flight home_listing hotel product product_group vehicle If the mapped variable equals the value you enter in the field, then the value is set to the type you select from the drop-down list. In most cases, the values product or product_group are used, and that value must match the content_type you specify for the products in your product feed uploaded to Facebook. Other values are most commonly used with Dynamic Ads. Variable Description destination Destination. flight Flight. home_listing Home Listing. hotel Hotel. product Product. product_group Product Group. vehicle Vehicle. Events Event Name Description AddPaymentInfo Add payment information. AddToCart Add to cart. AddToWishlist Add to wish list. CompleteRegistration Complete registration. Contact Contact. CustomizeProduct Customize product. Donate Donate. FindLocation Find location. InitiateCheckout Initiate checkout. Lead Lead. PageView Page view. Purchase Purchase. Schedule Schedule. Search Search. StartTrial Start trial. SubmitApplication Submit application. Subscribe Subscribe. ViewContent View content. Custom Enter the name of your custom event in the field provided. Event-specific Parameters In order to map a parameter for a specific event only, first select the name of the parameter from the drop-down list, Enter the name of the parameter you want to set and then select the name of the event for which you want to set that parameter. If you are mapping a parameter for a custom event, you must enter the name of the custom event in the field that appears. If you want to enter a custom parameter name, select the Custom option from the parameter drop-down list and enter the name of the custom parameter in the field that displays. If you want to specify a custom event for the event-specific mapping to occur, select the Custom option from the events drop-down list and enter the name of the custom event in the field that displays. Variable Description AddPaymentInfo Add payment information. AddToCart Add to cart. AddToWishlist Add to wish list. CompleteRegistration Complete registration. Contact Contact. CustomizeProduct Customize product. Donate Donate. FindLocation Find location. InitiateCheckout Initiate checkout. Lead Lead. PageView Page view. Purchase Purchase. Schedule Schedule. Search Search. StartTrial Start trial. SubmitApplication Submit application. Subscribe Subscribe. ViewContent View content. Custom Custom. Automotive Parameters Destination Variable Description Body Style body_style Body style. Condition of Vehicle condition_of_vehicle Condition of vehicle. Country country Country. Drivetrain drivetrain Drive train. Exterior Color exterior_color Exterior color. Fuel Type fuel_type Fuel type. Interior Color interior_color Interior color. Lead Type lead_type Lead type. Make make Make. Model model Model. Postal Code postal_code Postal code. Preferred Price Range preferred_price_range Array. Preferred price range. Must be an array that contains the minimum and maximum preferred prices. Price price Price. Registration Type registration_type Registration type. Search Type search_type Search type. State of Vehicle state_of_vehicle State of vehicle. Transmission transmission Transmission. Trim trim Trim. ViewContent Type viewcontent_type View content type. VIN vin VIN number Year year Year. Destination Parameters Variable Description city City. country Country. num_adults Number of adults. num_children Number of children. region Region. suggested_destinations Array. Suggested destinations. Must be an array of the suggested destinations. travel_start Travel start date. travel_end Travel end date. Flight Parameters Variable >Description departing_arrival_date Departing arrival date. departing_departure_date Departing departure date. destination_ids Destination IDs. num_adults Number of adults. num_children Number of children. num_infants Number of infants. preferred_num_stops Preferred number of stops. price Price. returning_arrival_date Returning arrival date. returning_departure_date Returning departure date. travel_class Travel class. user_score User score. Hotel Parameters Variable Description checkin_date Check-in date. checkout_date Check-out date. city City. country Country. destination_ids Array. Destination IDs. Must be an array that contains Destination IDs. hotel_score Hotel score. num_adults Number of adults. num_children Number of children. preferred_neighborhoods Array. Preferred neighborhoods. preferred_price_range Array. Preferred price range. preferred_star_ratings Preferred star ratings. region Region. user_score User score. Movie Parameters Variable Description movieref Movie referrer. Real Estate Parameters Variable Description availability Availability. city City. country Country. lease_start_date Lease start date. lease_end_date Lease end date. listing_type Listing type. neighborhood Neighborhood. preferred_baths_range Array. Preferred baths range. preferred_beds_range Array. Preferred beds range. preferred_price_range Array. Preferred price range. property_type Property type. region Region. Vendor Documentation See the following vendor documentation for more information: Facebook Pixel Developer Documentation. Migrating from Deprecated Pixels Reference: Standard and Custom Events The Facebook Pixel FAQ Advertiser Help Center: Using Facebook Pixel with Tealium Conversion Tracking with the Pixel ... View more

We are excited to announce the availability of user permissions for the server-side products. This new feature allows account owners to manage server-side user permissions separately from the user permissions that are controlled in Tealium iQ Tag Management. How it Works Server-side user permissions creates a separation of access between the Tealium client-side interface and the server-side interface. This allows account administrators to grant access to users only for the areas that they intend to work on. New users for the entire account are still added in Tealium iQ Tag Management. Once added, the new users appear in the server-side user permissions list where server-side access is granted by profile. Server-Side Permission Roles Server-side access is controlled using predefined permission roles. For each profile in the account, users are assigned a permission role to determine their access level. The following table describes the four (4) available server-side permission roles: Permission Role Description No Access (default) The No Access permission role does not grant any access to the server-side profile. If the user attempts to access the server-side, their profile is blocked and an "Access Denied" message displays. Reader The Reader permission grants read-only access to the server-side profile. A user in this role can browse the profile configuration, but the Save/Publish button is disabled. Users with this role cannot save any changes. Editor The Editor permission grants edit and save access to the server-side profile. Users with this role can also access and edit settings from the Profile Admin > Settings menu. Publisher The Publisher permission grants the same access as the Editor role, with the addition of the ability to publish the profile. User Migration from iQ Tag Management Prior to this release, access to the server-side products was managed from iQ Tag Management. From there, a user with permission to publish to the production (prod) environment had full save and publish permissions in the corresponding server-side products. In order not to disrupt user access to the server-side, a migration policy was applied to map client-side user permissions to server-side permissions. With this release, your server-side account is pre-populated with users from your corresponding iQ Tag Management account. During migration your client-side users were placed into the following server-side permission groups: Client-Side Permissions Migrated Server-Side Permissions Manage Account and Manage Users Administrator Has full access to the account, including the ability to edit server-side user permissions and add users. Cannot be edited. Publish to Prod Publisher Has the ability to save and publish. Any Reader All other users will have read access. Admin Users Admins of the server-side interface are the only users that have the ability to change the permissions of server-side users. None of the server-side permission roles grant this ability. To be an admin on the server-side, you must have the Manage Account permission in the client-side interface. Only the Manage Users permission grants the ability to add users to the account. To learn more about managing user permission in Tealium iQ Tag Management, see Managing User Permissions in iQ Tag Management. Get Started! For step-by-step instruction on how to get started, go to Managing Server-Side Permissions. ... View more

The goal of this solution is to set the Tealium TAPID as a first-party cookie using a reverse proxy. The TAPID cookie is normally set as a third-party cookie, but due to new restrictions in browsers, these cookies are becoming more difficult to rely on. Using a reverse proxy is one way to have requests to Tealium Collect directed through your own subdomain to ensure that the resulting cookie remains in the first-party context. Related Topics How Tealium Uses Cookies Chrome’s SameSite Feature Updates Could Be More Significant than Apple’s ITP  What you can do about ITP and Third-Party Cookie Blocking In this article: How It Works If you're using the Tealium Collect tag to collect data in Tealium EventStream or AudienceStream then you might be familiar with the endpoint  collect.tealiumiq.com . This endpoint that collects all incoming requests to the Tealium Customer Data Hub and it sets a third-party cookie called TAPID that is used for identity resolution in AudienceStream. The cookie is set in the domain .tealiumiq.com . If you want the TAPID to be set as a first-party cookie, then requests to Tealium Collect must use an endpoint that matches your domain. One way to accomplish this is by using a reverse proxy. A reverse proxy solution requires the following: Reverse Proxy: a server that can run a reverse proxy configuration. Tealium Collect: an instance of the Tealium Collect tag in Tealium iQ Tag Management or the Collect module in a Tealium for Mobile installation. Reverse Proxy A reverse proxy allows you to effectively serve requests from your domain while continuing to benefit from the enterprise scale of the Tealium Customer Data Hub. Instead of sending requests to collect.tealiumiq.com , you would send them to an endpoint of your own, such as collect.example.com . A reverse proxy can be implemented in several ways, but they all require the following: A web server that can handle the network traffic generated by your Tealium installations. DNS entry for your new endpoint, such as collect.example.com SSL Certificate for the new subdomain Region Hostnames If your data collection is restricted to a specific geographic region, then your reverse proxy configuration should direct traffic to one of the following regional endpoints: REGION COLLECT HOSTNAME Global collect.tealiumiq.com Germany collect-eu-central-1.tealiumiq.com Ireland collect-eu-west-1.tealiumiq.com Tokyo collect-ap-northeast-1.tealiumiq.com Sydney collect-ap-southeast-2.tealiumiq.com Tealium Collect After your new endpoint and reverse proxy is in place, you must change the URL that Tealium Collect uses. The default endpoint has your Tealium account and profile in the pathname. Your new endpoint will be the same except for the hostname. Default Endpoint: https://collect.tealiumiq.com/ACCOUNT/PROFILE/2/i.gif Reverse Proxy Endpoint: https://collect.example.com/ACCOUNT/PROFILE/2/i.gif Tealium Collect Tag Your new reverse proxy endpoint must be set in the Tealium Collect configuration. Set the Server field to your new URL: References: Tealium for Android: Collect URL Override Tealium for iOS/Swift: Collect URL Override Tealium Collect Tag Setup Guide Example: Nginx Nginx is a light-weight server that is ideal to use as a reverse proxy. It can handle large amounts of network traffic and, with a simple configuration, can pass those requests onto the Tealium endpoints for processing. This solution would take all traffic coming to your new endpoint (collect.example.com) and forward it to the Tealium collect endpoint (collect*.tealiumiq.com). It will also set header cookies in your domain, ensuring that they remain first-party.  Sample Nginx server block configuration: server { listen 443 ssl; # TODO: Your subdomain server_name collect.example.com; ssl on; # TODO: Your SSL certificates ssl_certificate <path_to_fullchain>.pem; ssl_certificate_key <path_to_privatekey>.pem; location / { # TODO: Only change this if you use a regional Tealium Collect hostname proxy_pass https://collect.tealiumiq.com; proxy_set_header X-Real-IP $remote_addr; proxy_set_header HOST $http_host; # TODO: Your cookie domain for Set-Cookie header proxy_cookie_domain $http_host example.com; } } ... View more

The CCPA Consent Manager makes it easy to allow users to opt-out of the sale of personal information and set preferences for the sale of personal information. This tool adds the ability to add a privacy banner and popup to your site to inform your visitors about your sale of personal information policy and to provide opt-out options.  The CCPA Consent Manager can be fully  customized to match your site requirements and it supports translated content for your global visitors. Learn about more features of Tealium Consent Management. In this article: Table of Contents Placeholder How It Works The CCPA Consent Manager notifies your users of your policy for processing personal information and allows them to opt-out of the sale of their personal information or control how their personal information is sold. This solution can be deployed to your site either as a privacy banner and popup or just as a popup to integrate with your existing banner.  The banner informs your users about your policy and provides a link to your "Do Not Sell My Information" page required by CCPA. The popup is triggered from the banner and allows a visitor to opt-out of the sale of personal information or set preferences for the sale of their personal information.  This feature is  integrated with your Tealium iQ Tag Management account to make it easy to configure and categorize vendor tags that might be governed by CCPA.  The tags that you identify as selling information can be categorized as “Dot Not Sell” and presented to your users in the popup.  Visitor Experience Once deployed to your website using the Universal Tag (utag.js), the CCPA Consent Manager operates automatically – no additional coding is needed for it to function. The  banner and popup is displayed based on the configured load rule and the presence of a "do not sell" cookie. When the cookie is not set, the CCPA Consent Manager is triggered automatically on pages that match the load rule. Once a preference is set, the cookie is created and subsequent page views will not trigger the banner or popup. The CCPA Consent Manager can be displayed programmatically using the JavaScript helper functions. Features The CCPA Consent Manager offers the following features: Display Templates Customizable Style and Layout Multi-Language Support Configurable Display Condition Global Settings for Enterprise Rollout Steps The CCPA Consent Manager is set up using the following screens: User Experience Select how it will display on your site: either as a banner and popup or just a popup. We recommend selecting the banner and popup as the most complete solution. However, if you already display a cookie banner on your site, the popup option is best.  Content Use this screen to enter the message displayed to your customers on the banner and popup, add multiple language translations, and provide your company's logo URL and privacy policy link. Customization Customize the design and layout of your prompt by editing the CSS, HTML, and JavaScript used to display your prompt. Display Rule Use your data layer to create a load rule that determines when the banner should be displayed. This feature does not require additional code on your site. All of the configuration is bundled with your existing installation of the Universal Tag (utag.js). Once you activate and configure the CCPA Consent Manager the changes are included in your next publish. Global Parameters The parameters used in the CCPA Consent Manager can be set globally at the account level. This allows you to set the titles, messages, and labels once and have each profile inherit those values. To learn more, see Managing Global Consent Content Parameters. Getting Started Use the following steps to begin setting up the CCPA Consent Manager: In the left sidebar, go to Client-Side Tools > Consent Management. If the CCPA banner and popup is already set up, you can toggle it on or off from this screen. In the CCPA Consent Manager section, click Get Started to launch the configuration modal. User Experience To get started, choose the user experience option that matches your site: Banner and Popup (Recommended) This option adds a cookie banner to be displayed on the page. You set the message and links and the consent manager takes care of the rest, displaying the banner on the page based on your configured settings. The banner contains a link that opens the popup where users set their "Do Not Sell" preferences. Popup Only Select this option if you already display a cookie banner on your site. This option makes the popup available using a JavaScript method that you add to a link in your banner. Content On the Content screen, customize the text displayed in the banner and popup, add languages for translated content, define custom parameters, and show a preview of the banner and popup. Content Parameters The Consent Manager uses parameters to construct the final text that displays on your site. It uses templates so that custom content can be easily added. Parameters are referenced in the templates in the format  {{parameter_name}} . The standard built-in content parameters are: Banner Parameters Title {{title}} The main heading of the Banner or Pop-up. Message {{message}} Your message to customers to inform them about your tracking intentions and links to other resources such as a privacy policy or contact form. Do Not Sell Details Button {{ details_button }} The label on the submission button. Continue to Site Button {{ continue_button }} URL of the logo to display. Privacy Policy URL {{ privacy_policy_url }} The URL to your Do Not Sell page. Privacy Policy Text {{ privacy_policy_text }} The text of the link to your Do Not Sell page. Cookie Statement URL   {{ cookie_statement_url }} The URL to your cookie policy page. Cookie Statement Text    {{ cookie_statement_text }} The text of the link to your cookie policy page. Popup Parameters Title {{title}} The main heading of the popup. Message {{message}} Your message to customers to inform them about your tracking intentions. Do Not Sell Description    {{do_not_sell_description}} Description of what opt-out of selling of personal information means. Confirmation Button   {{confirmation_button}} The label on the submission button. Company Logo URL    {{ company_logo_url }} The URL of the logo to display. Do Not Sell Description    {{do_not_sell_description}} Description of what opt-out of selling of personal information means. To edit the content of the standard parameters, modify the text fields and click Finish. Sample HTML code with parameters: < div class ="privacy_prompt consent_doNotSell" > < div class ="privacy_prompt_content" > < h1 > {{title}} </ h1 > < img src ="{{company_logo_url}}" class ="logo" > < p > {{message}} </ p > < input id ='consent_doNotSell_checkbox' type ='checkbox' /> {{do_not_sell_description}} </ div > < div class ="privacy_prompt_footer" > < div class ="button right" id ="consent_doNotSell_submit" > {{confirmation_button}} </ div > </ div > < div class ="close_btn_thick" ></ div > </ div > Custom Parameters Custom parameters can be added to further customize the Consent Manager. These parameters can be referenced within the standard parameters or in the templates. Best Practice: Avoid putting translatable text directly in the HTML or JavaScript. Instead, construct the code with {{parameters}} and define the values using custom parameters. To add a custom parameter: Scroll down to the Custom Parameters section and click + Add Parameter. The Custom Parameter dialog displays. Enter a name for the parameter. Click Apply. The new custom parameter displays in the list. Enter a value for the new parameter. This value will be substituted where the parameter is referenced. Click Finish. Languages The Consent Manager is built with automatic language detection. The banner and popup detects the language setting in the browser (two-character language code) and presents the corresponding version if that language has been configured. The prompt is configured in English (en) by default. Language Overrides You can optionally override the language with a value provided in the data layer if it is in the ISO format. To override a language, use a preloader extension to set the gdprDLRef override: window.utag_cfg_ovrd = window.utag_cfg_ovrd || {}; window.utag_cfg_ovrd.gdprDLRef = utag_data.site_language; Adding a Language To add a language: In the Language side panel, click + Add. The Add Language dialog displays. Select the desired language and click Apply. The new language displays in the side panel. Click the new language to configure the content. Enter the translated values in the standard parameter boxes (Title, Message, and Confirmation Button). Click Finish. Setting the Default Language The default language is used to display the Consent Manager when the user's detected browser language does not have a matching language configured. To set a default language: Check the Make Default Language box located in the language title bar. Click Preview to view your language configuration. Customization (CSS, HTML, JavaScript) On the Customization screen, you will see the code behind the banner and popup – the CSS, HTML, and JavaScript. This code can be edited to adjust the look and design of the banner and popup to match your website and customer needs. The JavaScript code is minified before it is published into the utag.js file. If the minification process fails for any reason (such as a syntax error), the publish process halts and returns a warning message in Tealium iQ. Upon successful publish, when utag.js executes on the page, the Consent Manager JavaScript code is injected into the <head> of the page. Affected Tags On the   Affected Tags   screen you select the tags that are governed by your Do Not Sell policy--that is, tags that will be blocked if the user opts out of Do Not Sell.  To select tags affected by your Do Not Sell policy: Select a category from the sidebar. The list of tags displays in the main panel. Tick the checkbox next to each affected tag or tick the checkbox at the top to select all tags displayed. Click   Finish. Display Rule On the Display Rule screen, you will select the load rule to determine when to load the banner and popup and display it to customers. You can select an existing load rule or create one to satisfy your legal criteria. Consent Cookie The prompt relies on a cookie named CONSENTMGR . The presence of this cookie and the values it contains will determine the behavior of the prompt and reflect the state of the visitor's choice. The key/value pairs are delimited by the pipe ("|") character. The CONSENTMGR cookie stores the following key/value pairs related to the Do Not Sell Prompt: dns – a boolean value that reflects the Do Not Sell choice of the visitor:   true – the visitor opted-in to Do Not Sell   false –the visitor opted-out of Do Not Sell ts – the timestamp of the last state change Example value of the CONSENTMGR cookie: ts:1525369619|dns:true This cookie has a default expiry of 13 months from the time it is set or changed. JavaScript Helper Functions Once enabled and published, the CCPA banner and popup introduces JavaScript utility functions into the utag namespace to allow you to integrate additional functionality. The namespace utag.gdpr contains all of the consent management utility functions. utag.gdpr.showDoNotSellBanner() Displays the CCPA banner. By default, this function is called when the display rule evaluates to true . Optionally set the language as a parameter when calling the function. This will override all other language detection logic. utag.gdpr.showDoNotSellBanner("EN"); utag.gdpr.showDoNotSellPrompt() Displays the CCPA popup. I f you are not using the banner, integrate t his function into your site banner to provide visitors a way to change their consent setting. Optionally set the language as a parameter when calling the function. This will override all other language detection logic. Example: <a href="javascript&colon; utag.gdpr.showDoNotSellPrompt('EN')">Change Consent</a> utag.gdpr.dns.getDnsState() Returns the value of the dns consent cookie. Example: utag.gdpr.dns.getDnsState() true utag.gdpr.dns.setDnsState() Set the value of the dns consent cookie. Recognized values: true, false, 1, 0, "true", "false". Example: utag.gdpr.dns.setDnsState(true); utag.gdpr.getCookieValues() Returns an object of key/value pairs from the CONSENTMGR cookie, accessible in the data layer object as  utag.data['cp.CONSENTMGR'] . Example of consent declined: utag.gdpr.getCookieValues() { ts: "1525369619", consent: "true", dns: "false" }   ... View more