🚨🚨🚨 fix(source-linkedin-ads) updated pk for ad_campaign_analytics and custom reports (#48451)

Co-authored-by: maxi297 <[email protected]>

Author: darynaishchenko

airbyte-integrations/connectors/source-linkedin-ads/metadata.yaml

@@ -11,7 +11,7 @@ data:
   connectorSubtype: api
   connectorType: source
   definitionId: 137ece28-5434-455c-8f34-69dc3782f451
-  dockerImageTag: 4.1.4
+  dockerImageTag: 5.0.0
   dockerRepository: airbyte/source-linkedin-ads
   documentationUrl: https://docs.airbyte.com/integrations/sources/linkedin-ads
   githubIssueLabel: source-linkedin-ads
@@ -87,6 +87,10 @@ data:
               - "creatives"
               - "campaign_groups"
               - "conversions"
+      5.0.0:
+        message: We would like to inform you that the Primary Key (PK) for ad_campaign_analytics and Custom Ad Analytics Reports streams has been changed from [string_of_pivot_values, end_date] to [string_of_pivot_values, end_date, sponsoredCampaign] and Primary Key (PK) for account_users stream has been changed from [account] to [account, user]. This update is intended to improve data integrity and ensure optimal performance. Upgrade LinkedIn Ads to apply these changes immediately. Otherwise, LinkedIn Ads will be upgraded automatically on 2024-12-10.
+        upgradeDeadline: "2024-12-10"
+        deadlineAction: "auto_upgrade"
   suggestedStreams:
     streams:
       - accounts

airbyte-integrations/connectors/source-linkedin-ads/pyproject.toml

@@ -3,7 +3,7 @@ requires = [ "poetry-core>=1.0.0",]
 build-backend = "poetry.core.masonry.api"
 
 [tool.poetry]
-version = "4.1.4"
+version = "5.0.0"
 name = "source-linkedin-ads"
 description = "Source implementation for Linkedin Ads."
 authors = [ "Airbyte <[email protected]>",]

airbyte-integrations/connectors/source-linkedin-ads/source_linkedin_ads/manifest.yaml

@@ -55,6 +55,7 @@ definitions:
       name: account_users
       primary_key:
         - account
+        - user
       retriever:
         type: SimpleRetriever
         requester:
@@ -387,6 +388,7 @@ definitions:
       primary_key:
         - string_of_pivot_values
         - end_date
+        - sponsoredCampaign
       retriever:
         class_name: "source_linkedin_ads.components.LinkedInAdsCustomRetriever"
         requester:

docs/integrations/sources/linkedin-ads-migrations.md

@@ -1,5 +1,40 @@
 # LinkedIn Ads Migration Guide
 
+## Upgrading to 5.0.0
+
+With LinkedIn Ads v5.0.0, we modified primary keys for stream(s): `ad_campaign_analytics`, `Custom Ad Analytics Reports`, `account_users`.
+
+This enhances data integrity and improves the efficiency of your syncs. Users with deduping enabled on those streams might have missing data as records would have been collapsed on the wrong primary key. We highly recommend initiating a connection refresh to ensure all the data is available in the destination.
+
+- `ad_campaign_analytics`
+- `Custom Ad Analytics Reports`
+
+| Old PK                               | New PK                                                  | 
+|:-------------------------------------|:--------------------------------------------------------|
+| `[string_of_pivot_values, end_date]` | `[string_of_pivot_values, end_date, sponsoredCampaign]` | 
+
+- `account_users`
+
+| Old PK      | New PK            | 
+|:------------|:------------------|
+| `[account]` | `[account, user]` | 
+
+## Migration Steps
+
+Clearing your data is required for the affected streams in order to continue syncing successfully. To clear your data 
+for the affected streams, follow the steps below:
+
+1. Select **Connections** in the main navbar and select the connection(s) affected by the update.
+2. Select the **Schema** tab.
+   1. Select **Refresh source schema** to bring in any schema changes. Any detected schema changes will be listed for your review.
+   2. Select **OK** to approve changes.
+3. Select **Save changes** at the bottom of the page.
+   1. Ensure the **Clear affected streams** option is checked to ensure your streams continue syncing successfully with the new schema.
+4. Select **Save connection**.
+
+This will clear the data in your destination for the subset of streams with schema changes. After the clear succeeds, 
+trigger a sync by clicking **Sync Now**. For more information on clearing your data in Airbyte, see [this page](/operator-guides/clear).
+
 ## Upgrading to 4.0.0
 
 Version 3.X.X introduced a regression in the connector that was reverted in 4.0.0. If you were using 3.X.X, please go through the migration steps. If you were still using 2.X.X, please upgrade to 4.0.0; after that, there are no additional actions required.