Last reviewed Sep 6, 2026
If the same real-world campaign shows up as two separate records in Launches, this is almost always the result of two different Scan findings being confirmed independently, rather than a system error.
How to fix it
- Identify which record has more complete or more recent activity; this is usually the one to keep.
- If you haven't confirmed the duplicate yet and it's still a Scan finding, merge it into the existing campaign instead of confirming it separately. See Merging a finding into an existing campaign.
- If both are already confirmed campaign records, contact support to have them merged, since merging two existing launch records isn't currently a self-serve action.
Preventing it next time
Preventing this going forward usually comes down to reviewing Scan's confidence and suggested matches carefully before confirming a new finding. See How Scan avoids creating duplicate campaigns.