- Joined
- Apr 17, 2018
- Messages
- 22,789
That also should be what is on https://affiliates.mobipium.com/pixel
It sounds like that is working for other peopleHey Luke, it says trk in the Affiliate network query string parameter field instead of cid... should I just enter that in Mobipius?
View attachment 26124
You can find their documentation here: https://doc.voluum.com/?lang=enWould it be possible to direct me to an article with Voluum as a tracker?
Use cid since that's what we used in the guide.
Glad trk worked for you but I do believe cid should work if it's in both spots properly. Glad it's tracking!Hello. I would like to share my own newbie experience of setting postbacks (and probably to save at least $5 and a little(not a little, tbh) time for someone . During the campaign setup, I made several mistakes.
TLDR;
- Check your setup before run.
- If you have incorrectly tracked statistics on bemob, meaning that it doesn’t show conversion properly, however on mobipium it is, then you certainly incorrectly configured the postback. Make sure your settings follow the guide.
- If everything matches, however, the error remains replace cid with trk in postback on mobipium and in use trk as network query string parameter for BeMob click ID
My mistakes
- Always check whether you setup your campaign, offer, etc correctly before run. For example, I forgot to specify Affiliate Network in one of the offers. In accordance, this offer would not be tracked.
offer errors that the support team indicated to me
Error 2
@Luke indicated using cid unique tracking parameter
However, in my case, it did not work and the traffic was not tracked
offer errors that support showed me
I have read all thread in steps 7,10 completely. And I often found the same problems: here, here, here here, here, and many others. Although, as far as I understood, they had used different parameters in mobipium and bemob, or other inconsistencies. In my case both places had cid. Furthermore, there were cases where they used trk in both places and it helped them. As the result, I got confused because everyone had solved the problem in his own way, and it seemed that everyone was successful. (Some put cid in both places, others trk)
After investigation, I decided that I also messed up the parameters. After careful checking and making sure that in both places cid is used I ran the campaign again... I've spent $5 more to end up with nothing. The statistics were displayed incorrectly.After that, I finally asked the support team of bemob for help and described the problem. After some time, support connected to me and requested temporary access. They discovered the problem, indicating to me that I should use a parameter trk instead of cid for tracking. After some time, I started a new campaign by replacing cid with trk in mobipium and bemob
AND IT WORKED!
I finally got the first statistics tracked by bemob
Lesson learned
1 Before asking something it is worth rereading the thread, it’s likely that someone already has faced your problem (how many times have I heard this)
2If the problem is new, don't hesitate to ask for help. I believe that I have saved my time not writing to the thread for help but immediately to support. Nevertheless, I share this information with you on the forum. I hope my experience will help someone to set up their campaign easier.
It's important that the two match. I recommend reading what @Tenzin said here:instead of cid I put trk is that okay? Or leave it as cid?
Yes, you are correct about everything above. I believe the multiple callbacks is if you have multiple postbacks you want to fire (not a fallback). I've only ever used the Primary one though.Just to check if I understand things correctly but we are basically doing 2 things here, correct?
1. We specify on MOBIPIUM the parameter we use in the offer URL of which its value will be "loaded" in the tid "variable" on MOBIPIUM.
2. We specify on MOBIPIUM the callback URL (i.e., the URL they need to call when a conversion happend).
So lets say we have the offer URL: https://xxxxx.mobipiumlink.com/?mob=yyyyy&cid=42, here cid is the parameter in the URL that represents our BeMob click id.
MOBIPIUM will "store" the value of this parameter (42) in the "variable" tid (but only if we tell it to do so, which we do by saying cid is one of our unique tracker parameters).
If a conversion happens MOBIPIUM will let our tracker know by calling our callback URL with the click id the conversion happened for (42). Since that value 42 is stored in the variable tid on MOBIPIUM we pass it into the callback URL. We surround tid with curly braces in the URL such that MOBIPIUM knows it needs to replace it with its value (42).
So, to get it working its important that the name of the click id parameter in the offer URL (which we set in BeMob) is exactly the same as the the one we provide to MOBIPIUM as the first one of our unique tracker parameters.
Is this correct?
Also, why can we set these parameters and callback URL 3 times? View attachment 40087 Is this useful if you want to pass a single conversion to 3 trackers at the same time? Or is it like a fallback-mechanism? That if the "primary" callback URL does not work, it will use the second one and if that one does not work, the third one?
Thanks!
these are already tracked as Visits/unique visits on Bemob
you can check this guide for a permanent solution for this
this is usually 2 or 3 visits with Referre google.com with a cost of 4-5 $ that miss with your statistics
these are already tracked as Visits/unique visits on Bemob
View attachment 40535
and Bemob Recording 10800, with around 7000+ Clickloss "which is really huge% "around 40%
Check for zone id with a very big difference in visits between Popads and Bemob, Also be sure both Bemob and Popads in the same time zone