Our integration with Impact.com allows for tracking and attributing influencer sales associated with Impact.com tagged event links. Within Impact.com, you can register individuals and organizations for affiliate marketing, and those registered will receive a commission based on the volume of sales they generate.
ℹ️ Supported for Event Listings only. It is not possible to utilize Impact.com tracking on Classic Checkout or Embedded Listings.
This is handled by tagged event links per influencer/affiliate. Within Impact.com, each Influencer is assigned an "irclickid" which is tagged in the Event URL, for example:
https://tickets.showclix.com/tickets/?im_ref=14zqjADgl7uNcN9V8uPPgD3Cj:oube4Osd-nEHg-PBf
When sales are converted on Leap, Event Ticketing will fire a message to Impact that includes the Sale Info as well as the irclickid to attribute for the sale.
Setup
You can enable the Impact.com integration via the Marketing Accounts page. From the admin:
- Navigate to the Marketing tab
- Select Marketing Accounts
- Navigate to Impact.com and select Connect
- Enter your Impact.com UUID and Event ID
- Click Save

Impact may first request you to answer some questions about Event Ticketing and then provide a formal 'Technical Implementation Plan' that will include both the Event ID and UUID to input.
In the Technical Implementation Plan, the Event ID will be clearly shown in the top of the document in the Overview area. The UUID can be found in the Universal Tracking Tag highlighted in blue below:

Technical Details
Leap's Integration with Impact.com is facilitated via Impact's JavaScript UTT. This is comprised of three components:
-
Impact's
Universal Tracking Tag (UTT)is installed on the global tag of all checkout pages. -
Impact's
identifyfunction is installed on all checkout pages.- Note: Due to guest checkout, customer identification may not be possible until the sale complete page
-
Impact's
trackConversionfunction installed and fired on the confirmation screen (see appendix for field mappings)
The UTT is required for the other two functions to work. The UTT loads first on each page, and then the different functions follow.
Identify Function Format and Field Mapping
This function is installed on all checkout pages and is used to identify users as accurately across your site, and across devices.
Here's the format of the identify function:
<script type="text/javascript">
ire('identify', {customerId: 'Customer Id', customProfileId: 'UUID'});
</script>
And the field mapping used for each parameter:
| Parameter | Impact Description | Leap Field |
| customProfileId | Unique identifier used to identify a visitor on your website. | Customer ID |
| customerId | Unique customer identifier your platform assigns to customer accounts. Do not use personally identifiable data for this field. Pass an empty string if unavailable. | Customer ID |
TrackConversion Function Format And Field Mapping
This function is fired on the confirmation screen after Customer completes a Sale.
Here's the format of the trackConversion function:
<script type="text/javascript">
ire('trackConversion', EventID, {
orderId: "Order Id here",
customProfileId: "UUID here",
customerId: "Customer Id here",
customerEmail: "SHA1 Hash of Customer's Email",
customerStatus: "Customer Status here",
currencyCode: "USD",
orderPromoCode: "Promo Code here",
orderDiscount: 15.00,
items: [
{
subTotal: 28.00,
category: "Product Category 1",
sku: "sku-11111",
quantity: 2,
name: "Product Name 1"
},
{
subTotal: 99.00,
category: "Product Category 2",
sku: "sku-22222",
quantity: 3,
name: "Product Name 2"
}
]
},
{
verifySiteDefinitionMatch:true
}
);
</script>And the field mapping used for each parameter:
Parameter |
Impact Description |
Leap Field |
orderId |
Unique order identifier your platform assigns to orders. |
Order ID |
customProfileId |
Unique identifier used to identify a visitor on your website. |
Customer ID |
customerId |
Unique customer identifier your platform assigns to customer accounts. Do not use personally identifiable data for this field. Pass an empty string if unavailable. |
Customer ID |
customerEmail |
SHA-1 hash of the customer's email address. Pass an empty string if unavailable. |
Always empty |
customerStatus |
Submit values of either New or Existing. Can be configured to alter payouts. |
“New” if never before seen customer“Existing” if previous records exist |
currencyCode |
Three-letter ISO 4217 code for the currency of your platform. |
Determined by the Seller’s currency. |
orderPromoCode |
Promotional (or coupon) code applied to the order. Pass an empty string if unavailable. |
Coupon code |
orderDiscount |
Total discount amount on the order. This will be subtracted proportionally from the item-level subtotals when revenue values are calculated by impact.com. |
Sum of discounts applied to the Order |
subTotal |
SKU set subtotal of the line item (pre-tax, pre-shipping, pre-discount). |
Face Value of the Ticket or Product sold |
category |
Item category identifier. Can be configured to alter payouts. |
Event Name |
sku |
Item stock-keeping unit (SKU) identifier. |
Price Level ID for TicketsProduct Configuration ID for Products |
quantity |
Item quantity. |
Number of items |
name |
Item name. |
Price Level Name for TicketsProduct Name for Products |