Custom Objects: Doing it wrong?

[Anonymous]

We've hit a bit of a sticking point in our final pieces of tech integration with custom objects and the API.

In short, we're looking to manage our leads for smart list in different Nurture campaigns. Our end goal is to achieve some structure such as the following

Marketo Person <--- SW User (a user in our system) <--- Accounts (accounts a user can be an owner of) <---Campaigns (1 or more products in an account)

another way to look at it is a User has at least one account and that account has at least one campaign (one of our products) in it
Marketo Person
     Sw User (user in our system)
            Accounts ( accounts users can be apart of)
                  Campaigns (one or more of our products in an account)

However, I'm not seeing a way of going 3 levels deep in these objects. Is the above chain able to be linked? I've tried numerous ways to publish the edge objects, and use 2 link fields in the bridge, but I'm always left with one object out, or the error trying to link the campaign object last (Need link field links to standard object (Lead, Company) for approve.).

If the above is not achievable (Marketo lead <-- Custom object 1 <--- Custom Object 2 <--- Custom Object 3), our second thought was to implement custom fields in the Marketo person (standard object) that we'd have used otherwise in our Custom object 1 (user in our system).

That means our chain would be doable as Marketo Person <--- Accounts --> Campaigns.

Any thoughts or answers are much appreciated.

[Bill_Lundy3]

Sanford Whiteman​ or Grégoire Michel any ideas on this one?

[SanfordWhiteman]

I don't believe 3rd-level relationships are supported, and even if you could hack it together filtering would be broken. Definitely accessibility from Velocity scripts is broken with even 2nd-level objects, which is a deal-breaker for me in many cases.

If the above is not achievable (Marketo lead <-- Custom object 1 <--- Custom Object 2 <--- Custom Object 3), our second thought was to implement custom fields in the Marketo person (standard object) that we'd have used otherwise in our Custom object 1 (user in our system).

That means our chain would be doable as Marketo Person <--- Accounts --> Campaigns.

Sure, that would work. (With the Velocity exception.)

Or you could think about using Velocity tokens themselves as your product catalog (this enables wider visibility).