Skip to main content
All CollectionsOther Articles
Tealium ObservePoint Trigger
Tealium ObservePoint Trigger
Luiza Gircoveanu avatar
Written by Luiza Gircoveanu
Updated over a week ago

This integration allows a group of ObservePoint Audits and Journeys to be automatically run when you publish to any Tealium profile. This is available to any organization that is a mutual customer of ObservePoint and Tealium.

Note: This integration is configured within Tealium with the help of your Customer Success rep at Tealium.

The main use of this is to test changes at scale quickly and verify your analytics are still functioning after the release of updates. For example, if you wish to test the data quality on 1000 pages, your e-commerce funnel, and also the customer registration funnel automatically each time you publish a change to your Tealium QA profile.

How to Set up the Trigger

First, you'll want to set up your ObservePoint Audits and Journeys to validate in the correct places. If you don't already have Audits and Journeys checking what you need to check, set up new ones, and make sure to add any Rules for your most important pieces. That way you'll get an alert on those tags or variables. You'll want to add yourself to the Notifications of these Audits and Journeys or set up an integration to get alerts. Then you'll need to grab the IDs of those Audits and Journeys. This can be found in the URL of the Audits and Journeys. See below for an example:

You'll also need to grab your API Key, to get that go to your profile by clicking the Profile icon and selecting Profile:

Then you'll be able to copy your API Key to the clipboard. If your revoke the API key any place where it is set will no longer work so be careful not to revoke and set new unless that is your intention!

Once you have those IDs and API Key, you'll need to contact your CSM and ask for the 'Tealium ObservePoint Trigger' to be set up. You'll want to send them the IDs, and the API Key, and let them know to which Tealium profile you want this applied.

It is recommended that you duplicate this for your QA and PROD Tealium environments, giving you a 'double gateway' protecting your data quality.

Did this answer your question?