Provide pod/datacenter-neutral way to reference Marketo UI URLs

0 Likes

Provide pod/datacenter-neutral way to reference Marketo UI URLs

As a developer who builds tight integrations with Marketo, I am interested in being able to send users back to Marketo where appropriate reviews can be done for things like Lead records, Smart Lists, various Assets, etc.

For example, if I am showing records to a Marketo customer that may need to be reviewed (such as having a bad email address), I'd like to provide the exact record in Marketo's UI for cross-referencing. However, to create a URL around a Lead record's details, the structure needs to be like the following:

 

https://app-aba.marketo.com/leadDatabase/loadLeadDetail?leadId=123

 

Without an Idea like Provide API method to determine instance datacenter , there is no way to provide a correct URL to end users. There is no valid way to create a redirect that would allow a developer to send people back to Marketo without knowing the exact datacenter and pod.

 

Today, Salesforce works around this potential issue by using login.salesforce.com as a valid wildcard redirect, like so:

 

https://login.salesforce.com/lightning/r/OBJECT_TYPE/<RECORD_ID>/view

 

However, no such equivalent exists inside Marketo's architecture. The current closest behavior involves the newer URL structure of https://engage-ab.marketo.com/?munchkinId=123-ABC-456#/classic/MA, where an improper datacenter will still resolve—swapping the URL for "engage-sj" or similar still results in the final correct URL.

Given that we want to help keep Marketo users inside Marketo where relevant, could a wildcard redirect link be made available?