GameLedger reaches people who are already holding the phone, halfway through deciding what to install. That is a useful audience for anyone selling games, controllers, power banks, cloud saves, emulators, accessibility tools or mobile subscriptions, and a useless audience for most other things. We will tell you if we think your campaign does not fit.
1. Who we work with
Most of our readers are in the United States, the United Kingdom, Australia and Canada, reading on a phone, mostly on a mobile connection. That shapes what performs here. Campaigns that are designed for a desktop screen, or that need a long form to convert, do badly.
We are a good fit for: Android and cross-platform game publishers, hardware and accessory brands, mobile gaming services, emulator and launcher projects, and anything a player buys after they have already decided they want the game.
We are a poor fit for: crypto, betting and adult offers, payday loans, weight-loss claims, or anything that needs a desktop to work. We will decline those, and we do not need to explain why in a pitch deck.
2. Ad formats
The site runs through Google AdSense, and placements are reserved and clearly marked in the markup. Three formats are available.
2.1 Standard display
Fixed-size display units in the reserved slots. The header placement takes a leaderboard on desktop; the in-feed placements take a medium rectangle on desktop and a fluid unit on mobile. These are the workhorse units and they carry the lowest cost per click.
2.2 Responsive display
Fluid units that resize to fit the available width — a 728×90 leaderboard on a wide screen, a 320×100 banner on a tablet, a 300×250 rectangle on a phone in portrait. This is the recommended format for most campaigns, because it avoids the awkward gaps that a fixed unit leaves behind on a narrow screen. Each unit reserves its space before it loads, so the page does not shift while you are reading it.
2.3 Native and in-article
Native units that match the surrounding page, used for app promotions and for campaigns that need a picture and a line of copy rather than a banner. These are sold in blocks and booked with a minimum run. Native placements are visually distinct from our editorial cards and are never inserted into a review, a rating summary or a rating bar.
3. Where the placements are
Every ad slot on the site is reserved, labelled and separated from the content by a clear margin and a visible "Advertisement" or "Sponsored" label. The reserved slots are:
- Header — below the site header, above the page content. On desktop it sits above the fold; on mobile it sits below it.
- In-feed — between content blocks on game pages, category pages and editorial pages, spaced well away from surrounding text.
- Sidebar — a 300×250 unit, sticky on desktop only. It does not exist on mobile, because there is no room for it and a sticky unit on a phone is an irritation rather than an advertisement.
- Footer — above the site footer, on every page.
We do not run interstitial pop-ups, auto-playing sound, full-screen takeovers, sticky elements that cover the content, or anything that scrolls with the page. We do not run ads inside the review list, inside a rating summary, or immediately next to a "View on Google Play" button in a way that could be mistaken for the developer's own call to action.
4. Editorial independence, in writing
Buying an advert on GameLedger buys an advert and nothing else. It does not buy a rating, a chart position, a review, a mention in a category page, or the removal of a criticism. We will not write a paid review without a visible and unambiguous label, and we will not put an advertiser's product at the top of a "best games" list. If your product is covered on the site and we think it is bad, we will say so whether or not you buy from us.
Full detail is in our Editorial Policy.
5. Enquiries and rates
Rate cards and a media kit are sent on request rather than published, because we update them as inventory and traffic move. Email support@gameguide003.northfivefun.com with the subject line "Advertising enquiry" and we will send you the current rates and availability. We aim to reply within five working days.
Useful things to include: the product, the countries you want to reach, the format you are interested in and the budget you have in mind. If you tell us the budget up front, we can be honest about whether the campaign is worth running here, which saves you both a conversation later.
6. House rules for campaigns
- Your landing page must be mobile-first, fast, and not interstitially gated.
- No deceptive download buttons, no fake "Play" icons, no system-mimicking UI, no countdown timers designed to trick.
- No claims we cannot verify, no misleading "editor's choice" wording, no implication of an editorial relationship in the creative itself.
- No malware, no misleading system notifications, and anything targeting Android must respect the Play Store's own policies.
- We reserve the right to decline a campaign that would damage reader trust in the site, and to pull a campaign that generates reader complaints.
7. Technical notes for the site owner
The following snippets are commented out on purpose. The site is published with no live advertising script, no ad-client ID and no publisher ID, so that it can be reviewed and approved before anything loads for a reader. Uncomment and fill in the placeholders only once an AdSense account has been approved and the slots have been configured in the AdSense dashboard.
7.1 AdSense snippet — to be pasted into the ad slots
Each reserved slot in the markup carries a data-ad-slot attribute
(header, in-feed, sidebar, footer) and a
data-ad-format attribute. The loader should read those and insert one ad unit per
slot. Do not place a single unit inside a slot that is meant to hold several.
<!-- GOOGLE ADSENSE — uncomment after account approval.
Replace ca-pub-XXXXXXXXXXXXXXXX with the real publisher ID and
replace PUBLISHED_SLOT_ID with the ad unit ID from the AdSense dashboard.
Keep this script in the <head> of every page. -->
<script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-XXXXXXXXXXXXXXXX" crossorigin="anonymous"></script>
<!-- EXAMPLE UNIT — uncomment and duplicate per slot.
The ins element must be a direct child of the reserved .ad-slot container. -->
<ins class="adsbygoogle"
style="display:block"
data-ad-client="ca-pub-XXXXXXXXXXXXXXXX"
data-ad-slot="PUBLISHED_SLOT_ID"
data-ad-format="auto"
data-full-width-responsive="true"></ins>
<script>
(adsbygoogle = window.adsbygoogle || []).push({});
</script>Keep the reserved min-height on each slot so that the page does not shift
when the unit loads. Do not remove the visible "Advertisement" or "Sponsored" label, and do
not position any ad so that it could be mistaken for a navigation element, a game card or a
button belonging to the site.
7.2 ads.txt — to be created at the site root
Create a file named ads.txt in the root of the domain,
https://gameguide003.northfivefun.com/ads.txt. It must contain exactly one line: the
authorised publisher ID for this domain, with no ad-client ID, no comments and no extra
whitespace.
# ads.txt for gameguide003.northfivefun.com
# Uncomment and replace with the real authorised publisher ID from AdSense.
# google.com, pub-XXXXXXXXXXXXXXXX, DIRECT, f08c47fec0942fa0For a reseller or an agency selling on your behalf, add one further line per authorised
seller, for example google.com, pub-0000000000000000, RESELLER, f08c47fec0942fa0.
The IAB technical lab ID is included in the example above; replace it with the one from your
own AdSense account if it differs.
7.3 Consent — required before you switch the ads on
This site deliberately ships with no cookie banner, so there is no built-in flag for the loader to check. If you serve this site to readers in the EEA, the UK or Switzerland, you must add a consent mechanism before the ad script loads. Google AdSense enforces this through its EU User Consent Policy: without a valid consent signal, your ad requests are served without personalised advertising and you can be asked to fix it.
The two practical routes are (a) Google's own consent flow, or (b) a consent management platform such as one certified by IAB Europe. Whichever you pick, the rule is the same: the ad script must not be requested until consent has been granted, and the slots must stay empty and unfilled if consent is refused. Remember to update our Cookie Policy and Privacy Policy to describe the mechanism you actually use, and to list the new advertising partners it involves.