Home > Tracking Campaigns > Voluum

---

Voluum + Decisive = 404 errors (8)

---

I setup tracking from Affiliaxe to Voluum to Decisive. Conversions are showing in Voluum but not being sent to Decisive. An error is reporting in Voluum that says:

Postback sending error
Unexpected HTTP response code: 404
http://win.crwd.io/convert/

My settings are as follows:

Voluum Campaign URL: http://0nxyx.voluumtrk.comXXX?crtv={{{creative_id}}}&bidh ash={{{bidhash}}} (ENTERED INTO DECISIVE AD)

Voluum Traffic Source: See screenshot

Affiliaxe Postback: http://0nxyx.voluumtrk.com/postback?cid={aff_sub} (THIS IS OBVIOUSLY WORKING SINCE I'M GETTING CONVERSIONS IN VOLUUM)

I had 4 conversions error in the last 12 hours. 2 were direct linking and 2 were from LPs.

What am I missing? Thanks

---

I don't have a space in "bidhash" here. The forum text editor is adding that.

---

I think I may have figured this out. My Decisive ads were using a Voluum campaign URL with a custom variable rather than the external ID (in the traffic source setup, see screenshot above). I had fixed this in Voluum but not yet submitted the new URLs in Decisive. So the URL was http://0nxyx.voluumtrk.comXXX?crtv={{{creative_id}}}&subi d={{{bidhash}}} and "subid" was just a custom variable. I submitted the new URLs in Decisive so we'll see if future conversions track to Decisive.

Custom variables are only for Voluum reporting. I think you need to use the External ID to send back the bidhash to Decisive.

Hopefully that helps someone else.

---

That was most certainly the issue.

You hadn't programmed Voluum to expect a custom variable called subid, so it would not log it and therefore the bidhash was lost.

You can use any variable - externalid included - in the postback for conversion tracking. The externalid is just there so that you can use it consistently between traffic sources. If you could only use externalid then it would be impossible to use postbacks that require more than one piece of data sent back.

You should pass as much information from Decisive as possible.

The custom variables are there to provide insight into campaign performance. Only passing creative ID creates a situation where you are throwing away a lot of Voluum's reporting and insight power. Data is money, collect it even if you don't know how to use it.

---

I was using subid={{{bidhash}}} in the URL so that wasn't keeping it from working based on what you're saying. I had a conversion today and it tracked to Decisive using externalid so I'm just using that from now on.

I also found that Voluum has presets for popular traffic sources including Decisive with all the variables entered. However, some of them are tracked automatically by Voluum so it may not be worth passing more info that might just slow things down.

I'm starting to realize how valuable all this data is just from seeing a handful of conversions tracked in Voluum

---

Oh, you mean subid was configured as a custom variable so was being tracked fine? Where you then using {var:subid} or {varX} (where X = the custom variable number) in the postback?

Also, you should pass data like Device Type and so on from the traffic source as well where possible. It won't slow anything down. Logging data like this will have submillisecond impact on processing speeds. You could probably add 100,000 key/value pairs to the URL and the database writing would still have negligible impact on your redirect speeds. In fact, it is probably designed to not wait for any logging processes before redirecting (i.e. do it asynchronously).

Anyway, the device type, OS version, ISP etc. that the traffic source passes is useful even though Voluum detects this automatically. Why? Because they may differ due to different databases used, and you can now look at the data and see that.

Furthermore, if you find that some OS/Devices/etc. are working better than others, do you want to optimise at the traffic source with Voluum's opinion on device types, or the traffic source's opinion? Whether the traffic source's data is more accurate or not is irrelevant - it's what is actually used in your targeting.

---

Hi webeminence,

I think I have the same problem, but I didnt get how you fixed it. Here are screen shots and some codes of mine. Could you help me please?



OFFER URL:
http://adtrking.com/?a=476409&c=77506&s1={campaign.id}&s2={os}&s3={cou ntry}&s5={clickid}

Campaign URL:
http://wjmtw.voluumtrk.com/13de6ed5-4d14-4ca5-9a57-e851deef917e?media={{{media}}}&app={{{app}}}&site= {{{site}}}&placement={{{placement}}}&cat={{{catego ry}}}&device={{{device}}}&isp={{{carrier}}}&os={{{ os_version}}}&cid={{{creative_id}}}&adid={{{ad_id} }}&bidhash={{{bidhash}}}



How i got all this... i followed this video on http://stmforum.com/forum/showthread...ll-Video-Guide

please any help would be great! thanks
stekoh

---

What is your advanced setup for the traffic source in Voluum?

The postback looks to be setup fine and is firing but the information being sent back is not valid, which is generally due to the data you have initially passed or an error in the configuration (a single incorrect bracket will break it).

---

Home > Tracking Campaigns > Voluum