Forum Discussion
Help - IAM's are spamming some of our users
Hey Charlie - hasty response here given the nature of the issue.
You could pretty quickly set up a custom attribute to determine if someone is eligible for this IAM. I'm not sure what your entry criteria is for the campaign/canvas, but you could set up a custom attribute called "last_rating_request_date" and update it after someone receives this IAM. If you're using a canvas, send your IAM and then use the user update step to enter today's date into the "last_rating_request_date" field. Then update your entry criteria to only allow individuals where last_rating_request_date is more than 30 days ago, or however long you'd like to make that wait.
You can set today's date in the User Update step using the json editor and entering something along these lines:
{% assign timestamp = 'now' | date: "%Y-%m-%dT%H:%M:%SZ" %}
{
"attributes": [
{
"last_rating_request_date": "{{timestamp}}"
}
]
}
Each time someone is qualified to move back through and receive the IAM, they'd receive that message and then the update step would keep the date updated - scales pretty easily. You could also add an additional attribute, or custom event, to log how many times someone has entered this canvas and block them from reentering after 3 attempts with no rating submitted, assuming your capturing that rating as a data point somehow.
Fully recognize that this doesn't solve the issue/mystery on why someone is reentering when they shouldn't be, but it's a potential solution to basically recreate the functionality you're experiencing these issues with to put a stop to the spammy behavior as you investigate further.
Hope that helps!
- charliesmith042 years agoActive Member II
Thanks so much Jake. I will pass this on to my team and hopefully they will give this a try.
Related Content
- 2 years ago
- 2 years ago
- 2 months ago