It's also good to keep in mind that GDPR is not the only compliance issue you have with purchased data. https://nation.marketo.com/t5/Knowledgebase/Best-Practices-for-Purchased-Data/ta-p/248405
... View more
We went live with a similar solution not long ago. We decided to choose smart lists as well, but I'm pretty confident our solution was a bit more simplified than what would work for you. In short... we started with a static list for every action/channel we wanted to record: form submissions, content downloads, etc... Then we created additional static lists for each product that might be associated to those actions. We ran smart campaigns to add to people to a list, then we eventually remove them from those lists. The removal from the lists is the most important part. It's the catalyst to pass the information into our CRM via an API connection. Once in our CRM, new custom object records are created for each [action + product] and stamped with a bunch of relational data (status, stage, score, dates, counters, etc...) Those new [action + product] records are now organized, presented, and updated by our Sales Team in a highly automated process as well. We passed a lot of our reporting needs into the CRM, as well as a lot of historical/archival needs around previous interests. We felt that out of the box Marketo would allow the Marketing team enough time to properly orchestrate all of the necessary reactions to an inbound interest. We also concluded that any detailed reporting on product interest would have to be closely tied to Sales data/processes in our CRM anyway. All in all, it was a heavy CRM development project with a very simple API connection. I can't imagine it scales well for teams managing large numbers of products like yours though. We topped out at less than 350 static lists across 5 product categories.
... View more