Hello,
We have a bunch of different third-party systems that create the leads through API calls. Our system needs to handle new leads differently based on the lead source (specific API users) at the lead creation webhook. For that, we need to get an email or username of lead creator API user.
Does Marketo have any solution to this issue? (e.g. create a custom field and fill it at some Marketo interceptor)
Thanks in advance.
To handle this, I have created a custom field in Marketo called "Latest Lead Source" and feed this in Marketo from different systems with their respective source value. This way, even if you are using the same Marketo API user at multiple places, you can still be able to differentiate the leads from different sources.
Hope this will help.
Thanks.
"Latest Lead Source" field value is defined at the upstream system. Did I understand you correctly?
Yes, that's correct.
Our system needs to handle new leads differently based on the lead source (specific API users) at the lead creation webhook.
The REST API endpoints aren't webhooks. That's the reverse direction.
What Amit suggests is the best you can do within your (probable) technical limits. We take it further and have every API connection come in via an API gateway. That gateway always tags the inbound call with the identity of the requester, so they don't have to remember to include it.
Thank you for your answer.
The REST API endpoints aren't webhooks. That's the reverse direction.
I mean our downstream system handles lead creation webhook from Merketo. But the main problem is the identification of API user who creates leads.
We take it further and have every API connection come in via an API gateway. That gateway always tags the inbound call with the identity of the requester, so they don't have to remember to include it.
Did you create a reverse proxy over Marketo?
Does this proxy have its own authentification to identify users?
Is it possible to build this solution under Marketo infrastructure?
Did you create a reverse proxy over Marketo?
Yes.
Does this proxy have its own authentification to identify users?
Yes, sure does.
Is it possible to build this solution under Marketo infrastructure?
No, it's not.