Tealium Learning Center

Could you tell us more about what you are trying to do? ... View more

Hi @william1 , You'd think that a tally would keep a score (tally) of a specific item, but actually it's a Key-Value store. However the values can only be numbers. We're using this to see: what products the customer has looked at the most. This is a standard Tally where each Key is the product ID, and each value gets increased by 1 for every product view. what products the customer has looked most recently. This is a tally where each key is the product ID and the value get set to 0 (zero) first and afterwards the value get's set to the current timestamp in ms. This ensures that the last looked at product always has the highest value (the timestamp)    All the best, Tim  ... View more

Failure of connectors are a bit hard to understand. Looking at the error message you've provided I should think you haven't assigned the correct attributes to the facebook customer audience connector. I've requested a feature to let audiencestream send you an email when a connector fails, please upvote my feature request .   ... View more

@dan_george I'm having the same Issue when using the Google Sheets connector. I'm sending a captured date attribute and it also sends the timestamp in millisecond resolution. I would like to send a formatted date/time to the sheet. ... View more

Bump to this use case, we're currently running into the same issue. I've added a product idea for these types of use cases. I Would very much appreciate your upvote/like. See the product idea here: https://community.tealiumiq.com/t5/Product-Ideas/Stitching-with-changing-visitor-IDs/idi-p/24077 ... View more

I've fixed it by creating load rules that match parts of the cookie that is being set by the consent management dialogs. Also the cookie is read and stored into UDO variables to limit the firing of some applicable extensions.   This seems to work for now, but it feels like a work-around. ... View more

Hi @mark_reddin, Thanks for your reply. I was afraid of that.  Our current strategy is to recalculate part of the algorithm within the tag manager (IQ) for web-based tags and do the calculation, based on start and end of session, for other channels that have single hits (eg. email opens etc.) ... View more

Hi @KaiB, My understanding of the retention period is that it is a period that starts after each event that is sent to AudienceStream for that specific visitor/profile. If a profile hasn't received any events within the profile retention period it is removed from AudienceStream. The retention period is applicable to the storage of the entire profile not the individual profile's attributes The attribute for "last purchase date" will not change for a visitor if no rules are triggered for it. Event attributes are "forgotten" after the event is over. Visit attributes are "forgotten"after the visit is over (with a small time window) Visitor attributes are "forgotten" after the period since the last received event for that visitor was longer than the visitor retention period. As to your second question, wether this is 2 calender months or a preset amount of days, i'm not sure. All the best, Tim ... View more

Hi Mark, thanks for your reply.  We'd like to use a relatively simple algorithm that calculates the new score based on the current score and some other factors (such as time passed since last calculation). Something like this: x= (x/2 + y*(z-z*0.5))/4 so the question really is; what mathmatical operators can we use and how can we use them? ... View more