Yannick Simard | CTO and Co-Founder at Raccoon Logic Studios
Raccoon Logic Studios is an independent game studio in Montreal. It was founded in 2021 by a core team from Typhoon Studios. The first game the studio built, Revenge of the Savage Planet, shipped in May 2025 on Steam and the console stores. The studio owns about ten domains across its titles and the company site, and every campaign link runs through them.
Every trailer, wishlist push and storefront link needs its own destination. A YouTube trailer sends viewers to a Steam wishlist page before release and to the purchase page after it. An Xbox event on Facebook needs another link. Storefront URLs also end in a product ID nobody remembers, where a studio domain carries the game's name.
The studio routes every campaign link through redirect.pizza, on its own domains, and has done for about five years.
CTO and co-founder Yannick Simard reads the clicks per link, platform and country in one place, next to what each storefront reports. Yannick has not seen it go down since he built it. "It's a really good match", he says.
At a glance
- About ten domains across the studio's titles and company site, all campaign links routed through redirect.pizza
- Four social platforms and three storefronts served from one set of branded links
- One view of campaign-link traffic across stores, alongside the analytics each platform already provides
- Zero outages reported since setup, configured once and extended per campaign
One small team, three properties, ten domains
Raccoon Logic Studios is a small team of AAA veterans, and everyone wears several hats. Each game has its own website, the company has one, and a few short domains sit on top for campaign links. Marketing runs on Facebook, TikTok, Instagram and YouTube, with a call to action in every post. Yannick manages the engineering team and the technical roadmap, handles the console makers' requirements, and doubles as the studio's part-time data analyst.
Why the launch plan needed dozens of traceable links
The marketing plan for Revenge of the Savage Planet combined four social platforms, three storefronts and two phases. Before release every link had to reach a wishlist page, after release a purchase page. Every combination needed its own destination, and the destination changed on launch day.
The studio's website aliases covered a plain redirect and nothing else. The storefronts each report in their own console and their own shape, and not all of them offer the same detail. What none of them gives is one view across all three. Yannick wanted that view of campaign-link traffic across storefronts, next to the analytics each platform already provided.
Buying beat wiring redirects into the website
Yannick could have coded the redirects into the studio's website, and a web server can log those requests. What he wanted was good telemetry built in: knowing where people come from when they click, without assembling it himself. The logging, the reporting and the upkeep would otherwise have been his to build and keep running. That is on top of an engineering roadmap and the console makers' requirements. He searched for redirect solutions, compared one or two tools, and tested redirect.pizza against the mental model he already had. Once the prototype worked, he did not touch it again, apart from adding links per campaign.
I didn't want to just jump into it and try to implement something myself. redirect.pizza was among the possibilities, and I picked it up.
What the work looks like now
Every call to action gets its own redirect on a studio domain. A YouTube trailer gets a link to the Steam wishlist, an Xbox event on Facebook gets another. Before release the link lands on the wishlist page, after release on the purchase page, and the link itself never changes. Yannick configured the DNS records by hand and adds a redirect whenever a new campaign starts.
We have one easy way to set up all those redirects, for now and future products. It's something we know works. It never went down a single time, as far as I know.
redirect.pizza serves each redirect over automatic HTTPS and logs every click. It does not host the studio's websites or replace Google Analytics, and it does not know what happened after the click. Yannick reads a timeline per link, an estimate of bot versus human traffic, and the platform and country a click came from. He combines that with each platform's own analytics and hands the marketing team a readable version.
One example of what that changes. When the numbers show people reaching a wishlist page mostly from a phone, the content gets tailored towards that. Yannick is not on the marketing team himself, and says his reading is that it fed into how they proceeded.
By always redirecting, we can centralize the information about who visited the website through that particular call to action and that particular Facebook posting or TikTok.
One picture of campaign traffic, instead of one console at a time
That is what the studio ended up with. Campaign-link traffic across four platforms and three stores is visible in one place, without opening a console per store to collect it. Yannick combines that view with the storefront reports to see what happened after the click. redirect.pizza is not a link shortener on a shared domain and not an analytics suite. It serves the redirects on domains the studio owns, with a certificate per domain on any plan from Free (Margherita) up. The click data starts at Basic (Pepperoni).
It's a no-brainer because I don't need to spend more time thinking about it or maintaining it or verifying it.
Try redirect.pizza on your own domains
Route your campaign links through your own domains, or talk to the team about bulk setups for a launch.
Related Reads
