Titro: Multilingual SEO and Meta Tracking for a Subtitle App

Titro’s buyers talk to a camera and post the result: creators on TikTok, Instagram Reels and YouTube Shorts, podcasters and interviewers with long recordings, and agencies, media companies and newsrooms that subtitle for clients. Many are Albanian speakers in Kosovo and Albania, or in Albanian families in Germany, Switzerland and Austria, who switch into English or German mid-sentence. Titro understands both main Albanian dialects, Gheg and Tosk, and keeps up when a sentence changes language.

At the end of September 2026, as titro.live went up, we pulled Google Keyword Planner data, moved the first pages onto the phrases people actually search and added new ones. Four findings shaped the site:

Titro’s Albanian site, titroshqip.com, came first and already held the Albanian pages, so they stayed there. Google accepts language versions on different domains, so the two sites name each other with hreflang annotations. Google only uses those when every page in a set points back at the others.

Fourteen English pages, including every comparison page, have no German version, and two German pages have no English one. One of those two covers bilingual subtitles and says plainly what Titro does not do: one export carries one language, mixed as spoken or fully translated.

The blog has 15 posts in each language, published between October 1 and October 20, 2026:

Each post is checked against how the app behaves, limits included. The noise post names the problem no filter fixes, and the names post says the personal dictionary learns a spelling once you make the same fix in two different videos.

We also write from titro.live’s Search Console data. When German searches about Instagram began to appear in early October, the Instagram Reels guide went up in English and German on October 5.

Teleprompter searches were among the largest in the data, and Titro’s app already had a teleprompter, so titro.live has a free online teleprompter that works on the page: paste a script, set the speed in words per minute, mirror the text for a beam-splitter rig, and read. It runs in the browser with no account, and the script stays on the device. The page links to the app’s teleprompter, where the subtitles follow what you actually said.

In mid-September 2026, Titro had no Meta Pixel, no Conversions API and no campaign data. It sells subscriptions on the web, and the two moments that matter most happen where a browser pixel can’t see them: a new user’s free first video finishing on Titro’s servers, and Paddle, its payment provider, confirming a subscription. So the tracking has a browser half and a server half.

Server events carry the email address and the account ID, both hashed with SHA-256 before they leave. Meta requires the email to be hashed and recommends hashing the ID. At signup the account stores the ad’s UTM tags and, only for visitors who accepted all cookies, the browser identifiers Meta uses to match a click to a person. Meta can then credit a server event to the ad that started it, and Titro can count paying users per ad in its own records. Both Titro sites and its server send to one pixel ID, so both halves land in one dataset.

The browser side waits for consent. The Google tag starts in Consent Mode with advertising and analytics storage denied, and the Meta Pixel doesn’t load until a visitor taps “Accept all”. The banner appears in English or German by browser language. The server events are disclosed in Titro’s privacy policy, which names Meta, lists the three moments reported (a sign-up, the first finished video and a new subscription) and explains how to opt out of the server reports.

1. 1

   Pull search data for every market that has it, build pages around the words people actually type, and check each page against what the product really does.

2. 2

   Put each language on its own URL and link every version to the others both ways, across domains when a language lives on another site.

3. 3

   Write comparison pages from competitors’ own pricing and help pages, date every source, and say where a competitor is ahead.

4. 4

   Send events that happen away from the browser, such as a first use or a payment, from your server, each with an ID tied to the real event.

5. 5

   Ask for consent before the pixel loads, and store the ad’s tags on the account so paying customers can be counted per ad.

For how we set up this kind of measurement, see conversion tracking and analytics and Meta Pixel vs Conversions API on Shopify. Our Meta ads agency page covers how we run campaigns, and the ad creative page covers statics and video edits. The Traverse case study covers another app client, and the rest of our projects are on the work page.

If you sell an app or a subscription and want the same setup, send us your site through the contact page. A partner replies within one business day.