Click ID with FlashTalking Ad Server
  • 3 Minutes to read

    Click ID with FlashTalking Ad Server


      Article summary

      The article describes how to enable Enhanced Attribution for Yahoo Click ID in the FlashTalking ad server. The focus is on 3rd Party Hosted (Ad Tag) and Yahoo Hosted (Img 1x1 Click Tracker) implementations in the FlashTalking ad server. Note: Yahoo is currently working on a more permanent solution with FlashTalking.

      Important

      This setup involves using a FlashTalking universal macro. This means that a client could be using the macro for another use case. Check with the client beforehand to consult.

      The parameter and macro that Yahoo looks for to populate is vmcid=${CC}. It is intended for all ad types. Multiple options exist for separate ad types. In the sections below, you’ll find Display, 1x1s and VAST tag types.

      Display

      1. Add the ${CC} macro to an ft_custom (ft_c1) parameter via PIE tag.

      2. Apply an Event Tag to pass along the populated value via an ftqs macro

      3. Append the clickTags with the custom macro: vmcid=[ftqs:[ft_c1]], allowing for ft_c1 to be replaced with Yahoo’s macro from step 1.

      Step 1

      The PIE tag shown below can be used to add the Yahoo click macro to the body of the Async tag. This should be added only on the specific site (i.e., Yahoo) that are Yahoo properties being used for that advertiser campaign.

      Important

      This assumes you want to use ft_c1 and that ft_c1 isn’t being used for any other Data Pass. Check with a FlashTalking Solutions Engineering and/or Technical Services before you implement.

      Step 2

      The Event Tag shown below should also be added. This is to grab the values passed into FT tag variables and use them to replace custom macros within third-party tags.

      Important

      Be sure to check with Technical Services/Bitbucket for the latest version of this.

      Step 3

      Add the parameter/macro vmcid=[ftqs:[ft_c1]] to the Flashtalking clickTag. ft_c1 should be replaced with whatever variable was used in Step 1, i.e., vmcid=[ftqs:[ft_custom]] if ft_custom were used.

      If vmcid=${CC} already exists in the click suffix, completely replace it with the above.

      clickTags Example

      https://www.flashtalking.com?vmcid=[ftqs:[ft_c1]]
      https:/www.flashtalking.com?UTM=12345&vmcid=[ftqs:[ft_c1]]

      1x1s

      Append vmcid=${CC} to the clickTag.

      Since the DSP will have direct exposure to the Flashtalking click tracker, there is no need to add a custom ftqs macro here.

      Example

      https://www.flashtalking.com?vmcid=${CC}

      Advise the DSP to only implement the Normal Click Command ClickTag and not the Updatable Click Command ClickTag, so that the macro can be exposed to the DSP and noting that URL changes would require a tag update/swap.

      Example

      It may be worth removing the Updateable Click Command from the tag export sheet completely. This can be performed by doing the following:

      Find: <!– Normal Click Command1*

      Replace: (blank)

      Important

      This means that if the landing page URL is updated, a click tracker update/swap will be required within the DSP.

      VAST

      Similar to Display, this requires editing of the Flashtalking tag itself, in addition to a modification to replace the ${CC} macro within the click suffix.

      Follow these steps:

      1. Add the ${CC} macro to a custom parameter within the VAST tag, i.e., ft_c1

      2. Update the click suffix so that you are replacing the macro ${CC} in the vmcid=${CC} suffix with a custom EL parameter, i.e., vmcid=[%EL: param[“ft_c1”]%]

      Step 1

      It is recommended that New Tag Generation be used here. This will allow you to see what variables are currently populated and decide where to add the ${CC} macro. This can be accompished in the Video Settings at the Site Level.

      Example

      Step 2

      Add the parameter/macro vmcid=[%EL:param["ft_c1"]%] to the Flashtalking clickTag. ft_c1 should be replaced with whatever variable was used in Step 1, i.e., [%EL:param["ft_custom"]%] if ft_custom were used.

      If vmcid=${CC} already exists in the click suffix, completely replace it with the above.

      clickTags Example

      https://www.flashtalking.com?vmcid=[%EL:param[“ft_c1”]%]
      https:/www.flashtalking.com?UTM=12345&vmcid=[%EL:param[“ft_c1”]%]

      Important

      If you have any questions, contact your Account representative.


      Was this article helpful?