Jump to content

andrewatfornax

Approved members
  • Posts

    2007
  • Joined

  • Last visited

Posts posted by andrewatfornax

  1. Yes, you almost certainly can - easiest way would of course be to restore from backup, but if you don't have that, put a clean install in a new DB, and look at the default account details, and insert those again with SQL?

  2. Well - what you could do is either:

     

    1. Set up different zones for logged in/not logged in users, and use your CMS or other code to display the appropriate zone to logged in/not logged in users, and traffic banners to the zones accordingly; or

    2. Pass in a targeting variable to your zone tag via the CMS or other code, indicating if the user is logged in or not, and use delivery limitations to target banners accordingly.

  3. Normally, I would expect this is because the page impressions are recorded at the top of the page, but banner impressions depend on the banners actually loading; when site performance means pages take more than a second or so to load, you'll start to get an increasing variance between page impressions and banner impressions as load time decreases.

  4. Hi hogiro,

     

    I think that *probably* the best you could do, based on the Revive Adserver UI and according to http://dev.maxmind.com/geoip/legacy/csv/?rId=revive would be the Legacy Region database, as that seems to include Germany as a county, and then various regions within Germany.

     

    It does not appear to me that the US/Canada postal code delivery option has a database from MaxMind (in the legacy format, which is what Revive needs) that supports postcode-level targeting for Germany.

     

    Unfortunately, I have not yet had a chance to fully re-test the targeting functionality here as part of the ongoing documentation project, so can't say for sure at this stage. On the todo list!

  5. Unfortunately not. We can't tell from the above post if the 404 is from your adserver (in which case, something has gone wrong with your server - you will need to investigate yourself or speak to your admin team), or if it's from the banner's target server (in which case, something has gone wrong with the site the banner is linking to - you will need to speak to the administrator of that server).

     

    HTH,

  6. Hi omenicus,

     

    Alas, that link is not for anything associated directly with the Revive Adserver team (and isn't loading for me anyway), so I'm afraid we really can't comment on what it is.

     

    Best bet would be to contact the appropriate people for that link.

     

    Cheers,

     

    Andrew 

  7. Most likely explanation: Your OpenX installation is on faster hardware than your Revive Adserver installation. As a result, your OpenX served banners appear quickly, and the impressions are therefore more likely to be logged; your Revive Adserver banners are served more slowly, and users are more likely to navigate away from the page before they have loaded, and so there are fewer impressions logged. 

  8. Thanks for the feedback! 

     

    I don't think there is any specific need for Revive Adserver to have any given number of CPU cores - rather, it's more likely that this is simply the level of CPU power your specific installation requires to cope with the load you have.

     

    Did you change to asynchronous tags at all? One thought might be that if you did, then Revive Adserver is now trying to do more work in parallel than before (rather than doing all ad serving serially), and so this may have affected the level of performance you need for your specific installation...

     

    Hope that helps.

  9. Thanks for the feedback - and good to know that it's down to the network speed, rather than something wrong with the asynchronous tag.

     

    A thought - would you be able to mix the two types? Use the normal SPC tag on pages where users are likely to navigate quickly, but asynchronous on pages that are more content focused and users may stick around longer?

  10. This is a complex (and incompletely described, as I don't know what banner/campaign to zone links exist) scenario.

     

    Can you please try a more simple scenario?

     

    Campaign A - One banner; Campaign limited to 5 views.

    Campaign B - One banner, no capping.

    One zone. Both campaigns linked to the zone.

     

    I've tested this with both Asynchronous and JS tags, and in both cases, I see a mix of the campaign A and campaign B banners in the zone until I've seen the campaign A banner 5 times, and then I only see the campaign B banner.

     

    Can you get it to show the campaign A banner more than 5 times with this setup using the Asynch tag? 

×
×
  • Create New...