Skip to main content
All CollectionsSales TrackingServer Postback Tracking
How to Implement Recurring Subscription Tracking
How to Implement Recurring Subscription Tracking

Detailed steps on how to process and return conversion data for recurring subscription tracking

Christine Santiago avatar
Written by Christine Santiago
Updated over a week ago

Using Server Postback with Partner ID within Aspire’s Sales Tracking will allow you to track recurring conversions. For example, you can pay out affiliates a commission for the life of the monthly subscription that an affiliate converts.

Step 1: Configure your Link Tracking Offer

You’ll first need to create a Link Tracking offer within your Sales Tracking dashboard in Aspire to obtain the postback URL snippet.

Directions:

  1. Go to Reporting > Sales Tracking.

  2. Click “Add Offer”, then select “Link Tracking Offer” from the drop-down menu.

  3. Enter an Offer Name, Offer Description, Conversion Type, and Payout Option.

  4. Set the Conversion Tracking protocol to Server Postback w/ Partner ID.

  5. In the Offer URL tracking, enter the landing page where you want to redirect traffic.

    The URL will need to include the variable {affiliate_id} and your store’s parameter for affiliate ID. The query parameter name is going to depend on your implementation. Please confirm what the query parameter will be with the engineer implementing this.

    Basically, we need a way to pass this variable to your store - usually, this is done as a URL query parameter. For example, your offer URL could look like this: https://yourstore.com?affiliate_id={affiliate_id}

    Affiliate links will resolve to the above URL, with the affiliate_id parameter having a value (e.g. https://examplebrand.com?affiliate_id=100). In this example, the affiliate_id is 100 and it is a unique ID for the affiliate (i.e. Aspire member) that drove this click.

Step 2: Store the Session Identifier

Your store will need to be able to accept the affiliate_id as a query parameter.

Whenever a customer clicks on an affiliate’s link, we will redirect to the Offer URL and replace {affiliate_id} with the member’s unique affiliate_id.

For the example above, it would look something like https://yourstore.com?affiliate_id=123456

Your store will then need to handle recording the affiliate_id and storing it for that potential customer. This can be done using first-party cookies or storing it on the server.

💡 Important: If you have multiple domains (i.e. store.us and store.ca), you need to ensure the affiliate ID persists across both stores if the user changes stores.

Step 3: Return ID upon Conversion

When a potential customer that visits your website from an affiliate link converts to a recurring conversion/subscription, your store will need to make a GET API call to the postback URL. Your website should also store the affiliate_id in their database for that customer/subscription.

The postback URL will look something like this:

https://aspireiq.go2cloud.org/aff_lsr?offer_id={offer_id}&aff_id={affiliate_id}&amount={amount}

  • offer_id: this will be shown in the offer Instructions in Aspire once it has been created

  • affiliate_id: this will be the affiliate_id that was stored as part of Step 3 (and now stored in your database as part of this step)

  • amount: this should be the value of the conversion (e.g. if we are tracking a monthly subscription, this should be the cost of one month’s subscription)

Whenever the subscription is converted again (e.g. for monthly subscriptions it will get converted again each month), you’ll need to make the same API call from

Step 4. You will use the affiliate_id that was stored in your database as part of Step 4.

You can see what the postback URL to call is by clicking on “Instructions” on your Offer page within Sales Tracking.

💡 Important: You will need to change what comes after &aff_id= to whatever variable you are using on your website to store the transaction ID.

Once implemented, we highly recommend placing a test order to confirm whether all the macros and parameters are placed successfully in the right position. See this article on how to test your postback.

Did this answer your question?