When you are building your use cases in AudienceStream, you might need to take into account offline visits when setting them up. In some cases, you might want to prevent offline data from interfering in your use cases.
In this article:
You are setting up an abandoned basket use case, with a delayed connector. The requirement is:
Only vistor-level attributes can be sent in a delayed action. Visit-level attributes are out of scope by the time the connector action fires.
To simulate visit-level attributes, we could setup a visitor-level attributes and reset the attribute on new visit.
If the user visits the site again during the 3 days and doesn't add to cart, the boolean would be false, and the user would leave the Audience, so the connector action will not be triggered.
Delayed action is triggered only if the visitor is still in the audience at the scheduled time.
However, if you also have an offline data import reguarlerly for all customers, using File Import or Collect API, your use case might not work.
Offline data coming in using File Import or Collect API also creates visits. When there is an offline visit,the visit boolean will reset to false, and the offline visit will not set it back to true as the enrichment requires online add to cart action.
This would mean that the visitor would leave the Audience on the next offline data import, and the delayed connector action will not be triggered.
"Most Recent Online Visit Abandoned [bln]" will remain true even if there is an offline visit for this user.