Our Affiliate campaign lets you choose a link for your advocates to share like the Share campaign, but as an extra, it also enables you to track conversions for those shares.
For example, let's say you want to get more signups for your newsletter and ask your advocates to share the link to the signup page with their friends. You can see how many times they shared it and in the reporting section you can even see the amount of traffic that was generated, but you can't see how many people actually signed up because of your advocates. By adding Ambassify's conversion pixel to your site, you can start keeping track of this and rewarding your advocates for the conversions.
Setting up the conversion pixel
First things first, you need to create an affiliate campaign. To do so, you will have to create a Share campaign, and enable conversion tracking by ticking the box at the end of the page.
Once enabled, the Ambassify pixel script will show together with a brief description of the steps that you need to take.
You'll see your conversion pixel (it's the same for every campaign) at the top of the page. What you need to do now is copy it and paste it on a page of your website inside of the page head tag. Once someone visits this page, a conversion will be tracked in Ambassify and the advocate whose share link was last used will be awarded the points. We recommend placing this pixel on a confirmation page or similar to prevent getting too many conversions. (For example on the thank you page of your newsletter signup.)
Once your affiliate campaign is ready, you can also find the pixel when you open your campaign overview, and in the menu on the left navigate to conversions.
On this conversions page, you will - after your campaign has been launched - also find the conversions that the campaign has generated.
Adding custom behavior
The conversion pixel as it is available from the Conversions tab of a campaign will track a conversion when it is loaded. This is useful when you have a thank you page on which you can place the pixel and it makes it very low effort to install the pixel.
However if you would like to track conversions when something dynamic happens on your page, such as when a button is clicked, you will need to modify the script slightly.
In most cases this will involve some co-operation of your web developer.
The pixel will generate a conversion within Ambassify every time the ambt('conversion') line of the script is called. If you would not want to generate a conversion every time the script is loaded, but rather based on some event you can move that line into the event handler for your specific use-case.
An example:
function trackConversion() {ambt('conversion');}document.querySelector('input[type=submit]').addEventListener('click', trackConversion);Enriching the conversion data
By default, the conversion tracking is able to track when something happened and where it happened and we will show this data in the administration panel. Depending on your website's capabilities, it's also possible to tell the conversion tracking script who visited a specific page. This is a bit more technical so you might need some help from a web developer.
Going back to the newsletter example, you could read the data someone filled in in the subscription form and pass it to our script. This way, the Ambassify backend could also show you who signed up.
To make this possible, you will need to make some changes to your conversion script.
Replace the call to ambt("conversion") (inside the req square in the image above) with the code outlined below. Replace the givenName and familyName with code that fills in the right name and you are ready. If you do not have the first and last name separately, it's also possible to use name instead.
ambt('conversion', 'ViewAction', { agent: { givenName: 'John', familyName: 'Doe' }});
How conversion tracking works behind the scenes
Understanding how Ambassify tracks conversions can help you interpret your campaign data more effectively.
Whenever someone (let’s call them Visitor X) clicks on a link shared by one of your Ambassify users (User Y), Ambassify stores referral information in Visitor X’s browser. Specifically, we save:
The Ambassify User ID of the person who shared the link (User Y)
The Campaign ID the link was shared through
This information is stored in cookies for up to 2 years. However, keep in mind:
Due to evolving privacy features in modern browsers, cookie reliability can vary.
If Visitor X later clicks on a different Ambassify campaign link, the saved referral data will be overwritten with the latest campaign and user info.
When a conversion is logged using our tracking script, Ambassify checks for this stored referral data. If it's available, it attributes the conversion to the appropriate user and campaign.
Example Workflow
You create a campaign (Campaign Z) for a job opening like “Senior Frontend Engineer.”
User Y shares the campaign link on LinkedIn.
Visitor X clicks the link.
Ambassify stores the referral data (User Y, Campaign Z) in Visitor X’s browser.
X is redirected to the vacancy page.
X fills in the application form.
A conversion is logged and attributed to User Y and Campaign Z.
Important Notes and Edge Cases
Scenario 1: If Visitor X browses your site and applies for a different position (e.g., “Senior Backend Engineer”), the conversion will still be logged under Campaign Z because that was the initial referral link. To help with this, Ambassify also records the exact webpage where the conversion occurred and provides a consolidated view of all conversions regardless of campaign attribution.
Scenario 2: If Visitor X doesn't convert immediately but later returns and applies (even via another channel), the stored Ambassify data can still attribute the conversion to the original campaign and user—if the cookie is still present.