Integrating Marketo with pCon.login (EasternGraphics) – Seeking Best Practices | Community
Skip to main content
S
SimoneRomano
Level 2
April 14, 2026
Question

Integrating Marketo with pCon.login (EasternGraphics) – Seeking Best Practices

  • April 14, 2026
  • 1 reply
  • 20 views

Hi everyone,

I’m looking to connect pCon.login (by EasternGraphics) with Marketo Engage to automate lead flow and tracking. For those unfamiliar, pCon is a leading ecosystem in the interior design and furniture industry for 3D configuration and OFML data distribution (pCon.update).

I would like to know:

  • Has anyone attempted this integration before?

  • If so, did you build it internally (API-to-API) or did you have to rely on middleware (like Zapier or Make)?

We are trying to understand the best architectural approach to capture leads from pCon.update subscriptions and pCon.cloud configurations without adding unnecessary layers.

Any insights or experiences would be highly appreciated!

      1 reply

      SanfordWhiteman
      SanfordWhiteman
      Level 10
      April 14, 2026

      Could be wrong, but doubt anyone active on this community has worked on that integration.

       

      Either way, there’s no “API-to-API” communication outbound from the Marketo REST API. The API is passive and only processes inbound requests. Webhooks and self-service flow steps can be considered Marketo’s outbound APIs, but they only respond to person-level triggers.

       

      I’d suggest you explain your desired architecture and then we can give more suggestions. For example, what data flows from p.Con and to what Marketo objects (People? Custom Objects? Program Members?). What data, if any, flows back to p.Con?

      S
      SimoneRomanoAuthor
      Level 2
      April 15, 2026

      Thanks for the insights.

      To clarify, this is intended to be a very basic integration, so I’m looking to avoid complex architectures like Custom Objects. Here is the logic I’m aiming for:

      • Outbound (Marketo to p.Con): This would be limited strictly to synchronization of unsubscribes. I plan to use a Webhook triggered by the 'Unsubscribe' status change to send the Email, Company, and Unsubscribe = True back to p.Con.

      • Inbound (p.Con to Marketo): A standard lead push containing only core fields: First Name, Last Name, Email, and Company.

      • Data Organization: To keep both databases aligned and distinguishable, I intend to use either Program Membership or a specific Lead Source value. This should allow us to segment these leads effectively without needing a more complex data schema.

      Does this simplified approach seem viable given Marketo's webhook limitations, or is there a specific 'gotcha' I should be aware of when syncing the unsubscribe status this way?

      SanfordWhiteman
      SanfordWhiteman
      Level 10
      April 15, 2026

      No immediate red flags. But can you call the p.Con API using a stateless request like a webhook? That is, if p.Con needs a separate auth flow and/or access token refresh, that won’t work via a webhook. A webhook can only use a permanent access token.

       

      Likewise, the Marketo API can’t be called using a stateless request. You always need calls to the identity endpoint for a fresh bearer token. So if p.Con can just send dumb outbound webhooks, that won’t work. You’d need to go through an intermediate gateway layer that manages auth (plus probably transforming payloads from p.Con). Not a complex layer by any means, but you need something running. 

        Terms & ConditionsAccessibility statement

        Loading footer...