Home > Questions and Answers > Tracking Questions

---

Decisive + Appflood ? (7)

---

Hey guys,

I've had several conversions come through my network (Appflood) but no conversions are being recorded in my traffic source (Decisive), can someone take a look at my screen shots and see if they can spot what i've missed?

Thanks

Appflood





Decisive

---

Question: do you want to use Voluum or not?

At the moment your Decisive ads direct link to your Appflood URL so Voluum is skipped entirely. Is this intended?

If not, you should add Decisive as a traffic source in Voluum. Use the template. If you have entered everything manually, check that it is the same as the template as this will make things easier.

Make a campaign in Voluum with Decisive as the traffic source and your Appflood URL as the offer, with the affiliate URL as hxxp://appflood.go2cloud.org/?aff_c?offer_id=1234&aff_id=5678&aff_sub2={clickid } (note, don't use this format obviously not the entire URL verbatim...)

Set your Decisive ads to use your Voluum campaign URL. Voluum will be automatically set up via the template to pass Decisive's tracking token and fire it back upon conversions.

Now at your network end you are passing Voluum's click ID as aff_sub2, so remove all othe postback URLs and add just the Voluum one you have added - it is correct.

That should reconcile your tracking.

---

Thanks Zeno but i was actually planing on not using decisive.

I wasn't very clear about this and should have removed that Voluum postback url (i used Voluum originally but decided to just use decisive tracking to keep it simple for now).

Just looking at the pics again, could you see any reason why decisive isn't getting the conversion data? (so with voluum out of the picture)

Once i fix this i'll definitely send you a beer across the Tasman!

---

Oh, so you mean you aren't going to use Voluum? (may have typo'd in your latest post).

If you use the Appflood link that I see in the picture then the issue is with your Postback URLs at Appflood.

Firstly, remove the Voluum one and one of the Decisive ones.

Secondly, change the Decisive one to hxxp://win.crwd.io/convert/{aff_sub2}

The token {{{bidhash}}} means nothing to Appflood. You need to pass back the value that {{{bidhash}}} transforms into at Decisive's end. In your URL at Decisive you have ...aff_sub2={{{bidhash}}}...

For a real click this will become e.g. ...aff_sub2=sf82jsa902isu2d2k....

This value is now stored under aff_sub2 at Appflood so you need to use the {aff_sub2} token to pass it back to Decisive in the postback URL.

---

Lol, yeh sorry, i might have confused things by leaving the postback url from a previous attempt with voluum in appflood.

Beauty, thanks dude i've made all those changes and will wait for that next conversion to make sure it's working.

So just to make sure i've got my head around this correctly....

1)We first take the affiliate network (in this case appflood) url and then edit it so that the right values are passed through. (in this case AusGroc1 is the name ive chosen for the campaign, {{{bidhash}}} represents the ID of the user/click and varies from traffic source to traffic source and we use aff_sub2={{{bidhash}}} to tell Decisive that aff_sub2 represents the individual ID of the user, and in this case aff_sub3={{{creative_id}}} is irrelevant since all the info is passed through aff_sub2?)

2)Once we have the completed affiliate link we take that and put it into our traffic source (Decisive) and then take the postback from the traffic source(Decisive) and post that on the offer page at the affiliate network, Appflood. Even though Decisive gives the postback URL as {{{bidhash}}} we change this to the placeholder variables of the affiliate network,{aff_sub2}, so that the affiliate network knows what data (ID of click/conversion details) to send back to the traffic source?

FROM APPFLOOD

http://appflood.go2cloud.org/aff_c?offer_id=247&aff_id=3718&aff_sub=AusGroc1&af f_sub2={{{bidhash}}}&aff_sub3{{{creative_id}}}

FROM DECISIVE

http://win.crwd.io/convert/{aff_sub2}

The Decisive Conversion pixel is given as

http://win.crwd.io/convert/{{{bidhash}}}

Is that all correct?

---

1) Correct. Be aware {{{bidhash}}} is the token for Decisive only and yep, this varies per click and on different traffic sources (which support this kind of tracking), these IDs and the token will be different. All the info you need for tracking conversions is indeed passed through aff_sub2, so aff_sub3 gives you extra reporting info at Appflood but is irrelevant to tracking conversions at Decisive.

2) Yes, correct. Tokens are specific to a platform so we have to use whatever Appflood is programmed to interpret, in this cass {aff_sub2}.

All your links are correct - note the Decisive pixel is given with the {{{bidhash}}} token just to let you know that {{{bidhash}}} parses to the value that needs to be passed back.

It's more concise than saying:

"http://win.crwd.io/convert/ID_HERE" where "ID_HERE" is the 40-character string of text that the {{{bidhash}}} token evaluates to when used in advert URLs.

---

Brilliant, all of this is actually making sense to me which definitely wasn't the case this time last week, thanks dude!

---

Home > Questions and Answers > Tracking Questions