About xceled

xceled

Currently, Marketo offers some "Bulk Export" functionality for situations where latency can be higher and many records need to be exported. This is marketed as an alternative to real time calls. However, transitioning from real-time calls to the bulk export feature is not straight forward because the data offered by the real-time call exceeds what is offered in the bulk export call. This specifically affects the data in the "Attributes" property that is offered by both API calls. The real-time call returns more data in that field than the bulk export call. For consistency and to avoid additional API calls when transitioning from real-time to the bulk export API, it should offer the exact same data points in the "Attributes" property as the real-time call.

xceled

Thank you @SanfordWhiteman for the information, I wish they would use swagger to document the response model field limits. I'm not just storing lead data, also other types, so my need is generic across any API that returns a response payload. E.g. Email subject length, folder name length, email description length.

xceled

Hello, We'd like to send emails using the "Request Campaign" REST API on demand, but it looks like we would have to create a new campaign for each email we want to allow sending via the API. This is is undesirable for a variety of reasons, the main being is we now have to have a 1:1 mapping of email to API enabled campaign which then has to be accessible to our programmatic logic. Is there a way to just pass in the email asset id and have the campaign pick/send that email from a single campaign? We still want the email sends to be tracked under the original email, so I don't think a single email with 'Dynamic Content" works for us. It seems like Marketo wants to make sending emails from the API the hardest operation for people to perform.

xceled

Hello, I'm consuming the REST API for various integrations in in some cases have to store data locally. I'd like to have my DB schema match the max lengths of Marketo data but am having issues finding how to determine the max field length of various data fields returned via the API. Can anyone suggest and approach or resource to assist here?

xceled · ‎08-03-2021

Hello, Is it possible to sync the Marketo Lead Id of Contact/Lead records from Marketo to Dynamics? If so can you please share details on where to configure this?

xceled · ‎07-23-2021

You say its not feasible, but it is, they make it work fast in other places. Their own MSI solution, does not suffer from this issue. It can retrieve these same 2 activities for this lead in a fraction of the time. It does not use the REST API. Their own web UI, does not use the REST API, it uses https://instance.marketo.com/leadDatabase/queryDetailLogData. Which again, does not suffer from this issue and returns all of this leads activities in under a second. So why, is the REST API, designed to not leverage the same performance design that their other solutions use? The accepted solution here seems like it should not be "work around it" but rather should be that Marketo fix their API.

xceled · ‎07-23-2021

Why is that an acceptable solution? That is an awful solution for the API consumers and introduces significant burden on API consumers to store and maintain entire databases and sync processes for ALL activity records to cover the situation where we might need to get the activity details on demand for a single lead. You mention " The behavior of the nextPageToken is well-known: it's a cursor through the entire log, not through a filtered subset of the log by only a single activity.", its not well known to me, I read the API docs and this behavior was not mentioned or warned as a concern to be aware of. I had to find out by doing direct testing with the API. Your comment says exactly what is the problem, if they know our filter criteria from our API call, why are they querying the database in such a way that they are not using it in the query itself and applying the filter AFTER getting database results, giving this poor API experience. That's a benefit of databases, is to let them do the heavy lifting with your predicates, not apply them after the fact. So this answer only seems to reinforce my concern with the design issues of the API. Why even offer an API if its so inflexible that the answer is to copy all the data locally and avoid using the API?

xceled · ‎07-23-2021

The main issue I am running into is with the "Get Lead Activities" API: https://developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#!/Activities/getLeadActivitiesUsingGET For example, if I request all of the interesting moments from the past 90 days for a single lead, it takes 14 calls to the API passing new "nextPageToken" until there are no longer "moreResult" = true responses from Marketo. This is extremely slow, in our testing, takes about 28 seconds. In my first request, I pass a nextPageToken that is set at 90 days ago, and for my test Lead with id 835054, they have 2 interesting moments in that time period. So the result set is much less than 300, which is the total max batch size returned in a single response. So a single response should be able to return all Interesting Moment activities for this lead in the last 90 days. However it appears the Marketo implementation is not paginating by the batchSize parameter, but instead by some arbitrary period of time represented by each "nextPageToken". This design approach causes the performance issue by requiring us to execute 14 API calls in what could be returned in 1. 12 of these API calls return no data, that's 12 wasted calls against our API quota in addition to the processing time this adds. Need help to understand if there is anything we can do on our side, using the Marketo REST API, to improve this performance or if there needs to be a design change/enhancement to this API so that it paginates by returned row count, rather than arbitrary time periods. Marketo seems to have a less limited/better implementation they use on their own UI as they can return this Leads activities in a single call. So not sure why customers are only given the option to this extremely limited API.

xceled · ‎07-07-2021

When passing token data using the RequestCampaign API call, are there any field length limits on the values for the token types 'Rich Text' or 'Text'? Or any other restrictions on the API call that may restrict the amount of data passed via the tokens? Tokens are in the request body at the path: TriggerCampaignRequest>TriggerCampaignData>tokens https://developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#!/Campaigns/triggerCampaignUsingPOST

Online Status	Online
Date Last Visited	15m ago

Date Registered	‎07-07-2021 10:19 AM
Date Last Visited	15m ago
Total Messages Posted	9

Top Badges Earned

Bulk Export for Activities - "Attributes" property...

Re: API Documentation - How to find out max field ...

Request Campaign REST API - Generic approach with ...

API Documentation - How to find out max field leng...

Marketo -> Dynamics - Sync Lead Id

Re: Get Lead Activities - Design issue, performanc...

Re: Get Lead Activities - Design issue, performanc...

Get Lead Activities - Design issue, performance un...

API Question, RequestCampaign - Token Character Li...