Program Member Status Changes via Bulk Import API - Logs are overrun with unchanged status logs

jkimexperience · ‎03-21-2022

Hello -

My Company (app.experiencewelcome) has written an integration via Tray.Io with Marketo and our platform (events platform).

We send Program Member Status Updates back to the Marketo platform from ours when triggered by a webhook.

We've noticed recently, approximately since the beginning of the year, that Marketo's logs are getting drowned by Skipped Status Unchanged logs when hitting a Program Member's Status that is the same value that is currently stored.

I've looked at the API update notes, but don't see anything regarding bulk import that may cause this to occur.

Are there any tips anyone can offer so that I do not hit my customers with thousands of redundant logs per day?

Below is the input

{
"method": "POST",
"query_parameters": [
{
"key": "format",
"value": "csv"
},
{
"key": "programMemberStatus",
"value": "Registered"
}
],
"body": {
"form_data": {
"file": {
"name": "registered_csv.csv",
"url": "https://tray-csv-file-processing.s3.us-west-2.amazonaws.com/exports/abd412b1-9b1d-4ce4-9bd8-db57d55541aa.part_00000?AWSAccessKeyId=ASIAWLUGWV6AKLVSXM2R&Expires=1647962801&Signature=4627mNn9o2jNWSqucPE3HXRSD0o%3D&response-content-disposition=attachment%3B%20filename%3D%22registered_csv.csv%22&x-amz-security-token=xxxxc",
"mime_type": "text/csv",
"expires": 1647962801
}
}
},
"client_secret": "5b... <**--removed--**>",
"parse_response": "true",
"url": {
"full_url": "https://958-TTM-744.mktorest.com/bulk/v1/program/2748/members/import.json"
},
"client_id": "c0... <**--removed--**>",
"include_raw_body": false,
"endpoint": "ht... <**--removed--**>",
"quota_wait": false

SanfordWhiteman · ‎03-24-2022

Interesting point. I figured the “webhook” in question wasn’t a Marketo webhook but rather one fired from the 3rd-party platform to an (also 3rd-party) integration tier. If it’s a Marketo Call Webhook then it couldn’t know when someone needed updating.

But still, the other platform would know. There’s no reason to be setting a status that you know in advance will be skipped, because you’re the only one controlling the status.

On the other hand, sometimes Smart Campaigns are also changing statuses, so when setting via API we try for the one we want: if it’s the current one, no problem, and if it’s a previous one, also no problem as it means the person has been moved along.

Also, not clear why the Bulk Import API would be used for a single lead, if it’s really one-by-one. (Not that there’s anything specifically wrong with using the bulk APIs for single rows, except you don’t get a synchronous response.)

View solution in original post