> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/submit-and-modify-conversion-data/submit-conversion-data/submit-new-skus-after-conversion.md).

# コンバージョン後に新しいSKUを送信

場合によっては、トラッキング後にユーザーが注文に戻って商品を追加できることがあります。そのような場合は、新しい商品を FTP 経由で impact.com に送信すると、こちらで UPSERT できます。詳しくは [FTP 経由でコンバージョンデータを送信する](/brand/ja/what-would-you-like-to-learn-about/platform-features/submit-and-modify-conversion-data/submit-conversion-data/submit-conversion-data-via-ftp-or-email.md)をご覧ください。さらにこの手順についてサポートが必要な場合は、CSM（または [サポートに連絡してください](https://app.impact.com/support/portal.ihtml?createTicket=true)).

#### 要件

注文のオープン済み・請求済みレコードが、すでに impact.com に存在している必要があります。ロックされた注文にアイテムを upsert しようとしても失敗します。

{% stepper %}
{% step %}

#### データを準備する

以下の .csv テンプレートを使って、データの構成に役立てることができます。2 行目と 3 行目のサンプル値は、あなた自身のデータに置き換えてください。

```programlisting
ActionTrackerId,OrderId,CurrencyCode,Amount,Category,Sku,Quantity,Reason,Method
12345,1076543345142,USD,123.50,Added_Item_category,Added_Item,Added_Item_Sku,12,Order_Update,UPSERT
12346,1076543345143,USD,98.50,Added_Item_category,Added_Item,Added_Item_Sku,11,Order_Update,UPSERT
 
```

{% endstep %}

{% step %}

#### データファイルを送信する

参照してください [FTP 経由でコンバージョンデータを送信する](/brand/ja/what-would-you-like-to-learn-about/platform-features/submit-and-modify-conversion-data/submit-conversion-data/submit-conversion-data-via-ftp-or-email.md) impact.com に FTP データを送信する際のサポートについては、
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**注：** 最初の注文に適用された割引は、再処理されません。
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/submit-and-modify-conversion-data/submit-conversion-data/submit-new-skus-after-conversion.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.