The Marin Platform stores its own copy of each client's campaign structure separate from the publisher. When changes are made within the application, they must be synchronized with the content in the publishers' databases in order to achieve symmetry in both locations.
After making changes to campaigns using the application, you have the option to send changes to the publisher immediately, or wait until the application automatically sends them via its nightly sync with each publisher.
Similarly, our application must be kept in sync with changes that are made directly within the publisher. If changes are made in a publisher-specific editing tool such as Google AdWords Editor, a sync with our application is required in order to update the data.
This article will explain how to post changes from the Platform to the publishers. To find out out more about syncing changes to the Platform from the publisher, please read our Support article on that topic.
Local edits within the application are denoted by a blue pencil icon.
Once an edit has been made, the number of changes, as well as the option to post those changes, will become visible on tabs at the top right of the application. Changes made in the application are then queued up into the Activity Log.
From the Activity Log, you can:
Note: You cannot cancel a job once it has been posted.
If no action is taken, the changes will be queued as To Be Sent and pushed to the publishers in the application's nightly synchronization process at 8:00pm local time. However this can be delayed pending on other processes like bidding jobs. Any errors incurred, including errors made within the application and errors sent back by the publisher, will also be posted on this page.
Note: If you load a file into the account that contains objects and object details that already exist in the Platform and the publisher, there will be no corresponding child operation to be posted to the publisher. The reason is because there are no actual changes to be made on the publisher's end.
To post all pending changes, those with a To Be Sent status, use the Post All Now button in the upper right.
To post specified activities, check those items and choose the Post Now button.
To hold an item, simply check the items and use the Hold button. Held items are so noted in their status field.
To cancel an item, simply select the items and click Cancel. Note: You cannot cancel a job once it has been posted.
The Activity Log can accumulate a large number of records, as it displays several weeks of publisher interactions. You can narrow down what you are looking for based on its current status, the user who created the change, or the date, by adjusting the filters on the left side of the page.
Most errors will be visible in the Activity Log as they occur. However, some errors can only be detected after changes have been posted to the publisher. This process happens in the background.
Note: You can also check for errors by clicking on the red triangle sync error icon next to any object in the grid. This will take you to the Activity Log operation and will display the error in question.
For the quickest resolution, most errors found in the Activity Log can be searched for and resolved using the Support Center.
The last change made to the same object in the application will prevail within the publisher. For example, if a keyword's destination URL is modified in the application at 1 PM and was not immediately pushed out, and the same URL was modified again at 2 PM, the 2 PM modification would be sent to the publisher. Additionally, pushing a change from our application to the publisher will overwrite a value that was made directly in the publisher's UI.
As an example, if a campaign's end date is set to January 20, 2020 in Google AdWords and then changed to February 10, 2020 in the application, the two entities will be out of sync. Synchronizing changes from AdWords (manually or automatically), will overwrite the change made in the application. However, if the change is sent to the publisher via the application, it will overwrite the change at the publisher.
Here are the possible statuses that an object may display:
| Status | Definition |
| Succeeded | Operation was successful. |
| Succeeded partially | For bulk actions, a portion of the operation was successful. A portion of the operation failed. |
| Failed | Operation failed. Click on the cart operation number or the bulk file to view error messages. |
| Processing | For bulk actions, the application is processing the file and creating appropriate publisher operations. |
| To be sent | Operation is waiting to be sent to the publisher. All To be sent operations will be sent at the end of every day. |
| Sending Now | Operation is in the process of posting to the publisher. The application will display the % complete which is updated as the operation is processing. |
| Queued | If multiple operations are posted to the publisher, only one will be sending at any given time. The other operations will be queued and processed as operations complete. |
| Canceled | Operation has been canceled by the user. |
| Held | Operation has been held by the user. Operation will be held indefinitely until user manually posts to the publisher. Please be aware that scheduled activities, such as URL Autocorrect, Scheduled Actions, and Bidding may override items in held status. An item in held status is overridden when the schedule activity makes a change to the same item. |
