> For the complete documentation index, see [llms.txt](https://integrations.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.impact.com/integration-guides/for-brands/tracking-integrations/card-linked-offers-beta.md).

# Card-Linked Offers (Beta)

Card Linked Offers (CLO) reward shoppers who pay with a card they've linked to a partner's program, such as a cashback app. These purchases don't use a tracking link. Your partner sends the transactions to impact.com, and you set up an event type to receive them.

{% stepper %}
{% step %}

### Access event types

1. From the top navigation bar, select ![](https://3238951795-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiVbdCghMC6mw51rrphG6%2Fuploads%2FQ7Utk3BsV3EqnW4IQZBp%2Fuser-profile.svg?alt=media\&token=4b2302f5-3d55-4d54-8cfe-f6d7796191c0) **\[User profile]** → **Settings**.
2. On the right, under *Tracking*, select [**Event Types**](https://app.impact.com/secure/advertiser/tracking-settings/actiontracker/view-actiontracker-flow.ihtml).
3. In the upper-right corner, select **Create Event Type**.
   {% endstep %}

{% step %}

### Create the event type

<div data-with-frame="true"><figure><img src="https://3238951795-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiVbdCghMC6mw51rrphG6%2Fuploads%2FVJJNXQaQswOStmK7dN3D%2Fonline-event-type.png?alt=media&amp;token=9fca411f-69ae-4ae2-b85c-4fda6fb615c4" alt="" width="449"><figcaption></figcaption></figure></div>

Enter these settings for your CLO transactions:

* **Name**: `CardLinkedTransactions`
* **Type**: **Online Sale**. If you see the *Select A Conversion Type* screen first, select **Online Conversion**.
* **Tracking Method**: **Non-Pixel Tracking (Advanced)**
* Select **Email file to system SMTP server**.
  * An email address is generated. Save it for the validation test.
* Select **Save** to save the page.
  {% endstep %}

{% step %}

### Test and validate the event type

1. On the event type screen, find the **CardLinkedTransactions** tracker, then select **Start Test**. You go to the *Test Action* screen.
2. Create a CSV file with this header and one row:

```csv
CampaignId,ActionTrackerId,EventDate,OrderId,Amount,ClickId
{campaign ID},{event type ID},NOW,test123,0,{click ID}
```

* `CampaignId` is your Program ID.
* `ActionTrackerId` is the ID of your CardLinkedTransactions event type.
* `EventDate` is set to `NOW`, so the event date isn't earlier than your test click.
* `ClickId` is the click ID or `im_ref` value.

3. Email the CSV file to the address you saved in step 2.
   1. Attach the file only. You don't need a subject or message.
4. Wait 15 to 20 minutes, then select **Start Test** again on the event type screen.
5. On the *Test Action* screen, select **Approve** in the upper-right corner.
6. You return to the event type screen. The status of the event type changes to *Active*.

If the status stays *Pending Validation*, [contact impact.com support](https://app.impact.com/support/portal.ihtml).
{% endstep %}

{% step %}

### Share the Action Tracker ID with the partner

Share the `ActionTrackerId` with the partner. The partner needs to put the `ActionTrackerId` in the `event type ID` field in the file where they submit CLO conversions.

Read this guide to learn how to [send a message to a partner](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/messaging/send-a-message-to-a-partner).
{% endstep %}
{% endstepper %}


---

# 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://integrations.impact.com/integration-guides/for-brands/tracking-integrations/card-linked-offers-beta.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.
