Epom Help Center

Third Party Ad Server Click Tracking

Third-party Ad Server Click Tracking can be used for two purposes:

  1. To track statistics from Third-party Ad Server in Epom Analytics.
  2. To transmit statistics from Epom Ad Server to a Third Party Ad Server.

First Case

To track external statistics in Epom Ad Server, Third-party Ad Server Code should supports external click tracking.

If that is the case, Epom Click Macro – $$CLICK_REDIRECT_URL$$ – should be added before the third-party Banner code. For example:

If need be, the encoded versions of this macro are also available:

  • Encoded: $$CLICK_REDIRECT_URL_ESC$$
  • Twice encoded: $$CLICK_REDIRECT_URL_2_ESC$$

Note!

If you are provided with a code format that is different from the one highlighted above (i.e., iframe, JS), please consult with the code provider where to insert the Click Tracking Macro.

Second Case

To track Click Action statistics for Epom ads in Third-party Ad Server, the Click Macro or Click Tracking URL from that Ad Server should be inserted to the supp_click=""; string of the Invocation Code(s).

Click macros for several Third-party Ad Servers are listed below as an example:

Click macro: {clickurl}


<!-- BEGIN TAG - DO NOT MODIFY -->
          <script type="text/javascript">
          /*<![CDATA[*/
          supp_key = "90753ccb2860340d85e7ed09cda4c4f8";
          supp_channel = "";
          supp_code_format = "ads";
          <strong>supp_click = "{clickurl}";
          supp_custom_params = {};
          supp_width = "300";
          supp_height = "250";
          /*]]>*
          <;/script&gt;
          <!-- END TAG -->

OpenX also recommends that you substitute the {random} macro for [RANDOM_NUMBER] to avoid issues with client/proxy caching.

Click macro: %%CLICK_URL%%

Encoded click macro: %%CLICK_URL_UNESC%%

Twice encoded click macro: %%CLICK_URL_ESC_ESC%%
Click macro: r=[ExternalClickTrackerLink]

Third Party Ad Server Click Tracking


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.