Hey Sanford Whiteman, Thanks again for your response! Marketo Support mentioned using custom activities which didn't seem correct, so I'm glad you were able to confirm that COs would be the way to go. Our thought here was to include credit card transaction information in a manner to which we can pull smart lists for marketing efforts, instead of having to import lists for select campaigns. For instance, including transaction history would tell us if a member goes inactive and hasn't made any purchases on their card in a certain time frame, etc. We could then automate a campaign promoting usage or even target those members specifically for a special offer. I hope this makes sense. While I agree this isn't a place to host all that data and it may make the system run evennn slower, it is data we can use to target better. So, instead we're thinking about just pulling in select information aggregated on the back side that flags a field based on what we're trying to see. Detailed transaction history is just great to see because we could also see where purchases are being made, which could potentially assist us in personalizing campaigns. How are you utilizing custom objects to show historical data on purchase-type records: appointments, product holdings, sales quotes, and so on? Or does the CO field get overwritten when there's something new to populate?
... View more