@kapa.ai Dropping fields from ASA keywords (insights or keywordId or other) will cause incremental | append sync mode not working ?

Based on the knowledge sources, I can address this partially. Yes, dropping or renaming fields (schema changes) in your source table can cause issues with Incremental - Append sync mode in Airbyte. The documentation explicitly states: > "The current behavior of Incremental is not able to handle source schema changes yet, for example, when a column is added, renamed or deleted from an existing table etc. It is recommended to trigger a [Full refresh - Overwrite] to correctly replicate the data to the destination with the new schema changes." [Incremental Append - Known Limitations] Additionally, there is a specific concern around the cursor field: if the field being dropped or modified is the cursor field (e.g.,

keywordId

or another field used as the cursor), incremental sync will not work correctly, since the source connector uses a query like:

SELECT * FROM table WHERE cursor_field >= 'last_sync_max_cursor_field_value'

[Incremental Append - Known Limitations] However, the knowledge sources do not contain specific information about ASA (Apple Search Ads) keywords or its `insights`/`keywordId` fields in particular. I cannot confirm connector-specific behavior for that source beyond the general Airbyte incremental sync limitations described above. Recommendation: If you've dropped or changed schema fields in your source, it is advised to perform a Full Refresh - Overwrite sync to re-establish a correct baseline before resuming incremental syncs. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai Could I only do specific data period to see if it works?

Based on the knowledge sources, yes — you can configure a specific date range for your sync to test if it works correctly. When setting up incremental sync in Airbyte's Connector Builder, you can specify: • Start datetime – Set a specific past date to begin syncing from (e.g.,

2023-04-09T00:00:00Z

) • End datetime – Set a specific end date, or use

now

to sync up to the current time For example, setting a start date in the "Testing values" will result in a request like:

curl 'https://your-api.com/endpoint?from-date=2023-04-09T00:00:00Z&to-date=<now>'

[Incremental Sync Example] This way, you can limit the sync to a small, specific time window to verify that the connector is working as expected before running a full sync. Additionally, if you want a rolling lookback window (e.g., always re-sync the last N days), you can configure the Lookback window setting, which subtracts a duration from the last cutoff date before starting the sync. [Lookback Window] However, the knowledge sources do not contain specific details about the ASA (Apple Search Ads) connector's configuration UI, so I cannot confirm the exact steps for that particular connector. The general approach above applies to connectors built with the Connector Builder. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai but you are suggesting me to use Full Refresh - Overwrite sync

You're right to point that out. Let me clarify the distinction: Full Refresh - Overwrite was suggested specifically for the schema change scenario (when columns are added, renamed, or deleted). The Airbyte documentation recommends it as a one-time corrective action to re-establish the correct schema in the destination after a schema change has occurred. [Incremental Append - Known Limitations] It is not a long-term replacement for Incremental - Append if that's your preferred sync mode. The typical workflow would be: 1. Trigger a Full Refresh - Overwrite once to correct the destination table after the schema change. 2. Resume Incremental - Append syncs going forward, now that the schema is aligned. Regarding your previous question about testing with a specific data period — that approach is more relevant to verifying that your incremental sync is picking up records correctly after the fix, rather than as a substitute for the Full Refresh step. That said, the knowledge sources do not contain enough detail about the ASA (Apple Search Ads) connector specifically to confirm whether there are any connector-level constraints that might affect this workflow. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai so when I do the testing, I use Full Refresh - Overwrite to test a specific period, and compare with my current Incremental - Append data ?

Based on the knowledge sources, I can partially address this approach, but I want to be precise about what the documentation actually supports. What the docs say about Full Refresh - Overwrite: • It replaces/overwrites whatever data exists in the destination with the data from the current sync. [Sync Modes] This means if you run a Full Refresh - Overwrite, it will replace your existing destination data — so you wouldn't be able to directly compare it side-by-side with your current Incremental - Append data in the same table, since the overwrite would replace it. A more cautious approach would be: • Use Full Refresh - Append instead, which reads all data from the source but adds it to the destination rather than replacing it. This would let you compare the new data alongside your existing Incremental - Append records. [Sync Modes] However, the knowledge sources do not contain specific guidance on a testing/comparison workflow like the one you're describing, and they don't provide details specific to the Apple Search Ads connector's behavior in this scenario. I'd recommend being careful with Full Refresh - Overwrite in a production destination, as it will delete your existing data before writing new data. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai Where could I do test a specific period setting on Airbyte?

Based on the knowledge sources, you can configure and test a specific date period in the Connector Builder UI within Airbyte. Specifically, in the "Incremental sync" section of the Connector Builder, you can: 1. Set a "Start datetime" – e.g.,

2023-04-09T00:00:00Z

2. Set an "End datetime" – e.g., a specific end date or

now

Then, in the "Testing values" panel, you set the start date to the specific past date you want to test from. This will generate a request scoped to that time window, for example:

curl 'https://your-api.com/endpoint?from-date=2023-04-09T00:00:00Z&to-date=<now>'

[Incremental Sync Example] The knowledge sources do not provide details about testing specific periods outside of the Connector Builder UI (e.g., directly from the Connections UI). If you are not using a connector built with the Connector Builder, I cannot confirm from the available documentation where exactly you would configure this for the Apple Search Ads connector specifically. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai I didn't see Connector Builder UI on my Airbyte

There are a couple of reasons why you might not see the Connector Builder in your Airbyte UI: 1. Low-Resource Mode If you installed Airbyte using

abctl

with the

--low-resource-mode

flag, the Connector Builder is disabled. To access it, you need to: • Allocate Airbyte's suggested resources • Re-deploy Airbyte without the

--low-resource-mode

flag [Disabled in Low-Resource Mode] 2. Where to Find It If your Airbyte instance is properly resourced, the Connector Builder should be accessible by clicking "Builder" in the left-hand navigation bar of the Airbyte web UI. [Connector Builder Overview] If you don't see it there and you're not in low-resource mode, the knowledge sources don't provide further details on other reasons it might be missing. In that case, I'd recommend checking your Airbyte version or reaching out to Airbyte support. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai Do you mean to create a new connector builder?

No, I don't mean creating a new connector from scratch. The Connector Builder is simply a section/tool within the Airbyte UI that you access by clicking "Builder" in the left-hand navigation bar. [Connector Builder Overview] However, I should be transparent: the Connector Builder is primarily intended for building new source connectors, not for testing existing ones like Apple Search Ads. [Connector Builder Overview] So to clarify my earlier responses — if you're using an existing Apple Search Ads connector (not one you built yourself), the Connector Builder UI may not be the right place to test a specific data period. The knowledge sources do not provide specific guidance on where to configure a test date range for an existing pre-built connector outside of the Connector Builder. For your use case (testing a specific period with the Apple Search Ads connector), I'd recommend: • Checking the source configuration of your existing Apple Search Ads connection in Airbyte, where there may be a "Start Date" field you can adjust • Or reaching out to Airbyte support/community for guidance specific to that connector I'm sorry I cannot be more specific — the knowledge sources don't contain enough detail about the Apple Search Ads connector's configuration options. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.