Home > Paid Traffic Sources > Native

---

Revcontent not tracking conversions (15)

---

Has anyone had this issue lately?

I've had a few campaigns running for months with no issue and now over the past 2 weeks 90% of my conversions do not track. Nothing has changed in my setup on Voluum or on my websites. When I manually try to send the conversion by going to the postback url it returns 'null' and Voluum has confirmed this is happening with most postbacks on their end too.

I spoke with revcontent support and after a week of them continually telling me its my fault they admitted that the data I am sending to postback is correct and they don't know why its failing to track. They also told me there is nothing they can do to fix the problem.

Best part is after I said I will stop running money there if I can't get it fixed 2 of my campaigns that have been running for months were retroactively denied

---

Have you tried posting back conversions to your RevContent url using your browser and see in your browser's console what type of message do you get?

Practically that would help you get a better idea if revcontent's postback is accepted or refused, by simply looking at the response.

---

I’ve been having this issue too. I’m also using post back URL to pass conversions but Revcontent isn’t showing any of my conversions. Curious to see if other people are experiencing this as well.


Sent from my iPhone using Tapatalk

---

@platinum Sadly it only returns 'null'. I've sent RevC a list of these rc_uuid's and they confirmed they are real id's, but have no clue why they are returning null. They don't seem to keen on figuring it out either which is why I wanted to see if other people are having this issue. If a few of us complain it will cause a bigger stink than just one.

---

I am thinking now that I may not have my postback URL setup correctly. Would you mind verifying if it looks correct?

This is the postback URL:

https://trends.revcontent.com/api/v1/conversion.php?api_key={98b0363xxxxxxxxxxxxxxxa35} &uuid={rc_uuid}&amount={payout}

And this is the destination URL (or campaign URL):

https://rewardnice.com/f704260f-2b3f-46fd-8a61-c70eb87f1687?widget_id={widget_id}&content_id={con tent_id}&boost_id={boost_id}&adv_targets={adv_targ ets}&rc_uuid={uuid}

In the report breakdown in Voluum I can see that it is storing the Revcontent unique ID's for each click, it just doesn't seem to be sending them back correctly...

Also, does passing conversions back to Revcontent make a difference in campaign performance?

---

Make sure to remove the curly brackets from the API key value. Your postback url should look like below:

Where NNN equals Revcontent's Unique click id and $$$ the payout amount.

If you're keeping the curly brackets {} on your API key, most probably they are causing the issue.

---

Damn haha I should've noticed that... thanks man I appreciate it.

---

Glad you got it fixed @bhal07! Wish my fix was that easy.I'm having same issue as OP and Since SOME of my conversions fire, my url is correct but it just isn't working 100% of the time. Pretty mind boggling as to why.

---

nice

---

Been reading through this myself this late night, for Voluum (https://intercom.help/revcontent2/en...s-using-voluum) it says:

"To correctly track conversions back to the Revcontent you should use a tracking pixel from Voluum. You should place it after the conversion actually takes place, i.e. on the thank you page or in the appropriate place in your affiliate network."

This means normal S2S won't work properly? Or the "complex" clickbank conversion tracking?

---

If you use Revcontent's conversion tracking pixel to pass conversions from Voluum to Revcontent, you need to use Voluum's conversion tracking pixel to track conversions in Voluum. You can't mix S2S and cookie-based methods in this case - if you report conversion information to Revcontent with the cookie-based solution, Voluum has to get this information using the same type of solution.

According to this documentation, you need to set up the Revcontent conversion tracking pixel for each Revcontent campaign in Voluum separately. To do so, you have to:
1. Generate the pixel on the Revcontent site by choosing CPA ROI slider in the Revcontent’s campaign setup (screen from their doc)
2. Convert corresponding Revcontent campaign in Voluum to advance campaign. Edit campaign -> Convert to advance campaign (screen)
2. In the Destination tab expand Conversion reporting to traffic source -> Pixel redirect URL -> Unique for this campaign -> paste the pixel from Revcontent. (screen) ​

HOWEVER...

From what I know our users successfully use the S2S postback URL method to pass information about conversions from Voluum to Revcontent. As it is a more reliable solution and it does not rely on cookies I would recommend using it instead of the Pixel redirect URL. The additional prop is that you will not have to set it up for each campaign separately, it needs to be added in the Traffic source - Revcontent settings.

In order to pass conversions with Postback URL, you need to edit the Revocntent traffic source in Voluum and perform the following steps:

1. Map parameters for External ID. Recvontent uses rc_uuid parameter and <uuid> token to pass unique ID for visit. The setup should look like in the screenshot.

2. You need to configure your postback URL. Revcontent has 3 required parameters that need to be added in the postback URL:
- api_key - need to be matched with API access key
- rc_uuid - unique ID need to be matched with Voluum {externalid} token
- amount - need to be matched with Voluum {payout} token

So please get your Revconten API access key and configure your postback URL it, should look like the example below:

https://trends.revcontent.com/api/v1/conversion.php?api_key=put_your_api_key&rc_uuid={externalid}&amou nt={payout}
​
3. Paste configured postback URL in the Traffic source postback URL field.
​
4.. Please remember when you change the setup for traffic source the campaign URLs of this traffic source campaigns will also change, so you have to copy them and submit as a Destination URL on the traffic source site.

However, in this case to the Campaign URL rc_uuid=<uuid> will append and you have to remove it before you set it as the Destination URL on the Revcontent site. According to their documentation, this parameter will automatically be appended to your Destination URLs following a click event.
​
Once you finish the setup, when information about conversion will be passed to Voluum, Voluum will pass it to Revcontent with Postback URL.


Karolina

---

Hi Karolina / @voluum Voluum ,

Just following up on your reply - I am trying to set this up myself and i'm a little confused...

In the s2s example link you said the link should like like this example

"https://trends.revcontent.com/api/v1/conversion.php?api_key=put_your_api_key&rc_uuid={externalid}&amou nt={payout}"

but then you said "However, in this case to the Campaign URL rc_uuid=<uuid> will append and you have to remove it before you set it as the Destination URL on the Revcontent site.

So which one is it? Do we add the token rc_uuid={externalid} or remove it?

Thanks

---

Hi Karolina / @voluum Voluum ,

Just following up on your reply - I am trying to set this up myself and i'm a little confused...

In the s2s example link you said the link should like like this example

"https://trends.revcontent.com/api/v1/conversion.php?api_key=put_your_api_key&rc_uuid={externalid}&amou nt={payout}"

but then you said "However, in this case to the Campaign URL rc_uuid=<uuid> will append and you have to remove it before you set it as the Destination URL on the Revcontent site.

So which one is it? Do we add the token rc_uuid={externalid} or remove it?

Thanks

---

Hi Karolina / @voluum Voluum ,

Just following up on your reply - I am trying to set this up myself and i'm a little confused...

In the s2s example link you said the link should like like this example

"https://trends.revcontent.com/api/v1/conversion.php?api_key=put_your_api_key&rc_uuid={externalid}&amou nt={payout}"

but then you said "However, in this case to the Campaign URL rc_uuid=<uuid> will append and you have to remove it before you set it as the Destination URL on the Revcontent site.

So which one is it? Do we add the token rc_uuid={externalid} or remove it?

Thanks

PS. sorry it's bold text, i can't turn it off

---

Hi Karolina / @voluum Voluum ,

Just following up on your reply - I am trying to set this up myself and i'm a little confused...

In the s2s example link you said the link should like like this example

"https://trends.revcontent.com/api/v1/conversion.php?api_key=put_your_api_key&rc_uuid={externalid}&amou nt={payout}"

but then you said "However, in this case to the Campaign URL rc_uuid=<uuid> will append and you have to remove it before you set it as the Destination URL on the Revcontent site.

So which one is it? Do we add the token rc_uuid={externalid} or remove it?

Thanks

Ps. sorry it's bold text, i can't turn it off

---

Home > Paid Traffic Sources > Native