Skip to main content

Installing SocialLadder tracking pixel for Code Based attribution

Bob avatar
Written by Bob
Updated over 4 years ago

This article describes the architecture and steps to install the SocialLadder attribution mechanism for code based selling on non-Shopify eCommerce systems. This article is technical in nature and you may want your IT team to handle the steps below.

The SocialLadder Tracking Pixel enables our platform to receive information necessary to provide credit to ambassadors for the sales they’ve driven.

When an ambassador give their friend their personalized code and their friend makes a purchase, the SocialLadder Tracking Pixel will fire on the sales confirmation page to give SocialLadder information required in order to attribute this sale. SocialLadder’s server identifies which ambassador should receive credit by looking up the personal code used at purchase, attributes the sale to the ambassador and immediately rewards / notifies them of the completion.

The following code needs to be deployed on the sales confirmation page that is displayed after the sale completes.

<!-- Start SocialLadder Tracking Pixel-->
<img src="//socialladder.rkiapps.com/socialladderapi/api/v1/campaign/track?Action=SALE&UDF1=[order_number]&udf2=[total_price]&udf3=[slshop_id]&udf4=[slquantity]&udf5=[slpromocode]&udf7=[slemail]">
<!-- End SocialLadder Tracking Pixel-->

IMPORTANT NOTE: The {[]} codes should be replaced programmatically with the actual data about this purchase as described below.

order_number: This is required and is any unique number for the order (used to prevent duplicate attribution).

total_price: This is required and represents the total value of the order.

slshop_id: this is a unique identifier provided from the SocialLadder team.

slquantity: this is required and is an integer value representing the number of units (if this information is not available please set it to 1).

slpromocode: This is optional - if discount codes or promo codes are used it can be set here.

slemail: This is optional and can be the email address of the purchaser for the most secure deployments this should be eliminated.

Did this answer your question?