Connector Improvement: Amazon Attribution change detection
We have discovered that when a campaign is renamed in Amazon, the connector neither removes nor corrects the data in our destination DB; instead it synchronizes all the data under the new campaign ID as if it was new data, which results in duplicates in our destination DB (the same data is duplicated in both an old campaign ID and a new campaign ID).
Can the connector be improved in some way to rectify this situation?
Please sign in to leave a comment.
Comments
0 comments