Distinguishing between API web services in Activity log

[Anonymous]

We have marketo syncing with a FileMaker database through a lot of custom scripting.

Part of the custom scripting is getting lead data changes through the activities API and updating our database accordingly. 

One problem I've run into is that we don't want to have changes that were pushed up from the FileMaker database to Marketo to then be written back down to the FileMaker database again when we are going through the lead activity.

The FileMaker database is not the only thing connecting and making changes through the Web API.  However, both the "Reason" and "Source" attributes for the activity simply say "Web Service API".  This isn't enough information to filter our the changes from FileMaker.

Is there any way to set up a system to be able to tell where the Web Service API changes are coming from?  A setting, custom activity, or whatever?

[SanfordWhiteman]

Which REST API endpoint are you using to write data?

[Anonymous]

leads.json through the REST api.

[SanfordWhiteman]

You should switch to the Push Lead (/push.json) endpoint, which lets you include a call-specific source and reason with the payload.

[Anonymous]

I tried that, and the activity where the change is recorded still lists the source and reason as "Web service API".  Only when I go into the activity log for the lead through the website ui do I see that there is a seperate activity log that says that there was a push, but it does not say what data was changed in that separate log.