-
Re: Lookup tables
Sanford Whiteman Nov 12, 2018 7:53 AM (in response to Michael Oslin)If you feel like trying a new method, I'm working on a blog post about a new take and you can help me QA if you want. Send me a message.
P.S. Don't know which of my older posts you meant because it looks like you linked to the blog homepage.
-
Re: Lookup tables
Jay Jiang Nov 12, 2018 6:19 PM (in response to Michael Oslin)A simple php webhook solution
<?php $utm_campaign = $_POST['utm_campaign']; $data=[ "utm_campaign1"=>"utm_campaign_actual1", "utm_campaign2"=>"utm_campaign_actual2", "utm_campaign3"=>"utm_campaign_actual3", "utm_campaign4"=>"utm_campaign_actual4", "utm_campaign5"=>"utm_campaign_actual5" ]; if(isset($data[$utm_campaign])){ $response = ["utm_campaign"=>$data[$utm_campaign]]; echo json_encode($response); } ?>
-
Re: Lookup tables
Sanford Whiteman Nov 12, 2018 7:23 PM (in response to Jay Jiang)1 of 1 people found this helpfulWait a few days and you'll be able to do this without maintaining a whole separate server...
-
-
Re: Lookup tables
Grant Booth Nov 13, 2018 12:50 PM (in response to Michael Oslin)We use a webhook to Workato (where lookup tables are supported) to accomplish this. We send the value in the webhook, it matches it in a lookup table, and then sends a value back to Marketo via REST API. The lookup table can be updated via a simple CSV import. It is a custom process but I'd be happy to explain how we do it if you're interested in that route. We were already using Workato for other custom services and integrations, so it was 0 extra cost to do.
-
Re: Lookup tables
Sanford Whiteman Nov 13, 2018 1:12 PM (in response to Grant Booth)Via REST API? That sounds crazy. DoS waiting to happen for any batch that's larger than your number of daily API calls (not even touching the other integrations).
Shouldn't ever need to loop back over REST when using a webhook. The Webhook API is designed to write data back to the lead directly.
-
Re: Lookup tables
Grant Booth Nov 13, 2018 1:19 PM (in response to Sanford Whiteman)Sanford we only use it for triggers, not batch processes, so the API limit isn't a problem. The same webhook actually runs a variety of logic at the same time, so it needs a little time to process before writing into the Marketo DB. For example it also does some simple math-related tasks that can't be done in Marketo, like marking as junk if First Name = Last Name, etc.
-
Re: Lookup tables
Sanford Whiteman Nov 13, 2018 1:26 PM (in response to Grant Booth)1 of 2 people found this helpfulwe only use it for triggers, not batch processes, so the API limit isn't a problem.
But are the triggers themselves forcibly capped at a certain number of calls per day?
Either way, it's not the way one should use webhooks unless there's truly no alternative. The goal w/webhooks is that data updates on the host result from a single request/response. There are so many easier ways to do what you're doing that don't require any loopback connections.
For example it also does some simple math-related tasks that can't be done in Marketo, like marking as junk if First Name = Last Name, etc.
Surely that takes < 1μs to process on the server.
-
-
-