Hey Sanford Whiteman, Yes! I definitely meant purchase history. Could you elaborate further by what you mean here: "Generally there's one CO for every record in a purchase database. We detach (delete) and reattach the CO when purchases are modified (this means you will need to keep a record of the CO's marketoGUID field after insertion). Under high volume you would want to consolidate multiple purchases into a single CO as it is more efficient and easier on the system. For example, keeping 10 purchases at a time in a single CO record." Our approach was to have a custom object for 'Credit Card Transactions' that's linked to our 'Credit Cards' custom object which houses basic data. By adding all this data, will Marketo run even slower? Regards, Raquel
... View more
Hi Raquel, to echo what others have already said, the size of your team is a big factor in the review process. Our team isn't using any additional software outside of Marketo for email review processes. We do use a project management tool that allows for us to track the progress of the projects, but we include 'review/approval as a step in our marketing operations team's process. Simply put, the marketing ops person working on the request sends a sample email for 'review/approval' to the requester (testing things like CTA links, reviewing the sender info, subject line, email copy, etc.). Once we receive an email back from the requester with approval, we approve the asset in Marketo and schedule. It's worked well for our team! Hope that helps!
... View more