Tealium Learning Center

Hi @metpdolan  1. You can use Trace.  If you click on the entry in the trace that shows Actions Processed, it gives you all the detail of the variables, templates and then the actual payload sent, see screenshots below. 2. You could use something like webhook.site temporarily, for test users.  There, you can create a temporary endpoint.  If you change your webhook's url to that (again just for test users), it will show you exactly what was received. ... View more

Hi @mikaelkvantic  It's 2.  After the stitch happens, Audience memberships are re-evaluated and connectors fire if appropriate.  This doesn't happen during the event replay during the stitch itself. ... View more

@Ranjan_Mestri  Are you sure you set up the rule with the OR as per my screenshot? Lifetime event count is assigned, OR Lifetime event count is not assigned? If you did, then you need to reach out to support@tealium.com so that they can reproduce this and help you. Thanks Mark ... View more

Hi @Reinhard  There is a setting that controls whether this is, or is not, the case.  The setting is accessed via the gear icon in the top right of the screen And then the setting is "Enable Rule Dependency Checking".  If this is "On", then Server UDH orders the enrichments for attributes such that any that depend on a rule based on another attribute will have that other attribute's enrichments run first. If this is "Off", then there is no such ordering, but the behaviour will be still deterministic. The reason there is a setting, and a choice around this, is that the functionality was added to Server UDH to do this, a couple of years back.  To avoid introducing a potentially breaking change (in some edge cases), it was added in such a way that it was set as "On" by default for any new UDH profiles, but it needed to be switched on manually for existing UDH profiles. So, if you have a relatively new UDH profile, this should already be on, and you will have the behaviour you expect.  If not, and the setting is Off, you can switch it On, and then publish. There is another similar setting, with similar rationale, called "Enrichment Order Respects UI Order".  If this is "On", then multiple enrichments for a single attribute run in the same order they are present in the UI, from top to bottom.  If it is "Off" then again there is no such ordering, but the behaviour is still deterministic.   ... View more

Hi @aaqib  There is an enrichment on Set of Strings that populates the Set of Strings with the key values in a Tally that have a value greater than a threshold you can define (4, in your case). So the way I would do what you want here is to define a Set of Strings, and use this enrichment on it.  If the Set of Strings is assigned (you can check this using a rule operator on the Set of Strings), then the visitor is in the Audience. You can also/instead, if you wish, use a Number to count how many items are in this Set of Strings.  If this is >= 1, then the user is in your Audience. Here is a diagram that explains how all the AudienceStream attribute types can be used with each other like this; https://community.tealiumiq.com/t5/Universal-Data-Hub/AudienceStream-Visit-and-Visitor-Attributes-and-Enrichments/ta-p/23244 Thanks Mark ... View more

Hi @mtrapiello  Yes, you can filter out events that you do not want AudienceStream to process. How to do so is described here (under "AudienceStream Event Filter") https://community.tealiumiq.com/t5/Universal-Data-Hub/Server-Side-Account-Settings/ta-p/29654 Mark ... View more

@mtrapiello  I'd suggest you get in touch with your Tealium Account Manager for questions about your contract. Thanks Mark ... View more

Hi @holbue  Brief answer - you only need to upload the changed rows Fuller answer - every row in a File Import is processed as an event in Server UDH, in pretty much exactly the same way as an event from a web page or a Collect API call.  It's up to you when you are configuring the system to decide what to do with those events.  For example in AudienceStream, you might be assigning a first and last name to a visitor profile for a customer.  That visitor profile will retain the first and last name from a previous File Import - there isn't a need to upload the same row again. Because the rows are events, if the customer made another order, for example, then the next File Import should contain another row for that customer, because you'd likely be incrementing the lifetime order value on each such event/row. ... View more

Hi @PhilipWright  With a couple of notable exceptions that I will explain here, AudienceStream is purely an event driven system that operates at the individual visitor profile level.   What this means is that visitor profiles only change state when an event individually enriches that visitor profile.   More concretely in your example, let's say;   You define a Visitor Level date to capture the event date You base an Audience on a rule to say this date must be within the past 180 days You fire a connector action on users joining the audience and another connector action on users leaving the audience.   This will work - users will fire both connectors, but there is a subtlety - users will have to have another event (either return to the site or app, or be enriched with an offline event) in order to leave the 180 day audience and fire the "leave" connector.   If your use case can't rely on that happening, then you need to look at alternative approaches.   One approach is to use delayed connector actions.  These are documented here - https://community.tealiumiq.com/t5/Universal-Data-Hub/Delayed-Actions-for-Connectors/ta-p/17575   What you'd do in that case would be to fire your Joined Audience connector as normal when the user joins the audience.  However, instead of the Leave audience connector, you'd instead set up another connector action based on "In Audience at End of Visit", choosing the "Was not in Audience at beginning of visit" option, and specifying a delay of 180 days.  This means 180 days after joining the audience, this delayed connector would fire, and you could remove the user from retargeting or whatever at that point.   Delayed connectors will only fire if the user is still in the audience at the point in the future where the delay timer actually runs down to zero.  So depending on your use case, if there is a way for the user to leave the audience in the meantime, you may want to set up a conventional "Leave Audience" connector action to catch that as well.   Also note with delayed connectors that they use the visitor profile as it will be at the point in time in the future when the delay runs down to zero.  So don't pass visit level attributes (because they won't be in scope then) and make sure you are happy that visitor level attributes you want to pass will still have the desired value at the point in the future.  This consideration is only relevant if you are actually passing payload to the connector. If you're simply removing someone from a retargeting list, you probably don't care about this.   Another approach to look at would be AudienceSizing, which is detailed here - https://community.tealiumiq.com/t5/Universal-Data-Hub/Audience-Sizing/ta-p/13781.  This also allows you to get away from the event-driven nature of AudienceStream.  It currently isn't automated, so you'd have to run the job manually each time you wanted to.  However, Tealium are working on making this automated/scheduled. I don't have an ETA on that, though.   With either of the two approaches above, you need to check that your visitor and/or audience retention period is longer than 180 days - see here https://community.tealiumiq.com/t5/Universal-Data-Hub/Building-an-Audience/ta-p/11881    Just for completeness, another option would be to use the vendor system to handle the 180 day expiry.  Many retargeting system will allow you to specify that list membership expires X days after joining the list.  In fact, it's worth checking if this will automatically be applied before you assume that the user would stay in the list for 180 days in the first place. ... View more

Hi @aaqib  I'd suggest you email support@tealium.com with details of the account and profile, as well as how to reproduce the issue, so that they may investigate for you. ... View more

Hi @BenStephenson  If you email support@tealium.com telling them the account and profile, they can enable a beta feature for you.  This feature allows you to specify that a number attribute is a decimal (the default) or an integer.  This is done on the attribute, not the connector, but does change how the attribute is formatted when being sent in connector payloads. ... View more

Hi @aaqib  That looks like AudienceStream might not be enabled on the profile you are tracing into.  Please email support@tealium.com giving them steps to reproduce (and the account and profile name) Thanks Mark ... View more