As you start to work in the Customer Data Hub, the Save/Publish button will turn green indicating that there are unsaved changes. As you make progress in adding configuration to your profile it's best to save your changes periodically to minimize the risk of losing your work.

Table of Contents Placeholder

How to Save Changes

To save, click the Save/Publish button, determine whether you want to "Save" in the current version or "Save As" into a new version being sure to create a new title, then leave a description of the changes, uncheck the "Publish" checkbox, and click the "OK" button.

When selecting Save As, the title must be different from any previous version's title. If the title is not changed you will receive this publish error:


How to Publish Changes

To Publish, follow the steps above but be sure to leave the "Publish" checkbox checked.


A publish is necessary if you are making changes to rules or attributes and need the update to be applied in production.

How to Test Before Publishing

Customer Data Hub does not have a dev and qa environment, so testing your changes before releasing to production requires an extra step.  With the power of badges and rules you can easily restrict new functionality to a "Test User" which can be identified any number of ways. 

How to Configure a Badge for Testing

For this example, we will use a badge attribute called “Test User”.  This badge uses a rule that evaluates on “Any Event” when a query string parameter contains “tealium_test=true”.  This badge uses a second rule to indicate that it should be unassigned from a visitor when the query string parameter contains “tealium_test=false”. 

image 1 - test user badge rules.png

The badge and rule condition can be customized, but they should be unique so that regular site visitors do not get this badge applied to them.

How to Configure an Audience for Testing

If you are looking to test a specific Audience, you can simply add a condition that the “Test User” badge has to be assigned.  This will prevent all other users from joining that audience and will allow you to test any connector actions that are tied to that specific audience.

image 2 - test with  aud.png 

How to Configure an Attribute for Testing

To test a specific attribute, for example a String, you can include a specific rule that the “Test User” badge is assigned.  

image 4 - added to trait, independant.png

How to Test

When starting your Trace session, you must satisfy the test condition used in your test configuration. In this example, you would navigate to your site and append the query string parameter and value used in the rule.  

For example:

Once your Trace starts, you should then see your “Test User” badge assigned. 

image 6 - test user badge is assigned.png 

Testing this way before publishing to production will allow you to do be confident in your configuration logic, help reduce errors, and increase the accuracy of your strategy. 


Concurrent Users

Currently it is not possible for users to see if another user is concurrently editing, saving, or publishing at the same time. Please be sure to view the concurrent user status in Tealium iQ to verify.

Integration with Tealium iQ

  • Customer Data Hub can make use of the variables from Tealium iQ. To do so the Tealium iQ profile must be published to the Prod environment to make these variables appear as attributes within Customer Data Hub.
  • Tealium iQ can make use of AudienceStream attributes. In order to do so, AudienceStream must be published so that the attributes appear within Tealium iQ. These attributes can then be used like any other data layer variables.
  • By default, the current TiQ profile will attempt to read attributes from the corresponding AudienceStream profile. For example, the Tealium iQ profile tealium/main will read from the AudienceStream profile tealium/main. However, there will be times when Tealium iQ needs to read Attributes from another AudienceStream profile. If this is the case, in TiQ click the "Save/Publish" button, when the modal appears click the "Configure Publish Settings" button, when the new modal appears scroll to the "Implementation" section and select the appropriate profile from the "Data Layer Enrichment Profile" drop-down.DLE_Profile.png