Adds the Tealium tag and creates a data object from post data.
Features
Allows users to easily add the Tealium tag without editing any template files.
A data layer is added to your WordPress website containing:
- Site name
- Site description
- Post ID
- Post date
- Post categories
- Post tags
- All post meta data, including custom fields
- Search terms
- Number of search results
- Current user role
About Tealium
Tealium is the leader in enterprise tag management, serving some of the most demanding customers in the world. Tealium’s web-based services make it easy for digital marketers to deploy and manage their third-party vendor tags, and then correlate the data those tags generate into an actionable source. Using Tealium, organizations can streamline their digital marketing operations, improve web site performance, cut costs, and power their big data initiatives. The company differentiates itself through ease of use, scale and performance, and fanatical customer support. Select clients include Petco, A+E Networks, Fox Networks Group, Urban Outfitters, and many more! More than ever, today’s marketers are turning to digital solutions to improve efficiency and results.
Tags – commonly known as tracking pixels – are becoming the data collection mechanism of choice, leaving marketers reliant on them to gather the right data about visitor activity and take action to improve their experience. But the process of deploying and managing vendor tags can be a nightmare for marketers, due to the technical nature associated with tagging, heavy costs, impact on site performance, and the dependence of IT resources to make changes. Tealium puts digital marketers in control of their online solutions, making it easy to add, edit, or remove any vendor without requesting assistance from IT. In addition, Tealium provides a rich source of all of an organization’s digital data to help marketers improve the effectiveness of their customer acquisition campaigns.
Screenshots
The Tealium plugin allows your Tealium tag to be added straight to your site from your WordPress dashboard.
A data object is added to your site containing basic post or page data.
The plugin also takes categories and tags...
...and rolls them into the data object.
Custom fields and other meta data is also supported.
Many existing WordPress plugins make use of meta data, so your data object should be rich with potential variables.
Advanced settings allow a number of options to be configured and features enabled.
The bulk export feature allows you to quickly import your WordPress variables into Tealium.
What data is currently included in the data object?
- Site name
- Site description
- Post ID
- Post date
- Post categories
- Post tags
- All post meta data, including custom fields
- Search terms
- Number of search results
- Current user role
What are the Tealium tag location options?
- After opening body tag (recommended)
- Header – Before closing head tag
- Footer – Before closing body tag
- Immediately after the opening head tag
Is WooCommerce supported?
WooCommerce stores product information as meta data, so by default your data object will be rich with data on product pages.
Version 1.3 adds basic support for cart contents information in the data object.
Can I add to the data layer dynamically using PHP code?
This can be achieved calling the ‘tealium_addToDataObject’ action from your themes functions.php file or a separate plugin.
For more information see the action examples on GitHub.
Can I automatically switch between Tealium environments on my dev/live website?
This can be achieved by conditionally modifying the Tealium tag code by calling the ‘tealium_tagCode’ action from your themes functions.php file or a separate plugin.
For more information see the action examples on GitHub.
ChangeLog
2.1.16
- Bugfix – Outdated use of join() on admin page impacting PHP 8 users.
- Bugfix – Corrected issue where user roles were assumed to begin at 0.
2.1.15
- Fixed a bug where the iQ tag was inserted into some sitemap plugins. Thanks to peytz.dk for providing the fix.
2.1.14
- Added the role of the current WP user to the data layer. This will allow role-based load rules in TiQ.
2.1.13
- WooCommerce product data updates.
2.1.12
- Add post ID to data layer.
2.1.11
- AMP bug fix. Workaround for a bug in a 3rd-party AMP plugin.
2.1.10
- Add support for alternative utag_data namespace.
- Fix issue with tag injection despite AMP.
2.1.9
- Add translation support and template.
- Move data layer above sync file.
2.1.8
- Fix issues with WooCommerce support.
- Bug fix with key name conversion. Thank you mikeschinkel.
2.1.7
- Improve search result count performance.
2.1.6
- Switch from ‘Data Sources’ to ‘Variables’ to align with TiQ.
- Update the order that notes and aliases appear in bulk export.
2.1.5
- Fix bug where Tealium tag was served on admin pages in more recent versions of WP.
- Make function names less generic. Thank you arippberger.
- Fix admin message styling issue.
- Add more order data for WooCommerce.
2.1.4
- Added the option to exclude WordPress meta data.
2.1.3
- Add tag and category archive specific page types and post titles.
- Added the option to use EU only CDN nodes.
2.1.2
- Change name parameter location to match TiQ update.
2.1.1
- Added pretty printing of JSON object for older versions of PHP.
- Add name parameter on bulk variable export.
2.1
- Added DNS Prefetching option
2.0
- UI makeover.
- Quickly deploy Tealium by providing account/profile/environment details.
- Data source export.
- Cache buster for content editors.
- Support for utag.sync.js file.
- Support for sync/async deployments.
1.5.1
- Fixed opening head tag bug.
1.5
- Added search result count to data object.
- Added actions to allow the data object and Tealium tag to be modified by theme/plugin developers.
- Added top of opening head tag location setting.
- Configurable option for Camel Case or underscore data layer style.
1.4
1.3
- Tag location is now configurable.
- Basic support for WooCommerce cart data.
- Plugin refactored to support translations.
1.2
- Added the ability to exclude keys from the data object.
- The JSON object will now be pretty-printed where PHP support allows.
1.1
- Migrate from capabilities to roles.
1.0
