Home > Paid Traffic Sources > Native

content.ad conversion tracking and optimizations (5)


10-23-2016 01:01 PM #1 milobanski (AMC Alumnus)
content.ad conversion tracking and optimizations

Hello!

A few questions for content.ad tracking and optimizations:

1. How do I track conversions in content.ad when using Voluum?
>> I'm tracking all conversions from the affiliate network in Voluum, and all custom variables from content.ad as well, but conversions aren't being fired back to content.ad.

>> I received a pixel from content.ad support, but am not quite sure where to place it in voluum or the affiliate network. I attempted both, but so far no luck (placed it directly on the offer in the network, and in voluum under "Pixel Redirect URL" under the traffic source tab. My pixel looks as follows: http://api.content.ad/Lib/TrackConve...x-xxxxxxxxxxxx


2. And what's the easiest way to tell content.ad that I want more traffic from a particular publisher/widget?

Appreciate any advice. Thanks!


10-23-2016 09:27 PM #2 maryam (Member)

1. Put these in your traffic source Voluum

Click image for larger version. 

Name:	2016-10-23_1725.png 
Views:	71 
Size:	48.9 KB 
ID:	13149

Regarding conversions, you have to put the pixel in the receipt page after customer places order

2. Bid more on that widget


10-24-2016 07:29 PM #3 milobanski (AMC Alumnus)

I'm trying to track conversions not just in Voluum, but also in content.ad. I know how to pass tokens from content.ad to Voluum - I'm trying to figure out how to go the other way around.


10-24-2016 10:25 PM #4 voluum (Veteran Member)

Quote Originally Posted by milobanski View Post
I'm trying to track conversions not just in Voluum, but also in content.ad. I know how to pass tokens from content.ad to Voluum - I'm trying to figure out how to go the other way around.
Hi milobankski,

AFAIK, content.ad don't report conversions in their own panel, thus they don't have a supported means (S2S postback or pixel) to receive this data. They're only on CPC model, but correct me if I'm mistaken.

Just for future reference -
To do the data switcheroo in Voluum, remember this golden rule - TS token - in, Var token - out.

To elaborate, each field within your traffic source template in Voluum has it's own unique identifier (actually 2) and corresponding var token (internal and specific to Voluum templates).
The two identifiers are factored on the variable field number OR name.

So, if I mapped content ad's creative ID token - [adid] to the first custom variable field and gave the name - 'Ad ID'. The var tokens which would be used to relay any ad ID data would be {var1} OR {var:Ad ID}.

Note:: Names defined in token should be an exact match of those set within template - case sensitive.



Now, let's say that content.ad provided a postback URL to receive back Ad ID + Domain data for quality score purposes.
Example PB URL -
http://content.ad/postback?adid=[adid]&domain=[did]

Their tokens would then be replaced by the internal var tokens relative of field number / name defined.
We end up with -

http://content.ad/postback?adid={var1}&domain={var3}

Note: External ID + Cost fields within template have fixed names. The respective tokens for each are {externalid} and {campaign.cpa}

The usage of the same var token format applies also to passing data to landing pages and offers within your campaign funnel also. Just make sure to do a double-check on the parameters supported to receive data on the offer.

Hope this helps in future.
Let me know if content.ad provide you with any additional info regarding 3rd party tracking (I couldn't find any reference within their documentation)

Regards,
Adrian


10-25-2016 12:01 AM #5 maryam (Member)

Quote Originally Posted by milobanski View Post
I'm trying to track conversions not just in Voluum, but also in content.ad. I know how to pass tokens from content.ad to Voluum - I'm trying to figure out how to go the other way around.
You need to place the conversion pixel (content.ad sent you in email) between the body tags of your conversion page


Home > Paid Traffic Sources > Native