Proper Way to Store Data for Non-Marketable Records | Adobe Higher Education
Skip to main content
J
Jeff_Bedford
Level 2
February 7, 2019
Pergunta

Proper Way to Store Data for Non-Marketable Records

  • February 7, 2019
  • 2 respostas
  • 3588 Visualizações

Hey All-

I am admittedly posting this prior to looking for documentation - as the community (especially Sanford) has been really helpful in helping us think of solutions to a few of our problems so far. For today's issue, I present to you the case of the growing database. Let's say for example that we have 950K records in Marketo, and because of the way we are loading records in via API - that number grows quickly to over 1M. Oh no! We now owe Marketo lots of money as we have entered a new payment tier.

Then (totally for example!) we decide a good way to get back below the payment threshold. We are going to run some jobs that delete user records for leads that hard bounce, opt out of our email program, unsubscribe (because of durability), etc. It works! Everything is going smoothly - everyone is chipper. We are below the payment threshold.

Then, an obstacle! We have a client call in and request an audit of a program they were enrolled in. Easy enough right? Until we realize that the data they are requesting has been deleted as a result of our new deletion policy. So, the question becomes:

How can we keep those records in order to have the data necessary for emergency audits, historical reports, etc. - without having them count against our known lead count? We already store some key reporting metrics elsewhere - so our main use case is really based on the ability to look back, audit, and be able to re-create the story of what really happened. Any ideas?

Este tópico foi fechado para respostas.

2 Respostas

A
AnkitDu3
Level 6
February 7, 2019

What we are doing is we are exporting all non-marketable leads into an excel sheet with all columns and save the excel sheet by date when the data is exported. I would also like to know what can be other good options here.

SanfordWhiteman
SanfordWhiteman
Level 10
February 7, 2019

Glad you asked about lead offboarding strategies because I've been meaning to write a blog post about this area.

The simplest offboarding can be accomplished by sending lead data to a Google Sheet via a webhook, just before deletion. Upon later reentering the system, call the companion 'hook to look up in the existing sheet and pull the old data back in.

But this only applies to flat lead fields and, potentially, custom object records attached to the lead. It doesn't reproduce the program history, activity log, and so on. If you need to recapitulate the entire history of the lead, exactly as you would've seen in their Activity Log, that's unfortunately impossible. Even if you export the entire program tree structure and "entire" log (which isn't actually entire) into a set of timeseries and hierarchical databases, you can't repro the whole thing. (Don't listen to anyone who tells you otherwise.)

Can you tell me what you mean by "an audit of a program" exactly?

    A
    AnkitDu3
    Level 6
    February 7, 2019

    Do you have any documentation of on how to send the data to google excel sheet via webhook, I tried searching on your blog but couldn't find one.

    Termos e condiçõesAccessibility statement

    Loading footer...