1 of 1 people found this helpful
FYI I haven't looked to see if I am experiencing this problem but I found the most effective way to sync the data is to use the latest activity_at for the since. So instead of storing the time cursor, you actually query for the latest time by activity type id and thats what you use. I think this might be better because I assume Marketo is syncing these roughly in time order.
Not a bad idea, assuming Marketo does indeed write the data in time order. If I go that route, I think I would still factor in a buffer just to make sure.
I really think they should provide a parameter that is linked to the timestamp that the activity records are written to their database (like an insert_date_time). I would be guaranteed to get all records that way regardless of how they sync the data.