01-12-2017 09:08 AM
Audiences being joined and left are fully dependant on attributes and their enrichments. If an attribute value is changed such that the audience critera is no longer met, the visitor will leave the audience.
Let's talk about the process of events ofwhat happens when an event is fed into AudienceStream:
Therefore, visitors can join and leave audiences within the same session, depending on the setup of your AudienceStream instance.
Please let me know if you have any further questions or need more clarification!
06-05-2018 05:05 AM
06-06-2018 01:45 AM
No. As Dan said, Audience Evaluation is performed after each incoming event (or the visit timeout) has been processed, and the Visitor and Visit attributes enriched. So the visitor will end up, after each event, in one of the following states;
Was not in the Audience, and has now joined it
Was not in the Audience, and no change
Was in the Audience, and has now left it
Was in the Audience, and no change
I suspect that what you are asking is - "can I make the visitor join an Audience, fire a connector, and then leave the Audience immediately so that on the very next incoming event the cycle repeats"?
The answer to that is "no", not in AudienceStream. However, EventStream does allow for this, in the sense that connectors in EventStream are triggered by individual events match a defined set of rules, called a "Stream". And each and every event that matches that Stream, even from the same visitor, will trigger the connector. The only limitation is that the EventStream product deals purely with Event level data. No AudienceStream attributes can be sent along with the EventStream connector.