Name: Understanding Data Lifecycle Management in SAP Marketing Cloud
Uploaded: 2018-9-6
Duration: 291 s

Share feedback

<p><u><strong>Planned maintenance of Practice Systems</strong></u></p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div>Day by day thousands of interactions may be stored in your SAP Marketing Cloud system to support your marketing activities. As valuable as the data is at present, over time it can clog up your system, block storage space, and obscure important information. Watch this video on how to practice good housekeeping, and declutter your system regularly with SAP Marketing Cloud.<div><p>NOTE: The application job used as an example in this video has changed and is no longer valid, but the deletion concept recommended in the video still applies.</p></div></div></div>

Understanding Data Lifecycle Management in SAP Marketing Cloud

Day after day, thousands of interactions may be stored in your SAP marketing system to support your marketing activities. As valuable as the data is at present, over time, it can clog up your system, block storage space, and obscure important information. Let me show you how to practice good housekeeping and declutter your system regularly. First, I'll use the Interaction Data Browser for an overview. Let's see how many interactions older than six months we have in this system. November 30th. Okay. Quite a number. I want to see the dates and the list. Here we are. Let's focus on email as the origin of these interactions. Still quite a lot. Do we really need to know about such outdated interactions? Probably not. So how can you get rid of outdated interaction data such as outbound emails? It's quite simple. Marketing application jobs. Take care of that before we create a deletion job. I'd like to indicate that deleting interaction or contact data should always be done in a two step process. First, you just flagged the data for deletion. Run the job in test mode to check the results and adapt the job if required. Then run the job in productive mode. Once you are sure about the results, you create a second job to delete the flagged data. Let's see how this is done in the system. Click the plus to add an application job. As explained, we first create a flag for deletion job. There are templates you can use to define the job. Click to search for a suitable template. Search for interaction templates. Here we are. Choose the flag for deletion template. I'll specify a name to find the job more easily later. The template specifies a weekly recurrence of the job. That's fine with me. You can change the default, of course. There are additional settings such as a 90 day retention period or interaction types, but typically provide no useful insight when outdated. Be careful when specifying the parameters for the job. See the documentation for details. It's just a click away. Use the test mode. Check the result to avoid accidentally losing data that you want to retain. Because when you run the job productively, the data has been archived, which means it's not available anymore for marketing activities. Okay, let's run the job. There's the option to start immediately. Fine. Click schedule. Should be ready by now. I'll search for the job. Click the status information. Okay. There is quite some interaction data we may want to get rid of. What about outdated contacts? For example, cookies that are stored as contacts. Let's see. I can use the Contact Origin data browser for an overview of contacts with the origin cookie. There it is. As you see, it can be worth decluttering the system. And cookies are just one example. Another best practice is looking for invalid email addresses, which you can find using a corresponding interaction type, such as hard bounce. It's also worthwhile checking contacts that have had no interactions with in a given time. For that, you could use the deletion jobs that have already been shown. Now let's assume you have scheduled regular jobs that flag outdated interaction and contacts for deletion. Then it remains to create application jobs that really delete the flagged data. You do this in the same way we've already shown. Just use the relevant template. For example, the delete flagged interactions template for flagged contacts. There's another template that takes care of the deletion. And remember be careful with the parameters. Always check twice.