Auto Delete Profiles | Klaviyo Community

Hello Klaviyo Community,

I’ve got a problem I need some help with. In short, we’ve integrated our Shipstation account with Klaviyo to send shipped email notifications. With this integration, every email from shipstation gets imported into Klaviyo. Our Shipstation is also integrated with Amazon. The problem is that the emails from Amazon incoming to Shipstation are auto-generated and are not tied to any real person. They all end with “@marketplace.amazon.com”. What I would like to do is have these profiles be automatically deleted.

I’ve already created a segment isolating all of these profiles. I know you can use the segment to suppress profiles, but this is a chore to do manually.

I’ve followed the directions outlined in this article and am getting a 404 error when I do my test. The private API I created has full access so I’m not entirely sure what the cause is. Here are some of my screenshots;

What I have entered into the flow as described in the article linked above.

{
  "data": {
    "type": "data-privacy-deletion-job",
    "attributes": {
      "profile": {
        "data": {
          "type": "profile",
          "attributes": {
            "email": "{{person.email}}"
          }
        }
      }
    }
  }
}

What I have in the JSON section of the webhook.

Any help is most appreciated!

Page 1 / 1

I could be wrong, but I think the spaces in your dynamic field are mandatory. So when you pull in the email address, you actually need to use: {{ person.email }}

But if I were you, I would just suppress them instead of delete them.

I would 2nd @DavidSandel to not delete the profiles but suppress them —suppressing rather than deleting keeps these profiles available for future engagement without hurting deliverability. If they re-engage later, you can easily add them back into active segments. Deleting would mean losing them permanently.

Thanks @DavidSandel and @ali786! Appreciate the feedback. I guess my logic for deleting them was that these emails are not tied to any person we could ever engage with. But, I appreciate the feedback and will move to suppressing the profiles instead. I just don’t want to pay for them!

I made the changes you both suggested and according suppression option in the article I linked previously. Still no luck. I get this error code when I try to test it. I can see that it is pulling in the email correctly just not successfull in executing the action.

My only other thought is that the information in the article is outdated. It was written in June of 2022 so, the chances of the required info needing changed is high.

@DavidSandel I found it! I had the wrong “revision” date in there. I came across another Klaviyo Community post where someone was running into the same issue and you mentioned the revision date was according to the revision date of the API and not the date I was making the revision. Once I changed it according to the article, worked like a charm. Thanks!!

@shanermp - Glad you figured it out. I was just about to suggest that perhaps your revision date looks outdated, but you beat me to the solution. Just note, the API can change/update over time (as you see here) so you may want to monitor this periodically!

@retention thanks! I will make sure to check in periodically to ensure everything is running smoothly.

Appreciate the help everyone!

Reply

Sign up

Use your Klaviyo credentials

Log in to the Community

Use your Klaviyo credentials

Scanning file for viruses.

This file cannot be downloaded