Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Amazon Attribution change detection

Answered
Nick McAlpin User

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

1 comment

Date Votes
  • Official comment
    Lucas Alexander Fivetranner

    Hi Nick,

    Luke from the Product team here. Thanks for submitting this request.

    We use the campaign_id as a primary key. I don't know how we can detect that Amazon changed the campaign ID of an existing campaign vs. a new campaign exists in Amazon with a new campaign_id. 

    If you think this was caused by an issue in our connector logic, please open a ticket with our support team. They can request access to your connector and compare the data from the source to what's being written to your destination. That will help us determine whether there is an issue with our connector.

    Thanks!
    Luke