Skip to main content

​
Overview

Destination Type:

​
How it works

  1. A visitor clicks a partner’s impact.com tracking link and lands on your site with a click ID in the URL.
  2. The Converge Pixel saves the click ID on the visitor’s profile.
  3. When the visitor converts, Converge sends the conversion with the click ID to impact.com’s , and impact.com credits the partner.
Converge keeps the click ID on the profile, so conversions you track on your server, like orders from your store backend, include it too.
The Converge Pixel must run on the pages your impact.com tracking links land on. Otherwise, Converge can’t capture the click ID.

​
Installation instructions

Create an impact.com API token

Converge authenticates with an impact.com API access token, which consists of an Account SID and an Auth Token.
  1. In impact.com, select your user profile in the top navigation bar, then Settings.
  2. In the left column, scroll to Technical and select API.
  3. Select Create Access Token. Enter a Token Name, for example Converge Destination, and a short Description. Select Next.
  4. Toggle on the Conversions category and check the Create conversion scope. Converge doesn’t need any other scope.
  5. Select Create, then open the token to copy its Account SID and Auth Token.
For more detail, see impact.com’s guide.

Find your program ID and event type IDs

  1. In impact.com, select your brand name in the upper-left corner. Copy the program ID shown under your program’s name.
  2. Select your user profile, then Settings. Under Tracking, select Event Types.
  3. Copy the ID of each event type you want to track, for example your sale and lead event types. The ID is in parentheses next to the event type’s name.

Set up the destination in Converge

  1. In the Converge sidebar, click on and then click Create new Destination.
  2. Select the impact.com destination and click Next.
  3. Give your destination a name (e.g. impact.com Destination) and click Next.
  4. Fill in the Account SID, Auth Token, and Program ID, then click Next. Converge checks that the token is valid and that the program belongs to the account.
  5. Click Add new mapping and map each Converge event to the Event type ID it should be tracked as. For example, map Placed Order to your sale event type. Click Next.
    impact.com has no default mapping, because event type IDs are unique to your account. For more on mappings, see Event mapping.
  6. Select the sources you want to forward events from, then click Next.
  7. Review any issues and click Create destination.
Set this destination to Deactivated while you remove your existing impact.com conversion tracking. Running both in parallel leads to duplicate conversions. Follow the Turn off your old impact.com tracking instructions below, then set the destination to Active when you’re ready.

​
Turn off your old impact.com tracking

Turn off every other integration that sends conversions to impact.com for the same program, such as:
  • The impact.com Shopify app
  • Conversion tracking with the impact.com Universal Tracking Tag
  • Another server-side integration, like Segment’s impact.com destination
  • Scheduled file uploads of your orders

​
Send custom parameters

Custom parameters send an event or profile property as an extra impact.com parameter. Use them for any parameter of the that Converge doesn’t send by default.
  1. Navigate to your impact.com destination and click on Configuration.
  2. Open the Advanced configuration (optional) section.
  3. Under Custom parameters, click Add. Fill in the Converge property as Property name and the impact.com parameter as Destination property name, for example customer_id and CustomerId.
  4. Click Save.
Converge reads the property from the event first, then from the profile, and sends its value as text. Events without the property are sent without the parameter.

​
Send a customer ID

Map a property that holds your customer’s ID to CustomerId. impact.com then credits later events, like subscription renewals, to the partner who drove the customer’s first conversion. This uses impact.com’s , which you set up on your event types in impact.com. The first conversion and the later events must carry the same CustomerId. Converge sends events with a CustomerId even when they don’t have a click ID.

​
Conversion amount

Converge sends the conversion amount you pick in the destination configuration, together with the order currency. impact.com converts it to your account currency. Events without a total_price, such as Signed Up, are sent without an amount. Use them for impact.com event types that pay partners a fixed amount per action, like leads.

​
Sent parameters

Converge sends the amount as both the order subtotal and a single item subtotal. impact.com uses one or the other depending on your program’s item tracking, so it’s never counted twice.

​
Converge functionality

This integration supports the following Converge destination functionality.

​
FAQ

impact.com queues conversions and processes them in the background, which usually takes up to 30 minutes. Processed conversions show up as pending actions under Engage > Transactions > Pending Payouts > Actions.A Success status in the destination logs means impact.com accepted the conversion for processing. impact.com can still decide not to create an action, for example when the conversion happened before the click.
Converge skips a conversion that has neither an impact.com click ID nor another identifier impact.com can attribute it with, like CustomerId. This happens for visitors who didn’t come through an impact.com tracking link. To credit these conversions through chained actions, send a customer ID.
impact.com adds the click ID to your landing page URL as im_ref by default, or as irclickid when your program’s tracking template sets it. Converge reads only these two. If your tracking template uses a different parameter, change it to irclickid. Otherwise, Converge can’t capture the click ID.

​
Event mapping

impact.com has no default mapping. Map each Converge event to the ID of the impact.com event type it should be tracked as, for example: