Responder/Bulk Conversion Tracking


We provide you with the ability to track conversions against your responders and bulk sends (both SMS and Email).  By doing so you can track the number of conversion and the value of those conversions to effectively output a P&L for your responders.

Setting The Scene
You operate a razor blade subscription business online.  Until now you have been generating sales organically and through social media but now you have a network of suppliers that provide you with leads (not sales).  Your suppliers submit leads to a LeadByte list in your account, which is connected to an auto responder. 

The objective?  Collect leads from multiple suppliers, trigger an SMS and/OR email to each lead driving clicks to your "Order Now" page to get a sale (conversion) and attribute that conversion back to a supplier to establish Return on Investment (ROI).  

Prerequisites (for this to work)
For this to work within LeadByte you need to ensure the following:

  • You are using Custom Domains for link tracking
  • You / the advertiser have the ability to capture a transactionID from the URL to the page
  • You / the advertiser have the ability fire a postbackURL with the transactionID

LeadByte Steps
The first thing you need to do is ensure that your responder pushes are set to RPA (Revenue Per Conversion).  The other options are Revenue Per Click (RPC), Revenue Per Thousand Impressions (RPM). 
Image 2023-08-09 at 1.19.11 PM

By selecting RPA, you have the option to select the revenue type (static or dynamic).  By selecting static you can enter in a set value for each conversion automatically (relevant If the value of a conversion is the same each time).  When you select dynamic, the advertiser is required to pass the value of the conversion into the postbackURL.

Static PostbackURL:{insert}

Dynamic PostbackURL:{insert}&revenue={insert}

The PostbackURL is loaded by the advertiser when a conversion happens.

your_account_name is replaced with your LeadByte account handle.
The advertiser is required to replace the transid value and revenue value (for dynamic)

TransID (important)
The next thing you need to ensure is to include the [transid] tag in your redirect URL.  When RPA is selected as the Push Type, LeadByte automatically appends a transaction ID (transid) to each click.  This value must be captured by the advertiser so it can be loaded in the PostbackURL.  Be sure to use the tag ( [transid] ) to send the unique transaction ID to the destination page.

Example redirect URLs[transid]

LeadByte will automatically replace [transid] with a unique value

The Flow 
> Supplier ABC Ltd sends you a lead (customer)
> Customer is sent an SMS (system redirect URL is[transid])
> Customer clicks on link and is redirected to
> Customer signs up for a Razor Blade monthly subscription
> PostbackURL:
> Conversion is tracked in LeadByte

Sample Report


As always, if you have any questions or concerns please don't hesitate to raise a support ticket.

Was this article helpful?
1 out of 1 found this helpful