Hello,
my name is Dimitri De Franciscis, I've worked on a version of Openads module that enables channel targeting via "source" parameter, see:
http://blog.openx.org/11/how-to-implement-easy-and-effective-ad-targetin...
http://tinyurl.com/m7rfwb

It works only with Javascript calls.

Changes from version 6.x-1.0:
- Configuration page: new "Channel targeting" fieldset, where admin can select which taxonomy vocabulary to use for targeting;
- Taxonomy term form: additional "Source" field to use when node has been assigned this term.

Example:
- create your channel on OpenX, specifying "source" parameters to use, e.g. "sport", "programming", etc.
- create "Site section" vocabulary, or use existing one;
- edit each term that needs to be targeted, e.g.: "Sports" -> "sport", "Programming" -> "programming", etc.
- you can use any "source" value, even not-existing ones;
- associate vocabulary to node types if necessary;
- when creating/updating nodes, assign a term of "Site section"

The generated Openx *javascript* calls will include "source=" parameter.

The module works fine, check it out!

CommentFileSizeAuthor
#9 openads-1-0-taxonomy_patch_source_value.patch648 bytesayalon
openads_targeting_channel_by_source.patch36.91 KBmegadix

Comments

megadix’s picture

megadix commented

I've created an archive, with pointer to openads project on drupal.org and a tutorial (italian language only, I'm working on english translation):
http://www.megadix.it/content/modulo-drupal-openx
http://tinyurl.com/lcv9zn

Hope this helps

jaydub’s picture

jaydub commented

thanks. I'll take a closer look when I get a chance. Do you know by chance if the targeting behaviour will work the same in OpenX 2.6 or 2.4 as those releases of OpenX are the ones that I am essentially targeting for support.

megadix’s picture

megadix commented

Uhm, sorry but I had time to do very little testing:
- Drupal 6
- OpenX 2.8

I think that OpenX 2.6 should work fine anyway, but don't know about 2.4... do you think it is still widely used?

Anyway, I've translated my tutorial to english:
http://www.megadix.it/node/133

Enjoy it ;)

jaydub’s picture

jaydub commented

Thanks @megadix I haven't been able to get to look at your changes in detail yet. I will respond here when I am able to look over what you have done.

andrenoronha’s picture

andrenoronha commented

hey i tried it but it can't seem to work for me.
I'm using OpenX v2.6.4

would it work only for openx 2.8?

i really need this functionality and i appreciate your modifications in the module. thanks

andrenoronha’s picture

andrenoronha commented

i have a vocab that was formerly of multiple selection. i set it to be of unique selection.
it didnt work.

i created a new vocab for test and it did work. but only with terms labeled in a single word. example: "good houses" - didnt work. "houses" - worked.

i tried some ways to discover the bug it gave me random results...so now i'm a little confused...i'm going to upgrade my openx to 2.8....

am i missing something?

andrenoronha’s picture

andrenoronha commented

i updated openx to 2.8.5 version. but that was not the problem.
i realised that the name of the taxonomy is getting it not to work.

i think the module is not using the "source" parameter field in taxonomy config to compare with the sorce field in openx. it's comparing it to the name of the taxonomy instead.

i guess it has to do with the codes in lines 247 on:

foreach($node->taxonomy as $term) {
          if ($term->vid == $vid) {
            $source = $term->name;
            break;
          }
        }

is there the attribute for openads_source_vocabulary in the term object?

srobert72’s picture

srobert72 commented

Subscribing

ayalon’s picture

ayalon commented
StatusFileSize
new openads-1-0-taxonomy_patch_source_value.patch648 bytes

Ï think the author simply forgot to finish his modification. He added the "source" via form alter to the taxonomy form but he forgot to load the "source" value when generating the javascript code.

I corrected this. Please find attached a patch that works together with the patch in post #1