Summary
Conflicts happen when campaign data in Hunch does not match data in Meta. This guide explains how to spot these discrepancies, choose the correct values, and keep both platforms in sync so your campaigns run as intended.
How It Works
Conflicts occur when Hunch values differ from those in Meta Ads Manager. This may happen due to direct edits in Meta, automatic Meta updates, or sync delays. Hunch flags these mismatches with a conflict indicator and lets you decide whether to update Hunch with Meta’s values or overwrite Meta with Hunch’s values.
Before You Begin
Ensure you have edit permissions for the affected campaigns.
Have access to both Hunch and Meta accounts.
The campaign must be in a published or active state.
Be aware of recent changes made to the campaign.
Step-by-Step Instructions
Identifying Conflicts
Open the Campaign Insights module.
Locate the Conflicts section in the campaign table.
Click the conflict indicator to view details.
Resolving Conflicts
Review the campaigns with conflicts.
For each conflict, choose to keep the Meta value or the Hunch value.
Confirm your choice using the provided options.
Wait for the confirmation message before proceeding.
Preventing Future Conflicts
Make edits in Hunch whenever possible and avoid making changes directly in Meta unless necessary. If you do edit in Meta, refresh Hunch data immediately afterward.
Use Cases
Budget changes in Meta: Accept the Meta value to sync with Hunch.
Scheduled changes in Hunch not applied to Meta: Push Hunch’s values to Meta.
Multiple team edits: Decide which changes to keep based on priority.
FAQs
Q: How quickly are conflicts detected?
Usually within 5–10 minutes, depending on sync frequency.
Q: Can I ignore a conflict?
Yes, but it may cause campaign issues later.
Q: What if I choose the wrong value?
Check the activity log and manually adjust if needed.
Q: Why do conflicts occur if I only use Hunch?
They can still happen due to Meta optimizations or sync delays. Contact support if they persist.
Q: Can conflicts affect performance?
Yes. Resolve them promptly to avoid unintended settings.
Q: Are conflict resolutions logged?
Yes, all resolutions are recorded in the campaign activity history.