Tealium Learning Center

Hi @umarCh_RC  From https://community.tealiumiq.com/t5/Tealium-Predict-ML/Prerequisites/ta-p/33148 Target Attribute Volume Minimums Your target attribute must have a minimum daily average of 200 true and 200 false visitors over a 30-day period. So it's not the total numbers that are used for determining that a model is ready, but the daily average (actually it's the median) numbers. ... View more

Hi @PhilipWright  In AudienceStream, it doesn't matter what the source of a visit is - Collect tag, Collect API call, File Import - a visit is started for any of these inputs. It's just that some of them don't enrich some of the built in attributes (for example Lifetime Visit Count isn't incremented by File Import). However, all of these inputs will trigger a visit and therefore "In Audience at End of Visit" delayed connectors will fire as long as the visitor is in the audience at the end of the triggered visit. ... View more

Hi @Luissanchez2901 https://community.tealiumiq.com/t5/Attributes-and-Enrichments/How-to-track-a-visitor-favorite-over-a-rolling-time-period/ta-p/9654 The above recipe should help you Mark ... View more

Hi @emea21-561  To clarify, you mean that you'd like Trace to show Event-level server side enrichments? I think that's a good product idea, and you should log it here - https://community.tealiumiq.com/t5/Product-Ideas/idb-p/product-ideas Mark ... View more

Hi @dippradhan  I think you are referring to AudienceStore and EventStore, since they generate JSON files as their output. They are explained here More on AudienceStore setup More on Event Feed setup Basically, the difference is that EventStore can store a record of an incoming event as soon as it received by Server Side CDH.  AudienceStream is not relevant to EventStore - it operates on the "raw" event data before it is processed by AudienceStream, if AudienceStream is enabled (it need not be). AudienceStore, on the other hand, is actually a specific AudienceStream connector.  So a. You are dealing here with Visitor and Visit attributes that are stored, not Event attributes. b. Just like any other connector, you configure AudienceStream to tell it when exactly you wish to write the record to AudienceStore. ... View more

Hi @wangting  To do (A OR B) AND C in server side CDH, you can do (A AND C) OR (B AND C) You actually have a couple of different ways of doing this - you can do it all in a single enrichment, or do it in two enrichments.  This is because having two enrichments that assign a badge is equivalent to an OR - if the rule for either enrichment is true, then the badge is assigned.  Both ways are shown below.  My preference is two enrichments, as the rules are simpler.  Simpler rules are (a) easier to name and (b) more likely to end up being reused. As for using a visitor level badge vs a visit level, that depends on your use case.  If you want the user to join the audience the first time they do this action only, then a badge is a good choice.  If you want them to be able to join the audience again on the next visit where they repeat the action, then a visit level boolean would be a better choice.  However, if you go with the visitor level badge and later want to change that, you could add a first enrichment to the badge that removes the badge on any new visit as a quick way to convert it from visitor based to visit based. ... View more

Hi @aaqib  AudienceStream is mostly event-driven, meaning that as you say, the user must have an incoming event in order for their Visitor Profile to be enriched and Badges assigned or removed. We do have delayed connectors to help here.  Using that approach, you could have a connector fire if the user does not revisit the site after X days.  Delayed connectors work by setting up the triggering of the action at the end of the visit where the user is in an Audience.  However, rather than trigger immediately, they wait for X days, and they check that the user is still in the Audience after those X days.  So to ensure that the connector does not trigger if the user does return, you make sure the Audience is left if there is a return visit. We also have Audience Sizing as another option.  Using this approach, you would define a rule based on the users last visit date being older than X days, find the matching visitors and trigger a connector to them. ... View more

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