WeCanTrack WordPress Plugin

When you are connecting a WordPress website you should make use of our WordPress plugin. Our WordPress plugin will automatically place our JS tag on your website, on top of that it will be able to work with cloaking plugins such as Pretty Links, Thirsty Affiliates, Affiliate Link Lite and more.

If you are not cloaking your affiliate URLs our WordPress plugin will place redirect URLs containing your website’s domain, which make the URLs seem trustworthy and also won’t cause any issue with ad networks.

Nevertheless, if you don’t want our system to place redirect URLs you can turn on our client-side Auto-Tagging functionality within the advanced website settings. Then our system will place the click IDs directly into the affiliate URLs.

Requirements for Click Tracking & Attribution

We can only work with your affiliate URLs if you follow some basic rules:

Requirements to use the WordPress plugin

Install the Wecantrack WordPress plugin

  • Install the Wecantrack WordPress plugin (search for “wecantrack” or follow this link)
  • Click on ‘Install Now’
  • Click on ‘Activate Plugin’
  • Search for Wecantrack in the navigation bar and click on it
  • Go here to get your API key: https://app.wecantrack.com/user/integrations/wecantrack/api
  • Fill in your API key and verify it
  • Set the Plugin status to ‘Enable’
  • Click on ‘Update & Save’
  • If you have cache on your website please make sure to clear it after activating our plugin
  • If you’re making use of Thirsty Affiliates, please make sure to deactivate “Enable Enhanced Javascript Redirect on Frontend” within settings under Link Appearance.

Plugin Settings

Within our WordPress plugin settings you are able to disable the wecantrack JS tag placements. This means our plugin will no longer place the JS tags automatically. You can then instead place it manually to gain more control where or when our JS tag is placed. This is especially useful when you want to have full control to manage the loading of our JS tag (and thus session cookie) for consent reasons. In case you are having difficulties reaching the wanted results in regards to our JS tag or cookie placements, please do not hesitate to reach out to our support.

In case our plugin is showing ‘Invalid Request’ it is likely that there is an SSL problem. Your host might not have updated a relevant certificate. You can then disable the SSL verification for wecantrack’s API calls within the settings.

Moreover, if you are facing issues with click page attribution our referrer cookies might be of help. Please consider data processing regulations though before activating that funcitonality.
In case you are facing some inaccuracies within the click page report with that setting turned on, we advise to turn it off, since tracking of click pages is affected differently for different websites.

Testing the Wecantrack WordPress plugin without fully enabling it (optional)

If you want to test the plugin before fully using it, you can either test it by shortly activating it and checking the redirect path when clicking on your outgoing links, or you can leave our plugin’s status disabled and follow the next instructions.

  • Add an expression that the URL has to contain in order for the plugin to work
    If you’d for example place “?wct=on” in the “Enable plugin when URL contains” field (as in the screenshot on the right), your landing page needs to contain the expression in order for our plugin to be active (please use a new session, e.g. within an incognito browser window).
    https://wecantrack.com/?wct=on – on this URL our plugin would be activated
    https://wecantrack.com/ – on this URL our plugin would still be disabled
  • You can also place a slug or whole landing page URL if you want to test it on an entire page
  • The test is active as long as your session lasts
  • We suggest you test your outgoing links with this functionality and check whether the redirection path looks fine (you can for example use a Chrome plugin like “Redirect Path” to check that).
  • Check the following:
  • whether you land on the advertiser’s landing page
  • whether you are being directed through the affiliate URL
  • whether a SubID parameter is being placed containing the WCT ID (as in the screenshot “wct200325152941hmbtv”)