> ## Documentation Index
> Fetch the complete documentation index at: https://docs.invoca.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Impact: Setup & Overview

> Commission your partners, influencers, and affiliates for calls and call conversions by connecting Invoca to Impact Partnership Cloud.

Impact is a partnership management platform used to recruit, track, and pay affiliates, influencers, and other partners. Connecting Invoca to Impact lets you send call and Signal conversions to Impact so partners can be credited and paid.

## Step 1: Gather your IDs and credentials from Impact

You'll need your **Impact Campaign ID** (called a Program in the Impact UI) — the cornerstone of your tracking, where partners sign up, ads are hosted, and traffic tracking and payouts are associated. Contact your Impact technical representative if you have trouble finding it.

You'll also need an **Impact Action Tracker ID** for each action you're tracking. If you're only using the Log Calls action, you can skip the next part — but if you plan to have Impact award partner payouts, you'll also need your **Impact Account SID** and **Auth Token**, found in your Impact Account Settings.

## Step 2: Configure the integration in Invoca

1. In the sidebar, click **Integrations**, then **Manage Integrations**.
2. Click the **Impact.com** tile. If it doesn't say "Ready to Integrate," contact your CSM or submit a support case.
3. Enter a friendly name for your Impact account.

### Create an Action

Two Action types are available:

* **Send Conversions** — the most common choice, used if you want to award and pay commissions to partners in Impact.
* **Log Calls** — sends calls as events with call information (number dialed, destination, duration, Caller ID, recording link), without managing payouts.

For each Action:

1. Enter a friendly name (include "Call" or the Signal name to distinguish Actions).
2. Optionally filter by Profile or Campaign.
3. Under **Triggered By**, choose **All Calls**, **Paid Calls**, or **Signal** (with the specific Signal). Since Impact requires either an `irclickid` or `mpid` value to process a conversion, consider creating a rule-based Signal that checks for one of those values being present, and trigger on that Signal to avoid sending calls Impact can't attribute.
4. If using **Send Conversions**: enter the Account SID, the Impact Campaign/Program ID from Step 1, and the Action Tracker ID matching your Triggered By selection.
5. For **Send Conversions**, encode your Account SID and Auth Token locally rather than through a third-party website — don't paste live credentials into an external encoder. On macOS or Linux, run `echo -n 'ACCOUNT_SID:AUTH_TOKEN' | base64` in a terminal (replacing `ACCOUNT_SID` and `AUTH_TOKEN` with your actual values); on Windows, run `[Convert]::ToBase64String([Text.Encoding]::UTF8.GetBytes('ACCOUNT_SID:AUTH_TOKEN'))` in PowerShell. Enter the resulting value as the "Impact Auth Token (base64 encoded)."
6. Optionally enter a 3-letter currency code — Invoca defaults to USD.
7. Click **Save**. Repeat for each transaction type you want to report.

If you plan to use this integration with static promo numbers (for offline marketing or Google Call Extensions), assign a value for the Impact Media Partner ID (`mpid`) Marketing Data field to each of those promo numbers, corresponding to the Impact Partner ID that should get credit.

## Validate the integration

1. In Invoca, click **Integrations**, then **Manage Integrations**.
2. Click the **Impact** tile, then the name of the Action you created.
3. Review the Delivery Details chart, showing successes (green) and errors (red) by day for the last 30 days. Click into Delivery History to see individual requests and responses.

Invoca will send call or Signal transactions to Impact even without an Impact Partner ID or Click ID captured — Impact can't attribute these and will return an expected error. To reduce this noise, consider a rule-based Signal that checks for one of those identifiers before triggering the Action.

To ensure Log Calls Actions are sent before Send Conversions Actions, Send Conversions webhooks have a 5-minute delay — keep this in mind during testing. For event time, Invoca first tries the Signal "Occurred At" time, falling back to the transaction Start Time if blank.

## FAQ

**How is the partner link updated with URL parameters like `irclickid` or `mpid`?**
In Impact, the Impact Brand determines parameters for the partner link. Under Gateway, generate click tracking requirements — these can update dynamically based on the partner or use static values.

## Where to go next

* [Connect Apps & No-Code Integrations](/s/article/connect-apps-and-no-code-integrations)