> 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 debit or credit card they've linked to a partner's program, such as a cashback app or a bank rewards program. These purchases don't come through a tracking link, so your CLO partner sends the transactions to impact.com. Your part is to create an event type for these transactions, validate it with a test file, and share its details with your partner. {% stepper %} {% step %} ### Create the event type Create a new event type for your CLO transactions. Follow the steps in [Create an Event Type](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/event-types/create-an-event-type), using these settings: * **Name**: `CardLinkedTransactions` * **Type**: **Online Sale**. If you see the *Select A Conversion Type* screen first, select **Online Conversion**. * **Code**: Optional. Your partner can send this code instead of the Event Type ID to identify the event type. * **Tracking Method**: Leave the default for now. You set this in the next step. * **Returns Processing**: Keep the default, **Process returns using the Pending Payouts screen**. CLO doesn't support returns or negative transaction amounts. {% endstep %} {% step %} ### Set up an email address for your test file To validate the event type, you email it a test file. Set up the address you send it to: 1. On the [*Event Type Overview*](https://app.impact.com/secure/advertiser/tracking-settings/actiontracker/view-actiontracker-flow.ihtml) screen, hover over your event type and select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FaMIlbqH54V4Ow5JvT0I0%2F%5BMore%5D%20vNext%202.svg?alt=media\&token=6d5449e8-e413-48fa-b059-58ebb3e2c271) **\[More] → View/Edit**. 2. Under *Tracking Method*, select **Non-Pixel Tracking (advanced)**, then select **Batch upload**. 3. Select **Create new connection**, then complete the *Create Connection* screens: 1. On *Direction*, enter a **Connection Name**. Keep **Give data to impact.com**, then select **Next**. 2. On *Type*, keep **Conversions**, then select **Next**. 3. On *Method*, select **EMAIL** and keep **Push to impact.com**. Enter `*.csv` as the **File Pattern**, then select **Next**. 4. On *Credentials*, select **Create New Credentials** and enter a **Credential Name**. Optionally, add a **Return email address for receipt/result files** to get processing receipts by email. Select **Create**. 5. On the *Credentials Provisioned* screen, select **Copy** and save the email address somewhere safe. Then select **Next**. 6. On *Review*, check the details, then select **Create**. 4. Back on your event type, select your new connection from the **Connection** drop-down menu, then select **Save**. If your account shows **Email file to system SMTP server** under *Tracking Method* instead, select it, then select **Save** and copy the email address that appears. You only use this address for your test file. Your partner sends the real transactions through their own connection. {% endstep %} {% step %} ### Add the event type to your terms Add the CLO event type to the terms you use with your partner. Learn how to [add custom terms](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/contracts/add-custom-terms-to-your-contracts). The test in the next step needs the event type in your terms, and you can't send the terms to your partner until the event type is validated. {% endstep %} {% step %} ### Test and validate the event type 1. On the [*Event Type Overview*](https://app.impact.com/secure/advertiser/tracking-settings/actiontracker/view-actiontracker-flow.ihtml) screen, hover over your event type and select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FaMIlbqH54V4Ow5JvT0I0%2F%5BMore%5D%20vNext%202.svg?alt=media\&token=6d5449e8-e413-48fa-b059-58ebb3e2c271) **\[More] → Test**. You can also open the event type and select **Actions → Test**. 2. On the *Test Your Integration* screen, select a zero-payout testing **Template Term**, such as **Zero Payout (Testing Only)**, then select **Online Tracking Link** as the **Ad**. 3. Under *Run Test*, select **Start test in a new window**. You can also select **Copy** and paste the link into a new browser window. You don't need to complete a purchase on the page that opens: you only need its click ID. 4. Copy the click ID from the landing page URL. It's the value of the `irclickid` parameter. 5. Create a CSV file with the columns in the example below. `CampaignId` is your Program ID and `EventTypeId` is your Event Type ID. Set `EventDate` to `NOW`, `Amount` to `0.00`, and `ClickId` to the click ID you copied. Using `NOW` makes sure the event date isn't earlier than your test click. 6. Email the CSV file as an attachment to the email address you set up in step 2. Leave the subject and body empty. 7. From the left navigation bar, select ![](https://3238951795-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiVbdCghMC6mw51rrphG6%2Fuploads%2FYxS3uZ6Kt4mghl3lawOo%2Fengage.svg?alt=media\&token=0a54f160-9774-471b-a53f-515e9088fa2f) **\[Engage] → Transactions →** [**Test Actions**](https://app.impact.com/secure/advertiser/engage/actions/tests/test-actions-flow.ihtml). Your test action can take up to 30 minutes to appear. Your file might show a contract error on the *File Submissions* screen. That's expected, and the test action still appears here. 8. Hover over your test action and select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FaMIlbqH54V4Ow5JvT0I0%2F%5BMore%5D%20vNext%202.svg?alt=media\&token=6d5449e8-e413-48fa-b059-58ebb3e2c271) **\[More] → View Details**. 9. Review the details, then select **Approve** at the top right. The event type's status changes from *Pending Validation* to *Active*. Example test file: ```csv CampaignId,EventTypeId,Amount,EventDate,CurrencyCode,OrderId,ClickId 12345,78901,0.00,NOW,USD,test-clo-val-001, ``` For more about test actions, see [Create Test Actions](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/actions-and-payouts/actions/create-test-actions).
Troubleshoot your test | Issue | What to do | | ---------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Your test action doesn't appear after 30 minutes | On the *File Submissions* screen (**\[User profile] → Settings**, then **File Submissions** under *Technical*), check that impact.com received your file. Make sure your email has one CSV attachment and an empty subject and body. If you use a Batch upload connection, the file name must match your file pattern and can't start with `receipt_` or `result_`. | | The *File Submissions* screen shows a contract error | This is expected. Your test action still appears on the *Test Actions* screen. | | You set a specific `EventDate` and the test action doesn't appear | Set `EventDate` to `NOW` so the event date isn't earlier than your test click, then send the file again. | | You see "You cannot send these terms to a Partner until you have validated the selected Event Types for this Template Term!" | Validate the event type in this step first, then send the terms again. |
{% hint style="success" %} **Note:** If the event type status stays *Pending Validation* after you approve the test action, contact your CSM or impact.com support. {% endhint %} {% endstep %} {% step %} ### Share the details with your partner Once the event type is *Active*, send the terms to your partner, then share these details with them: * Event Type ID: shown in parentheses after the event type's name on the *Event Type Overview* screen * Program ID * Event Type Code, if you set one Optionally, also share your Merchant IDs (MIDs). They help your partner identify transactions from shoppers who have a relationship with the partner, for example through a loyalty account or a clipped offer. {% endstep %} {% step %} ### View and approve transactions Your partner sends eligible transactions to impact.com through their own connection. Learn how partners [submit card-linked transactions](/integration-guides/for-partners/card-linked-offers-beta/integration.md). Once they do, you can view the transactions: 1. From the left navigation bar, select ![](https://3238951795-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiVbdCghMC6mw51rrphG6%2Fuploads%2FYxS3uZ6Kt4mghl3lawOo%2Fengage.svg?alt=media\&token=0a54f160-9774-471b-a53f-515e9088fa2f) **\[Engage] → Transactions**. 2. Select **Pending Payouts** → [**Actions**](https://app.impact.com/secure/advertiser/engage/actions/open/pending-actions-flow.ihtml). 3. To see only card-linked transactions, filter by your CLO event type. Transactions are approved automatically based on your contract terms, or you can approve them manually. To approve a transaction manually, select ![](https://3238951795-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiVbdCghMC6mw51rrphG6%2Fuploads%2F2TKFDMY7RSc7BclbbJJV%2Fdropdown.svg?alt=media\&token=381aa52f-923f-4215-9d68-d3cc1432f682) **\[Drop-down menu] → Approve** in the *Actions* column. {% endstep %} {% endstepper %} {% hint style="info" %} **Tip:** To review and reconcile transactions manually, consider [open-ended locking](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/actions-and-payouts/open-ended-locking-explained), which lets you explicitly approve each action. {% 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://integrations.impact.com/integration-guides/for-brands/tracking-integrations/card-linked-offers-beta.md?ask=&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.