Marketing / Advertising Integration β Automated Account Resync
Zenoti automatically resyncs Meta and Google advertising integration accounts on a scheduled basis. This article explains how the automated resync pipeline works, what happens when individual account groups fail, how to trigger a manual Post-lock Variance Snapshot sync, and how to verify that resync is running correctly for your organization.
Audience: Organization administrators who manage Meta or Google advertising integrations.
Before you begin
- Your organization must have an active Meta or Google advertising integration configured under Configuration > Integrations > Integration settings.
- Confirm with your administrator which resync mode is active for your organization β MetaAccount or GoogleAccount β so you know which platform's accounts are being processed in the current run.
- You do not need to take manual action to trigger a resync for most operations. The pipeline runs automatically on a schedule. This article helps you understand the behavior, interpret outcomes, and use the manual sync options when needed.
How automated account resync works
Resync pipeline overview
The automated resync pipeline processes Meta and Google integration accounts independently. Each run operates in one of two modes:
- MetaAccount β processes only accounts linked to your Meta advertising integration
- GoogleAccount β processes only accounts linked to your Google advertising integration
Accounts whose platform does not match the active resync mode are skipped in that run. This ensures each platform's accounts are handled cleanly without interference from the other.
How accounts are grouped for resync
Rather than submitting one resync request per account, Zenoti groups accounts by organization, level, and integration before submitting. A single batch call covers all eligible accounts for a given tenant context.
For example, if your organization has ten Meta ad accounts associated with the same integration, they are bundled into one batch resync request rather than ten separate calls. This reduces unnecessary traffic and ensures consistent handling across accounts in the same context.
How failures are handled
If a resync request fails for a group of accounts, Zenoti logs the failure with the integration ID and the error message. Processing then continues for the remaining account groups β a single failure does not stop the entire run.
This means:
- Other account groups in the same run are not affected by one group's failure.
- You can review failure details in your integration logs to identify which integration ID encountered an error and what the error message was.
- If a group consistently fails, contact Zenoti Support and provide the integration ID and the error details from the logs.
Note: The resync pipeline runs on a managed schedule. You cannot manually trigger a resync from the Zenoti interface for advertising integrations. If you need a resync outside the normal schedule, contact Zenoti Support.
Steps
Verify your advertising integration is active
- Navigate to Configuration > Integrations > Integration settings.
- Locate and expand the Marketing or advertising integration accordion for Meta or Google.
- Confirm the integration is enabled and that your account credentials are current.
Important: If credentials have changed or expired, update them before the next scheduled resync. Stale credentials will cause all account groups under that integration to fail resync.
Check whether resync ran for your accounts
Because resync runs automatically, you verify outcomes rather than triggering the process yourself.
- After a resync is expected to have run, navigate to your integration logs or the monitoring surface available to your organization.
- Look for entries associated with your Meta or Google integration ID.
- Confirm that log entries show successful batch calls for your account groups.
- If you see failure entries, note the integration ID and error message reported in the log for each failed group.
Respond to a failed resync group
- Identify the integration ID and error message from the failure log entry.
- Verify that your integration credentials under Configuration > Integrations > Integration settings are valid and have not expired.
- If credentials are valid and the error persists across multiple scheduled runs, open a support ticket with Zenoti Support. Include:
- The integration ID from the failure log
- The error message text
- The approximate time the failure occurred
- Do not wait for Zenoti Support to re-enable resync for unaffected account groups β the pipeline continues processing other groups automatically.
Run a Post-lock Variance Snapshot manual sync
The Manual Sync panel in the accounting integration includes a Post-lock Variance Snapshot action. Use this when you need to rebuild variance data for a specific date after a financial lock has been applied.
- Navigate to Configuration > Integrations > Integration settings.
- Locate and expand the accounting integration accordion.
- Select the Manual Sync tab.
- Locate the Post-lock Variance Snapshot row in the manual sync options.
- Use the Choose a date date picker to select the date for which you want to rebuild the post-lock variance snapshot.
- Select Post to trigger the sync operation for the chosen date.
Note: The Post-lock Variance Snapshot action rebuilds variance data for the selected date. Run this only for dates where a financial lock is in place and a variance discrepancy has been identified. Selecting an incorrect date may produce misleading variance records.
Tip: For general information about accounting sync schedules and other manual sync options, see Configure accounting sync schedules.
Tips
- Each advertising run processes only one platform. If you manage both Meta and Google integrations, expect separate runs for each. Do not assume a single run covers both platforms.
- Batch grouping reduces load but also groups failures. If one account in a group has a configuration issue, the entire group's batch call may fail. Verify that all accounts in an integration are consistently configured.
- Keep credentials current. Expired or revoked credentials are the most common cause of resync failures. Review your Meta and Google advertising integration credentials on a regular schedule, especially after password rotations or permission changes on the advertising platform side.
- Failure isolation protects other groups. A failed batch for one organization-level-integration group does not affect other groups in the same run. You can confirm this by checking that other groups show successful log entries even when one group fails.
- Use Post-lock Variance Snapshot only for locked dates. This manual sync action is designed specifically for dates where a financial lock is active. For unlocked dates, use the standard accounting sync options instead.
Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
| No log entries appear for your integration after a scheduled resync window | The active resync mode does not match your platform (for example, the run used MetaAccount mode but your accounts are Google) | Confirm which resync mode is active for the current schedule with Zenoti Support |
| Log entries show failures for all account groups under an integration | Credentials for that integration have expired or been revoked | Update your integration credentials under Configuration > Integrations > Integration settings, then wait for the next scheduled run |
| One account group fails repeatedly while others succeed | That specific integration ID has a configuration mismatch or permission issue on the advertising platform side | Note the integration ID and error message, verify platform-side permissions, and contact Zenoti Support if the issue persists |
| Resync completed but advertising platform does not reflect updated data | Propagation delay on the advertising platform side | Wait for the advertising platform's standard propagation window; if data does not appear after 24 hours, contact Zenoti Support with the integration ID |
| You need a resync outside the normal schedule | No self-service trigger exists for advertising integration resyncs | Contact Zenoti Support and provide the integration ID and the reason for the out-of-cycle request |
| The Post button in Post-lock Variance Snapshot produces no visible result | The selected date may not have a financial lock applied, or the accounting integration is not fully configured | Verify that a financial lock is active for the selected date; confirm your accounting integration credentials and mapping are complete |