Skip to main content

Inflektion Integration

The following document covers the specific integration points for Inflektion’s Partnership Automation Platform into the rest of the IT and marketing stack.  One of our design principles is to create a completely modular system that can seamlessly integrate with your existing workflows and technologies.

Affiliate Signup Form

To integrate the signup form, the following endpoints are needed:

  • (Required) SEO/Podcast/Social-friendly Pretty Links: This will be used to automatically allow new affiliates to check the availability of their pretty link, and then create it once they sign up.  An API endpoint is needed that can do check/create requests to create HTTP 301 redirects for the desired domain.  Ideally, there is also capability to do rename/delete requests via the API.  This capability already exists by default in Shopify and BigCommerce APIs, and can be easily added to WordPress using the Redirection plugin.  If you want to use a separate dedicated domain besides your main domain, then this capability can be added easily via the TinyURL.com service.

  • (Ecommerce Only) Coupon Codes: Similar to above, affiliates can check/create their desired coupon code on signup.  The ability to check/create/delete ecommerce discount codes via API is needed.  This already exists via the standard Shopify, WooCommerce and BigCommerce APIs.

Tracking and Conversions

Affiliate tracking analytics will be integrated via the following integration points:

  • (Required) Click Tracking: This is done via adding a JavaScript library to the bottom of the <body> section of all pages.  This will allow for click tracking using both link decoration methods and links that already have gone through a redirection tracker.  Furthermore, this will also allow support for publishers that want to deep link, such as press affiliates.

  • (Required) Conversion Tracking: This is done either via inserting a JavaScript library on any purchase confirmation page, or using server-to-server postbacks containing the unique click ID.  For those using Segment, we have a standard integration webhook that can be used for any track() event.

  • (Highly Suggested) ITP-Compatible Tracking: This is important for making sure click ID tracking is persistent across Safari browsers due to Apple’s Intelligent Tracking Prevention technology.  While we have some other tracking technologies in place to address this already, developing an ITP-resistant storage for the click ID is also highly suggested.  This is already standard for our Shopify (native functionality) and WordPress (we have a simple plugin to install) integrations.  For other implementations, it’s recommended to develop a postback from the click tracking script above that then fires an XHR to set a first-party cookie using HTTP headers (instead of JavaScript).

  • (Highly Suggested) Email Attribution: This is done via a JavaScript listener that is added on your ESP’s email collection forms.  On email address submission, the listener will fire a callback associating that email address to the affiliate.  Often, this code is integrated via Google Tag Manager.

  • (Optional) Other Key Funnel Events: Similar to the above email attribution callback, any other key events can also be posted back to Inflektion in order to view these metrics by affiliate, sub ID, etc.

Landing Page Personalization

This is accomplished via adding an async JavaScript library in the <head> section for all pages.

Custom Integration Points

Inflektion also has the modular ability to execute custom code at each of the following points:

  • On affiliate signup
  • On affiliate approval
  • On affiliate removal
  • After each successful affiliate-generated sale

Common integrations that partners have done in the past have been to integrate Inflektion with custom workflows such as adding new affiliates to your company CRM (e.g. Hubspot, Klaviyo) or adding tags and other metadata to affiliate-generated orders.

Furthermore, Inflektion has the ability to integrate into various multi-touch attribution platforms (e.g. Rockerbox) through various ingestion methods such as API, daily email CSV attachments, and Google Sheets exports.

Recurring Orders

If the program is designed in a way that includes recurring orders done offline (i.e. not done by the customer/web browser), then integrating these offline orders can be done via:

  • Webhook - by pushing all or only offline orders to an endpoint hosted on Inflektion.
  • API - Inflektion will retrieve orders periodically.

New orders would then be matched for attribution purposes, and any matching records would have affiliate conversions created for them.  If offline orders are not discernable from other orders, existing online affiliate orders will not be double-counted due to multiple deduplication methods that exist.

Was this article helpful?