What Is Impact Radius?

impact.com (formerly Impact Radius) is a partnership automation platform used for affiliate marketing, influencer marketing, and partnership tracking. It provides technology to measure, optimize, and attribute traffic and conversion activity generated from partner-driven campaigns. Advertisers can send server-side page load and conversion events directly to impact.com to connect on-site and in-app activity with partner attribution and payout calculation. The platform supports both web and mobile app tracking across the full partnership lifecycle.

Product Type: Advertising
Integration Type: Starter Kit
Event Source Type: Web and Mobile App
Event Scope: Conversion Events Only

Capabilities

Supports conversion event tracking (purchases) and multi-channel page load tracking for attribution.
Accepts attribution identifiers (CustomerId, CustomProfileId) to link sessions to conversions.
Captures transaction and item-level details for reporting and payout calculation.
Uses authenticated requests to ensure secure integration.

Considerations

In this kit, the USERNAME connection parameter is used for the impact.com AccountSID and the PASSWORD connection parameter is used for the AuthToken.
Conversions older than 88 days are not recommended; conversions up to 398 days old can only be processed if attributed using MediaId.
When item-level details are provided, ItemSku, ItemCategory, ItemPrice, and ItemQuantity are required.

Limitations

OrderSubTotalPostDiscount should not be submitted when item-level data is provided.
OrderPromoCode only works for attribution if the code is pre-assigned to a partner in impact.com.
API submission records are retained for no more than 90 days.

Starter Kit Setup Guide

1. Gather Credentials

CampaignId: In the platform, click your account name in the top left corner. Your campaign ID is the gray integer listed under the Programs section.
ActionTrackerId: Ask your impact.com representative for the Action Tracker ID that identifies which conversion type to track.
PropertyId (for mobile apps): Found in Settings → Mobile Apps.
Ask your impact.com representative for the following credentials:
- USERNAME (AccountSID)
- PASSWORD (AuthToken)

2. Add an Impact Radius Integration

From the integration library, add an Impact Radius integration. Then, fill out the Connection Parameters:

Connection Parameter	Description
`USERNAME`	Username used for HTTP Basic Authentication. Used as the impact.com AccountSID.
`PASSWORD`	Password used for HTTP Basic Authentication. Used as the impact.com AuthToken.

3. Configure Event Mapping

MetaRouter provides all of the event mappings that Impact Radius integrations typically require. You may add custom events, parameters, or mappings in accordance with impact.com's API documentation.

4. Deploy to Pipeline

In the Pipelines tab, add your Impact Radius integration.
Select the correct integration revision.
Click Add Integration to finalize deployment.

Event Mappings

Global

Global mappings will be applied to all events. If your parameter names do not match the Expected Inputs provided, you will need to overwrite the Inputs provided with your own.

Output Key	Description	Expected Input
`CampaignId` Required	String: Program or campaign identifier on impact.com. Set as the `CAMPAIGN_ID` playbook parameter.	$$CAMPAIGN_ID$$
`CustomProfileId`	String: Anonymous ID used for cookieless attribution.	`anonymousId`
`UserAgent`	String: Browser or device user agent.	`context.userAgent`
`IpAddress`	String: IP address of the user.	`context.ip`
`CustomerId`	String: Authenticated customer ID.	`userId`
`EventDate` Required	String: Event timestamp reformatted to impact.com's required format.	Expression – converts `timestamp` from RFC3339 to impact.com format

Event Specific

Page

Output Key	Description	Expected Input
`PageUrl` Required	String: URL of the page being tracked.	`context.page.url`
`ReferringUrl`	String: Referring page URL.	`properties.referrer`

Screen

Output Key	Description	Expected Input
`Appleifv`	String: Apple Identifier for Vendors (device advertising ID).	`context.device.advertisingId`
`DeviceMfr`	String: Device manufacturer.	`context.device.manufacturer`
`DeviceModel`	String: Device model.	`context.device.model`
`PageUrl` Required	String: Screen or property URL for the app event.	`properties.url`
`PropertyId` Required	String: Mobile app property identifier.	`appId`
`ReferringUrl`	String: Referring URL.	`properties.referrer`
`TrackingConsent`	String: Ad tracking consent status for the device.	`context.device.adTrackingEnabled`

Order Completed

Output Key	Description	Expected Input
`ActionTrackerId` Required	Identifies which conversion type to track. Set as the `ACTION_TRACKER_ID` playbook parameter.	$$ACTION_TRACKER_ID$$
`OrderId` Required	String: Unique order identifier.	`properties.order_id`
`OrderPromoCode`	String: Promo or coupon code used on the order.	`properties.coupon`
`OrderDiscount`	Number: Discount amount applied to the order.	`properties.discount`
`OrderTax`	Number: Tax amount on the order.	`properties.tax`
`OrderShipping`	Number: Shipping charge amount.	`properties.shipping`
`OrderSubTotalPostDiscount`	Number: Order subtotal after discount.	`properties.revenue`
`OrderSubTotalPreDiscount`	Number: Order subtotal before discount.	`properties.total`
`CurrencyCode`	String: ISO 4217 currency code, normalized to uppercase.	`properties.currency`
`ItemCategory`, `ItemSku`, `ItemPrice`, `ItemQuantity`, `ItemName`	Array: Product-level details flattened into indexed fields (e.g., `ItemSku1`, `ItemPrice1`).	Expression – maps each item in `properties.products` to indexed product fields

Required & Recommended Identifiers

These identifiers must be mapped to Impact Radius in order for successful user matching to occur. Without these IDs, any events sent to Impact Radius may not be accurately reflected in reporting.

Attribute	Example	Sync Injector Required?
`CustomerId` Required	`111222`	No
`CustomProfileId` Required	`b171a9b06ce011ecafcd1b209be8601b`	No
`OrderPromoCode` Required	`SAVE20`	No
`Appleifv` Required	`AEBE52E7-03EE-455A-B3C4-E57283966239`	No

At least one attribution key is required per conversion.

Integration Validation

Coordinate with your impact.com representative to confirm that events are being received and processed correctly on their backend. Request verification that page load and conversion events appear as expected and that conversions are being attributed and reflected in reporting before launching to production.

Additional Impact Radius Documentation

impact.com - Conversions API Reference