Monetizing the calendar with Adsense or Ad Exchange (via DFP) tips?

Home Forums Calendar Products Events Calendar PRO Monetizing the calendar with Adsense or Ad Exchange (via DFP) tips?

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #906220
    tribedude
    Participant

    I have constructed my theme and have ads positioned in it where I would like them to be. There is one area I would like to put ad code – every x times under posts in calendar photo view. See private post below for image of locations….

    Since I am not going to be monetizing events with paid listings, ad revenue will be key so I am hoping to maximize this…

    Your advice would be appreciated.

    #906370
    tribedude
    Participant

    This reply is private.

    #906688
    Brian
    Member

    Hi, I can help point you in the right direction on this.

    For customizations I would reference our themer’s guide:

    https://theeventscalendar.com/support/documentation/events-calendar-themers-guide/

    That will show you how to move files to your theme to edit.

    You can look for the Photo Views starting with this file to move:

    /events-calendar-pro/views/pro/photo.php

    Then look in the photo directory for the other files.

    Let me know if you have any follow up questions.

    Thanks

    #907007
    tribedude
    Participant

    A few more questions relating to this matter:
    1) I am not really sure what to look for in those php files you suggested. I do not see anything that relates to the number of columns in the photo view content in any of them.
    2) If I I using a child theme, do I move these files in master theme/ tribe-events/? Or into a child theme/tribe-events/ directory?
    3) what does loop mean?
    4) to inject my DFP ad tags in between events in photo view, where exactly should the ad code go? In what file?

    Thanks,

    #907104
    Brian
    Member

    I can answer your questions as best I can, but we are unable to provide coding for customizations nor can we troubleshoot each step. So my answers related to the Events Calendar are as specific as I can make them, but things such as the loop I am going to be very general.

    1) I am not really sure what to look for in those php files you suggested. I do not see anything that relates to the number of columns in the photo view content in any of them.

    The columns are generated by css and then using the Isotope script.

    http://isotope.metafizzy.co/

    2) If I I using a child theme, do I move these files in master theme/ tribe-events/? Or into a child theme/tribe-events/ directory?

    Place them in the child theme.

    3) what does loop mean?

    The loop is a php term and used in WordPress to run to process posts and other similar content. This article explains more about it:
    http://codex.wordpress.org/The_Loop

    4) to inject my DFP ad tags in between events in photo view, where exactly should the ad code go? In what file?

    You can add it under the content of the photo view for an event by placing it in this file after moving it to your theme:

    /events-calendar-pro/views/pro/photo/loop.php

    Under this line:

    <?php tribe_get_template_part( ‘pro/photo/single’, ‘event’ ) ?>

    but before the closing div ( </div> )

    If you place it there it will show under every event though. It is beyond the support we can provide to create a counter here to only target certain events to place the coding in.

    That is about as much help as we can provide on this.

    Thanks

    #932205
    Brian
    Member

    This thread’s not seen much activity for the last couple of weeks – and there’s not too much more we can offer here given its a customization – so I’ll go ahead and close it. Of course if you still need help with this or any other issue please don’t hesitate to create a new thread (or threads) and one of the team will be only too happy to help. Thanks!

Viewing 6 posts - 1 through 6 (of 6 total)
  • The topic ‘Monetizing the calendar with Adsense or Ad Exchange (via DFP) tips?’ is closed to new replies.