My company has multiple different Brands (A, B, C) with different platforms (1,2,3, etc.) In our Marketo instance, we use Custom Objects to store information, like profile info, from other systems. Each profile gets its own object. So if I have a profile on Brand A, platform 1 and 2, Brand B platform 3, and Brand C platform 4, I’ll have 4 custom objects on my contact record. We keep all this information stored inside a Master Data Record outside Marketo, and each time we add a new platform, a new “row” gets added for each platform and a whole new mapping needs to be created. However, our data team suggested that we create an agnostic “Profile Data” object, where the brand and platforms are fields. This way, each time we add a new platform to the Master Data Record, they will just be pushed into our Marketo Instance without having to do extra mapping, scope work with development, etc. My concerns are this: we have plenty of fields that overlap platforms – first name, last name, email, etc – but we also have plenty that are unique to that individual platform: Is there a limit to the number of fields we can put into a Custom Object? Does it become too un-wieldy on the system to have too many fields in a Custom Object? What does this mean for the number of API calls? What about velocity scripting? We are currently starting to lean more heavily on velocity to pull information from objects to populate into emails, does this make it a never-ending cascade of conditional logic that will break the script?
... View more