Introduction
Marin 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 Ads Editor, a sync with our application is required in order to update the data.
Handy Tip
This article is specific to syncing changes to Marin from the publishers. To learn more about posting changes from Marin to the publisher, please read our dedicated help center article.
Why Synchronization Matters
It is important that campaign settings in our application are closely matched to those set within the publisher.
For example, if a bid has been changed at the publisher, but our application contains the old bid, our bidding algorithm will execute using settings and details for the old bid. This means that the application could possibly suppress a valid bid change or push out a bid change based on compromised data. As another example, if a Microsoft campaign is active within our application and is deleted or expired within Microsoft itself, any changes our application attempts to make to that campaign, or items within it, will be rejected by Microsoft.
We encourage you to make your campaign management changes using our application. Following the methods outlined below will ensure that changes will be properly recorded.
Bringing Publisher Changes Into Marin
There are two ways to ensure that any changes made directly with publishers are reflected in our application: Manual Sync and Automatic Nightly Sync. We will outline each of these below.
Manual Sync (Also Known As Hard Sync)
Once you have made changes in the publisher, if you would like these settings to be immediately reflected in Marin, you can do this through a manual sync.
To learn how to perform a manual sync, check out our dedicated article.
Note: Sync updates will only change an object's attributes or settings (keyword, campaign, creative, group); metrics are not changed. If metrics within our application do not reconcile with those at the publisher, contact our Customer Support department for assistance.
Automatic Nightly Sync
The Automatic Nightly Sync is also known as Sync-From-Cost-Reports. This automated sync occurs by comparing objects in our application versus those that show up in the Nightly Cost Reports and looking for discrepancies in status or values. The cost reports are downloaded on a nightly basis to obtain the previous day's publisher metrics (impressions, clicks), and contain keywords and creatives that received impressions.
Note: Cost data for publisher accounts will be ready by 9 a.m. local account time. E.g. if the account is PST (GMT-8) it will have data ready by 9 a.m. local time which is 17:00 GMT.
During the Automatic Nightly Sync, keywords and creatives are updated with the newest bids, quality scores, and destination URLs found in the Nightly Cost Reports. If a new keyword or creative is identified, or a bid change is ambiguous, Marin will sync the entire group level to ensure symmetry with the publisher. For example, if a keyword bid is changed in the cost report and now matches the group bid stored in Marin, it is unclear whether the keyword bid should be updated or if this keyword is now using the group bid. In this case, Marin will perform a group sync. Alternatively, if Marin identifies a new keyword bid that does not match the group bid, it will update the keyword bid directly within the application without initiating a group sync.
Note: Any items in Marin in the To be sent status will be pushed overnight at some point after 8 p.m. in the account time zone.
Important Notes About Syncing
- If a campaign has no clicks and impressions, as a best practice, budgets and other changes made in the publisher account should always be hard synced to ensure they are brought into Marin.
- The syncing process will never perform any create operations within the publisher, it will only ever pull in changes to Marin. If you see changes made by the System user, it's likely that this is the result of Marin syncing with the publisher. Find out more about the System user.
- If you're concerned about a change made in Marin and who made it, it's a good idea to hover over the object in the grid until you see the three dots icon. Click on this icon and select Settings History from the drop-down. Here you'll be able to see all recent changes and which user made them.
- To check that your campaigns and/or groups are syncing, navigate to the Campaigns and/or Groups view, and click the filter icon in the Operation Status column (next to the checkboxes in the grid, indicated by a Flag icon) and select the Syncing operation status. Look at the number of objects for this filter, and refresh the view after a few minutes. As the sync is processing, the number of objects for this filtered view should drop over time.
- Marin's default minimum bid change is 15 cents. Any bid change below 15 cents will not be updated through the nightly sync and will need to be synced manually.
- For Upgraded or Advanced URL fields in Microsoft and Yahoo! Japan, you will need to have opted into the corresponding betas before syncing can begin. Please reach out to your Marin account representative to opt into these betas.
- For Baidu, Marin will only sync the changes of "Active" campaigns made in the publisher console.
When And How Changes Are Synced To Marin
KEY | DESCRIPTION |
---|---|
daily | Synced daily |
impressions | Synced only with impressions |
hard sync | Hard sync only |
n/a | Not applicable |
CAMPAIGN | Y! Gemini | Microsoft | CRITEO | Yahoo! JAPAN | |
---|---|---|---|---|---|
Deleted | daily | n/a | daily | daily | daily |
Rename | daily | impressions | daily | daily | daily |
Status: Activated | daily | n/a | daily | daily | daily |
Status: Paused | daily | n/a | daily | daily | daily |
Status: Deleted | daily | n/a | daily | n/a | daily |
Attribute: End Date | daily | n/a | n/a | n/a | daily |
Attribute: Budget | daily | n/a | daily | daily | daily |
Attribute: Distribution | daily | impressions | daily | n/a | daily |
Negative Keywords | daily | n/a | daily | n/a | daily |
Ad Targeting | daily | n/a | n/a | n/a | daily |
Geo-Targeting | daily | n/a | daily | n/a | daily |
Language Targeting | daily | n/a | n/a | n/a | n/a |
Bid Settings: CPC vs. CPM | daily | impressions | n/a | n/a | n/a |
Device Targeting | daily | n/a | daily | n/a | daily |
Tracking Template | daily | n/a | daily | n/a | daily |
Custom Parameters | daily | n/a | daily | n/a | daily |
GROUP | Y! Gemini | Microsoft | CRITEO | Yahoo! JAPAN | |
---|---|---|---|---|---|
New | daily | impressions | impressions | impressions | impressions |
Status: Deleted | daily | n/a | hard sync | hard sync | hard sync |
Rename | daily | impressions | impressions | impressions | impressions |
Status: Activated | hard sync | n/a | impressions | impressions | impressions |
Status: Paused | hard sync | n/a | hard sync | hard sync | hard sync |
Group Search Bid | daily | n/a | hard sync | hard sync | hard sync |
Group Content Bid | n/a | impressions | hard sync | n/a | n/a |
Negative Keywords | hard sync | n/a | hard sync | n/a | hard sync |
Ad Targeting | n/a | n/a | hard sync | n/a | n/a |
Geo-Targeting | n/a | n/a | hard sync | n/a | n/a |
Language Targeting | n/a | n/a | hard sync | n/a | n/a |
Attribute: Distribution | n/a | impressions | hard sync | n/a | n/a |
Tracking Template | daily | n/a | hard sync | n/a | hard sync |
Custom Parameters | daily | n/a | hard sync | n/a | hard sync |
KEYWORD | Y! Gemini | Microsoft | CRITEO | Yahoo! JAPAN | |
---|---|---|---|---|---|
New | daily | impressions | impressions | n/a | impressions |
Status: Deleted | daily | n/a | hard sync | n/a | hard sync |
Status: Activated | daily | n/a | impressions | n/a | hard sync |
Status: Inactive | hard sync | n/a | n/a | n/a | hard sync |
Status: Paused | hard sync | n/a | hard sync | n/a | hard sync |
Destination URL | n/a | impressions | hard sync | n/a | hard sync |
Landing Page | daily | n/a | impressions | n/a | impressions |
Mobile Landing Page | daily | n/a | impressions | n/a | impressions |
Tracking Template | daily | n/a | impressions | n/a | impressions |
Custom Parameters | daily | n/a | impressions | n/a | impressions |
Keyword Search Bid | daily | impressions | impressions | n/a | hard sync |
Keyword Minimum Bid | daily | n/a | n/a | n/a | hard sync |
Pending | n/a | n/a | hard sync | n/a | hard sync |
Quality Score | daily | n/a | n/a | n/a | n/a |
CREATIVE | Y! Gemini | Microsoft | CRITEO | Yahoo! JAPAN | |
---|---|---|---|---|---|
New | daily | impressions | impressions | n/a | impressions |
Status: Deleted | daily | n/a | hard sync | n/a | hard sync |
Status: Activated | daily | impressions | impressions | n/a | hard sync |
Status: Paused | daily | impressions | hard sync | n/a | hard sync |
Attribute: Any Text | daily | n/a | n/a | n/a | n/a |
Destination URL | n/a | n/a | n/a | n/a | n/a |
Landing Page | daily | n/a | impressions | n/a | impressions |
Mobile Landing Page | daily | n/a | impressions | n/a | impressions |
Tracking Template | daily | n/a | impressions | n/a | impressions |
Custom Parameters | daily | n/a | impressions | n/a | impressions |
Approval Status | daily | n/a | impressions | n/a | impressions |
PLACEMENTS | Y! Gemini | Microsoft | CRITEO | |
---|---|---|---|---|
New | daily | n/a | n/a | n/a |
Status: Deleted | hard sync | n/a | n/a | n/a |
Status: Activated | daily | n/a | n/a | n/a |
Status: Inactive | hard sync | n/a | n/a | n/a |
Status: Paused | hard sync | n/a | n/a | n/a |
Destination URL | daily | n/a | n/a | n/a |
Landing Page | daily | n/a | n/a | n/a |
Mobile Landing Page | daily | n/a | n/a | n/a |
Tracking Template | daily | n/a | impressions | n/a |
Custom Parameters | daily | n/a | impressions | n/a |
Placement Content Bid | daily | n/a | n/a | n/a |
Placement Minimum Bid | daily | n/a | n/a | n/a |
PRODUCT GROUPS | MICROSOFT | |
---|---|---|
New (active or excluded) with no impressions | hard sync | hard sync |
Status: Deleted / Subdivided | daily | impressions |
Status: Active | daily | impressions |
Status: Excluded | daily | impressions |
Tracking Template | daily | n/a |
Custom Parameters | daily | n/a |
Destination URL | n/a | impressions |
Important Information About Publisher Synchronization
- Please note that if you have exceptionally large campaigns, the synchronization may likewise take an exceptionally long time. If you see the Sending Now status message for longer than usual, please first check that these campaigns are not simply very large and taking a while to process. Processing time can be upwards of 10 hours for very large campaigns.
- Note that, for Google and Microsoft campaigns, we synchronize all sitelinks on a daily basis. This is not the case for publishers other than Google and Microsoft.
- If objects are deleted in the publisher and do not exist in Marin, the system cannot sync down these objects and their corresponding data.
- Discrepancies between Marin and the publisher can occur if you make changes in the publisher without syncing them into Marin (either because that object is paused and we did not pull it in with the cost report or because the change required a manual sync). This scenario can cause confusion, which is why we recommend only making your edits through Marin.
- Marin cannot sync down cost data from the publisher for deleted objects.
- Triggering a Manual Sync for campaigns or groups in the To Be Sent or Held statuses will overwrite any pending changes for these objects which already exist in the Activity Log. However, the corresponding jobs for these pending changes in the Activity Log will still be visible. That said, and even though the option to post this job to the publisher is available, selecting it will actually result in no changes on the publisher's side.