When Service Objects first started creating integrations for Marketo, we started by demonstrating how our services can be utilized in Smart Campaigns via webhooks. Another feature of Marketo is landing pages, or web forms that can be developed through Marketo where end users can land or navigate to and interact with. These landing pages or web forms are very useful and present opportunities to make sure end-users are entering clean and validated data into their systems. However, danger lurks ahead…
All is not lost, however. We can still integrate with the Marketo Landing pages, however the way we integrate will depend on the service. We have two types of license keys for our services: Custom Keys, which are currently used with just our Global Address Complete service, and our traditional keys, used with the rest of our API services. After reading the blogs linked here you’ll discover that the key difference (no pun intended) is that Custom Keys are more secure than our traditional key, and can be listed in front-end code due to the additional security features they have. This makes it easy to integrate the Global Address Complete solution into a Marketo Landing Page – follow the link in this sentence for a blog on how to do just that.
To sum it up, in addition to having Marketo and a Service Objects License key for the service, you must be able to host a back-end web page that the Marketo Landing Page calls, where a license key can be added before the request hits our API. Here is a basic flow that can help with visualizing what is going on, and the difference in how Custom Keys and traditional keys should be implemented.
You will need to consider license key variations when implementing our services on a Marketo Landing Page. And, of course, if you have any questions or get hung up along the way, we are always here to help and walk you through what needs to be done – contact us anytime.