Page tree
Skip to end of metadata
Go to start of metadata

WWWPromoter has an advanced platform for tracking conversions which allows for detailed campaign optimization.  We offer both a tracking pixel and a server-to-server tracking API.  While a basic integration is available, more advanced integration (including attribution of sources via SubIDs) is available with some coding.

Important Things To Know

There are some important things that you should be aware of when using optimization features:

  • You should only use the tracking pixel or server-to-server post-back related to the campaign which caused the conversion.  Firing multiple pixels can lead to erroneous data, potentially resulting in false attributions.
  • Tracking pixels/server-to-server postbacks should only be placed on the confirmation page.  

Basic Integration

There are two types of conversion tracking options we have available: client pixels and server-to-server postback URLs.  They only differ in how they are integrated, one is dropped as an <img> tag, the other is implemented in the backend code by a developer.  We recommend using the server-to-server postback URL wherever possible, as it is more reliable when properly integrated.

It is important to note that basic integrations only track which campaigns are converting, to track which advertisement and which channel are responsible for the conversion, additional integration is required.

URLs for both types of conversion tracker are available on a campaign's dashboard under the "Conversion Tracking" section.

Advanced Integration

For those looking for more advanced integration options, we can attribute conversions to specific advertisements and channels.  This can be useful, for example, for A/B testing your advertisements.  This requires some work to accomplish however on the coding side, and we strongly recommend using server-to-server postback when doing this kind of integration as it requires some coding anyway.

Traditionally, there are two areas where you need to make changes in order to support advanced integrations: the advertisement itself, and the landing page flow.  If you are using an analytics platform like Voluum to track conversions, then you may not need to change your landing pages – in that case you should contact your analytics vendor.  In all cases, however, the advertisement itself must be configured to pass along the necessary data in order to ensure that the conversion is accurately tracked.

To facilitate passing information about an impression to your landing page or ad server, our platform uses a set of macros, which are replaced in the generated advertisement code which is served to the viewer.  These macros are:

  • %subid% — Advertiser Sub ID
  • %creativeid% — The ID belonging to this advertisement
  • %campaignid% — The ID belonging to this campaign
  • %advertiserid% — The ID belonging to this advertiser
  • %countrycode% — The country code of the user as determined by our systems
  • %browser% — The browser the user is using as determined by our systems
  • %devicetype% — The device type of the user as determined by our systems
  • %opsys% — The operating system of the user as determined by our systems
  • %campaign_rate_cpm% — The effective CPM for the campaign
  • %campaign_rate_cpv% — The effective CPV for the particular impression
  • %random% — A random number (useful for broken sites which require cache busting)
  • %timestamp% — A UNIX timestamp (number of seconds since January 1, 1970)

Once your landing page receives this information, it must forward back the information to our servers when you are ready to attribute a conversion to a campaign.  This is accomplished with some optional parameters on the URLs we provide:

  • ch= – the Sub ID that the conversion should be attributed to

  • ad= – the advertisement ID that the conversion should be attributed to

After you have logged some conversions, stats on your conversions will be included in the reports you pull.

  • No labels