I hope you are doing well.
I wanted to badge the user who has not visited the brand for X days. And wanted to get the difference between the current date & the last visit date. But the current date will populate/work only when a user does some activity on the platform and upon receiving the event it will assign the current date and do the rest of the logic of giving the difference between two dates.
But in my case, the user is not doing any activity and hence not receiving any events and it will not generate the difference between the last visit date until some event occurs. is there a way to get this difference even though the user is offline and we can get the difference and target those who are not showing any activity in the last X days and send them a message encouraging them to visit again?
What I thought is if I get the difference of X days then I can Assign a badge to those who visited X days ago and target those who met with these criteria.
Let me know if there is a solution that already exists within the platform or there is a workaround for these kinds of situations.
Md Aaqib Uddin
Solved! Go to Solution.
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.
Hi @mark_reddin, thanks for the alternative solution, the delayed connector works for me by setting up the triggering of the action at the end of the visit where the user is in an Audience. I'm using this solution in most of my recent implementations and really like the logic
And sorry for marking this as a solution too late, because I'm been busy/inactive and didn't get a chance.
Thanks for the kind support and help, much appreciated.